jazzm0 commented on issue #686: URL: https://github.com/apache/mina-sshd/issues/686#issuecomment-2717140921
Hi Tomas, I've created the registrar https://github.com/jazzm0/ssh-daemon/pull/87/files#diff-3cbccf0a1071ce5ee11f0568a069c5358ba7d5dde7fad851c205b94af2486a2d according to the documentation, and registered it via https://github.com/jazzm0/ssh-daemon/pull/87/files#diff-21740cc7b37e3b98b1728f43b9a5167784e53f41da94bc001f5f487b62c0b666R76. I even call SecurityUtils.setDefaultProviderChoice to set it as the first option. I also see, that despite the deletion of all other providers, a BouncyCastle provider is created. Despite this, I never see AbstractSecurityProviderRegistrar.isSecurityEntitySupported is called for AES encryption. Is there something else to do? I see, that my registered provider is always asked first, wether it supports the entity. Thanks for your feedback. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
