Skip to content

Conversation

@luigidemasi
Copy link

No description provided.

Copy link
Contributor

@norrisjeremy norrisjeremy left a comment

Choose a reason for hiding this comment

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

  1. Can you run mvn formatter:format to ensure that everything is formatted correctly?
  2. Does this support SSH certs for host keys? If not, we need to add support for that too, as I'm opposed to only adding support SSH certs for user pubkey auth, w/o also adding support for SSH certs as host keys as well at the same time.

@davsclaus
Copy link
Contributor

@norrisjeremy is there more feedback to this, as it would be nice to get to the finish line, thanks

@norrisjeremy
Copy link
Contributor

@norrisjeremy is there more feedback to this, as it would be nice to get to the finish line, thanks

  1. None of my earlier feedback appears to have actually been incorporated: the PR author simply marked them all as resolved w/o making any of the suggested changes.
  2. To quote part of my earlier review: "Does this support SSH certs for host keys? If not, we need to add support for that too, as I'm opposed to only adding support SSH certs for user pubkey auth, w/o also adding support for SSH certs as host keys as well at the same time."

@luigidemasi
Copy link
Author

@norrisjeremy is there more feedback to this, as it would be nice to get to the finish line, thanks

  1. None of my earlier feedback appears to have actually been incorporated: the PR author simply marked them all as resolved w/o making any of the suggested changes.
  2. To quote part of my earlier review: "Does this support SSH certs for host keys? If not, we need to add support for that too, as I'm opposed to only adding support SSH certs for user pubkey auth, w/o also adding support for SSH certs as host keys as well at the same time."

Hi @norrisjeremy, thanks for following up. I marked the comments as resolved on GitHub because I had already addressed them locally and didn’t want to lose track of your suggestions. I’m currently adding support for host keys as well (it’s nearly finished) and I’ll push everything together in the next update. Please let me know if you have any additional suggestions in the meantime.

@norrisjeremy
Copy link
Contributor

Hi @norrisjeremy, thanks for following up. I marked the comments as resolved on GitHub because I had already addressed them locally and didn’t want to lose track of your suggestions. I’m currently adding support for host keys as well (it’s nearly finished) and I’ll push everything together in the next update. Please let me know if you have any additional suggestions in the meantime.

Hi @luigidemasi,

Great, thanks! We are excited to have someone step up and contribute this work!

Thanks,
Jeremy

@luigidemasi
Copy link
Author

@norrisjeremy

  1. Does this support SSH certs for host keys? If not, we need to add support for that too, as I'm opposed to only adding support SSH certs for user pubkey auth, w/o also adding support for SSH certs as host keys as well at the same time.

I added the support for Host Certificate, let me know wdyt.

@davsclaus
Copy link
Contributor

Great to see progress on this one. If we are getting close to the finish line it would be good to do the last review and update the reported findings so fingers crossed we can get this merged and released. Thank you.

@norrisjeremy
Copy link
Contributor

Great to see progress on this one. If we are getting close to the finish line it would be good to do the last review and update the reported findings so fingers crossed we can get this merged and released. Thank you.

I probably won't have time to start reviewing this again until next week.

@davsclaus
Copy link
Contributor

Great to see progress on this one. If we are getting close to the finish line it would be good to do the last review and update the reported findings so fingers crossed we can get this merged and released. Thank you.

I probably won't have time to start reviewing this again until next week.

Thanks for the update, no problem. Just glad we are on path to the goal line.

@davsclaus
Copy link
Contributor

Sorry to bother - but would be good to get this reviewed

@norrisjeremy
Copy link
Contributor

Sorry to bother - but would be good to get this reviewed

HI @davsclaus,

Yes, I haven't forgotten, I will try to review it when I have some time available.

Thanks,
Jeremy

Copy link
Contributor

@norrisjeremy norrisjeremy left a comment

Choose a reason for hiding this comment

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

Just a few initial comments, I still have a lot left to review.

@luigidemasi luigidemasi force-pushed the openssh_certificate_support branch from e3194d7 to 7db8379 Compare October 18, 2025 12:50
@luigidemasi luigidemasi force-pushed the openssh_certificate_support branch 2 times, most recently from aa826fc to b2240d6 Compare January 15, 2026 19:34
Copy link
Contributor

@norrisjeremy norrisjeremy left a comment

Choose a reason for hiding this comment

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

Thank you for your patience as I continue review this.

Aside from a few small stylistic nits I've pointed out, the only signficant item I can see is API changes proposed for KeyExchange (changing the next() method to no longer be abstract & introducing the the doNext() and getFingerprint(byte[]) methods).

As I mentioned inline, if these API changes to KeyExchange aren't necessary for the cert support (which I don't believe they are, but I could have missed it since this is such a large PR), I'd rather they not be made (at least as part of this PR).

}


protected boolean doNext(Buffer buf, int sshMessageType) throws Exception {
Copy link
Contributor

Choose a reason for hiding this comment

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

From what I can see, the cert support being introduced here doesn't seem to require the changes here though to the next() method (and introduction of doNext()), right?

If that's true, then I'd rather not introduce API changes like this into KeyExchange.

@davsclaus
Copy link
Contributor

Thanks for the progress on this one - looks like we are getting close to be ready. @luigidemasi there is a few things still to do thanks.

@luigidemasi luigidemasi force-pushed the openssh_certificate_support branch from b2240d6 to 3002923 Compare January 22, 2026 17:28
@norrisjeremy
Copy link
Contributor

Hi @luigidemasi,

Can you run mvn formatter:format?
It seems the build fails currently:

Error:  Failed to execute goal net.revelc.code.formatter:formatter-maven-plugin:2.29.0:validate (default) on project jsch: File '/home/runner/work/jsch/jsch/src/test/java/com/jcraft/jsch/HostCertificateIT.java' has not been previously formatted. Please format file (for example by invoking `mvn net.revelc.code.formatter:formatter-maven-plugin:2.29.0:format`) and commit before running validation! -> [Help 1]

Thanks!
Jeremy

@luigidemasi luigidemasi force-pushed the openssh_certificate_support branch from 3002923 to 6147bd3 Compare January 22, 2026 17:34
@luigidemasi
Copy link
Author

luigidemasi commented Jan 22, 2026

Hi @luigidemasi,

Can you run mvn formatter:format? It seems the build fails currently:

Error:  Failed to execute goal net.revelc.code.formatter:formatter-maven-plugin:2.29.0:validate (default) on project jsch: File '/home/runner/work/jsch/jsch/src/test/java/com/jcraft/jsch/HostCertificateIT.java' has not been previously formatted. Please format file (for example by invoking `mvn net.revelc.code.formatter:formatter-maven-plugin:2.29.0:format`) and commit before running validation! -> [Help 1]

Thanks! Jeremy

@norrisjeremy done!

@luigidemasi luigidemasi force-pushed the openssh_certificate_support branch from 6147bd3 to fd2e894 Compare January 22, 2026 19:30
@luigidemasi luigidemasi force-pushed the openssh_certificate_support branch 2 times, most recently from a57ab9e to 95f18cb Compare January 26, 2026 13:22
@luigidemasi luigidemasi force-pushed the openssh_certificate_support branch from 95f18cb to 0556aad Compare January 27, 2026 21:04
@luigidemasi luigidemasi force-pushed the openssh_certificate_support branch from 0556aad to 0cf60d9 Compare January 28, 2026 10:33
@sonarqubecloud
Copy link

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.

4 participants