Skip to content

[PM-23653] Add support for ssh keys #375

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

[PM-23653] Add support for ssh keys #375

wants to merge 2 commits into from

Conversation

Hinton
Copy link
Member

@Hinton Hinton commented Aug 1, 2025

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-23653

📔 Objective

Adds support for importing ssh keys using CXF.

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation
    team

🦮 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

@Hinton Hinton requested a review from a team as a code owner August 1, 2025 08:27
@Hinton Hinton requested review from justindbaur and quexten August 1, 2025 08:27
Copy link
Contributor

github-actions bot commented Aug 1, 2025

Logo
Checkmarx One – Scan Summary & Detailsb95419d5-1f9f-434a-8719-af79648b6b31

Great job! No new security vulnerabilities introduced in this pull request

Copy link

codecov bot commented Aug 1, 2025

Codecov Report

❌ Patch coverage is 83.60656% with 20 lines in your changes missing coverage. Please review.
✅ Project coverage is 74.15%. Comparing base (f75f62e) to head (b1bbf60).

Files with missing lines Patch % Lines
crates/bitwarden-exporters/src/cxf/import.rs 28.00% 18 Missing ⚠️
crates/bitwarden-ssh/src/import.rs 87.50% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #375      +/-   ##
==========================================
+ Coverage   74.11%   74.15%   +0.04%     
==========================================
  Files         253      254       +1     
  Lines       21774    21879     +105     
==========================================
+ Hits        16138    16225      +87     
- Misses       5636     5654      +18     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

sonarqubecloud bot commented Aug 1, 2025

Copy link
Contributor

@quexten quexten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After the removal of expect this looks good to me. One note, but it's not actionable here.

};

let fields = [
credential.key_comment.as_ref().map(|comment| Field {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note (non-actionable): In the agent, we treat the name of the cipher as the comment, and advertise it as such. We may want to research (not here) how other clients treat comment vs name, to not disrupt user experience. If someone comes over from another product which uses a separate key comment field, suddenly all their ciphers may be named something different.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we will have a lot of follow up work as other credential managers implements credential exchange and we discover edge cases 😰

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants