Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we replace sharks with blahaj ? #8990

Closed
Tracked by #6090
FirelightFlagboy opened this issue Nov 25, 2024 · 3 comments · Fixed by #9309
Closed
Tracked by #6090

Should we replace sharks with blahaj ? #8990

FirelightFlagboy opened this issue Nov 25, 2024 · 3 comments · Fixed by #9309
Assignees
Labels
A-Client Area: Parsec desktop application I-Dependency Impact: related to an dependency I-Rust Impact: Rust-related stuff

Comments

@FirelightFlagboy
Copy link
Contributor

FirelightFlagboy commented Nov 25, 2024

sharks is the rust crate we use to provide Shamir support.
That crate did not receive any updates since 2021 and the vulnerability RUSTSEC-2024-0398 was found in it.

The crate blahaj is a fork of sharks that fix that vulnerability. That fork was created because apparently the owner of sharks was not reachable.

FirelightFlagboy added a commit that referenced this issue Nov 25, 2024
@FirelightFlagboy FirelightFlagboy added A-Client Area: Parsec desktop application I-Dependency Impact: related to an dependency I-Rust Impact: Rust-related stuff labels Nov 25, 2024
@vxgmichel
Copy link
Contributor

vxgmichel commented Nov 25, 2024

+1 on migrating, the change is minor so our code won't need to be updated

github-merge-queue bot pushed a commit that referenced this issue Nov 25, 2024
FirelightFlagboy added a commit that referenced this issue Nov 28, 2024
FirelightFlagboy added a commit that referenced this issue Nov 28, 2024
FirelightFlagboy added a commit that referenced this issue Dec 13, 2024
FirelightFlagboy added a commit that referenced this issue Dec 19, 2024
@mmmarcos
Copy link
Contributor

mmmarcos commented Jan 6, 2025

@Landeers I recall there were some discussions regarding the sharks lib for the Resana project. Is this change OK for you?

@Landeers
Copy link
Contributor

Landeers commented Jan 8, 2025

@Landeers I recall there were some discussions regarding the sharks lib for the Resana project. Is this change OK for you?

OK for me

FirelightFlagboy added a commit that referenced this issue Jan 15, 2025
FirelightFlagboy added a commit that referenced this issue Jan 16, 2025
FirelightFlagboy added a commit that referenced this issue Jan 16, 2025
FirelightFlagboy added a commit that referenced this issue Jan 16, 2025
FirelightFlagboy added a commit that referenced this issue Jan 17, 2025
vxgmichel pushed a commit that referenced this issue Jan 17, 2025
* [rust] update `fuser` to `0.15.1`

Fix #9173

* Make `setattr` always return file attr even if no attr where changed

Fix #8976, fix #8991

Co-authored-by: Emmanuel Leblond <[email protected]>

* [rust] Update `ruzstd` to `0.7.3`

* Ignore `RUSTSEC-2024-0398`

Related to #8990

---------

Co-authored-by: Emmanuel Leblond <[email protected]>
FirelightFlagboy added a commit that referenced this issue Jan 21, 2025
FirelightFlagboy added a commit that referenced this issue Jan 21, 2025
* [rust] update `fuser` to `0.15.1`

Fix #9173

* Make `setattr` always return file attr even if no attr where changed

Fix #8976, fix #8991

Co-authored-by: Emmanuel Leblond <[email protected]>

* [rust] Update `ruzstd` to `0.7.3`

* Ignore `RUSTSEC-2024-0398`

Related to #8990

---------

Co-authored-by: Emmanuel Leblond <[email protected]>
FirelightFlagboy added a commit that referenced this issue Jan 21, 2025
* [rust] update `fuser` to `0.15.1`

Fix #9173

* Make `setattr` always return file attr even if no attr where changed

Fix #8976, fix #8991

Co-authored-by: Emmanuel Leblond <[email protected]>

* [rust] Update `ruzstd` to `0.7.3`

* Ignore `RUSTSEC-2024-0398`

Related to #8990

---------

Co-authored-by: Emmanuel Leblond <[email protected]>
FirelightFlagboy added a commit that referenced this issue Jan 21, 2025
* [rust] update `fuser` to `0.15.1`

Fix #9173

* Make `setattr` always return file attr even if no attr where changed

Fix #8976, fix #8991

Co-authored-by: Emmanuel Leblond <[email protected]>

* [rust] Update `ruzstd` to `0.7.3`

* Ignore `RUSTSEC-2024-0398`

Related to #8990

---------

Co-authored-by: Emmanuel Leblond <[email protected]>
FirelightFlagboy added a commit that referenced this issue Jan 21, 2025
* [rust] update `fuser` to `0.15.1`

Fix #9173

* Make `setattr` always return file attr even if no attr where changed

Fix #8976, fix #8991

Co-authored-by: Emmanuel Leblond <[email protected]>

* [rust] Update `ruzstd` to `0.7.3`

* Ignore `RUSTSEC-2024-0398`

Related to #8990

---------

Co-authored-by: Emmanuel Leblond <[email protected]>
github-merge-queue bot pushed a commit that referenced this issue Jan 21, 2025
* [rust] update `fuser` to `0.15.1`

Fix #9173

* Make `setattr` always return file attr even if no attr where changed

Fix #8976, fix #8991

Co-authored-by: Emmanuel Leblond <[email protected]>

* [rust] Update `ruzstd` to `0.7.3`

* Ignore `RUSTSEC-2024-0398`

Related to #8990

---------

Co-authored-by: Emmanuel Leblond <[email protected]>
github-merge-queue bot pushed a commit that referenced this issue Jan 21, 2025
* [rust] update `fuser` to `0.15.1`

Fix #9173

* Make `setattr` always return file attr even if no attr where changed

Fix #8976, fix #8991

Co-authored-by: Emmanuel Leblond <[email protected]>

* [rust] Update `ruzstd` to `0.7.3`

* Ignore `RUSTSEC-2024-0398`

Related to #8990

---------

Co-authored-by: Emmanuel Leblond <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client Area: Parsec desktop application I-Dependency Impact: related to an dependency I-Rust Impact: Rust-related stuff
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants