-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PM-15937] ssh agent: fix first start when no .bitwarden-ssh-agent.sock exists #12356
Conversation
Thank you for your contribution! We've added this to our internal Community PR board for review. Details on our contribution process can be found here: https://contributing.bitwarden.com/contributing/pull-requests/community-pr-process. |
Ohh, interesting. I think this error was introduced as a result of a last minute security fix (#12048). I will test the PR closely tomorrow and give the final approval. Thank you for the PR! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good, I've reproduced the bug and confirmed this fixes it. Thank you!
@Icelk Could you accept the CLA? (If you've already done that, also let me know. I know the CLAssistant was buggy the past few weeks). |
No New Or Fixed Issues Found |
Just did, thanks for reminding me :) And also thank you for developing Bitwarden and all it's components! It's a great project and hugely appreciated. |
Nice, thanks again for the PR! |
🎟️ Tracking
#10825
📔 Objective
When starting the ssh-agent the first time on unix, the rust code tries to remove the previous ssh-agent socket. On first time setup, there is no file, so it fails. This change makes it fail gracefully when no file is found.
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes