Peter Dettman
Peter Dettman
I will be committing the more-or-less completed port to the main repo this weekend I expect.
After some delays the new TLS code is now committed (see Org.BouncyCastle.Tls namespace).
Our API makes little to no attempt to integrate into System.Security.Cryptography API, and it wouldn't make much sense to do so on a case-by-case basis. I'm not saying it would...
@rdicroce I'm working on merging this now (leave the conflicts to me).
As I recall, I didn't like the negotiated certificate type being stored in the CertificateRequest and had intended to move it into the SecurityParameters. If you wanted to make that...
I've now merged this. Thanks for your patience. It will be in 1.72 that is releasing shortly. Note that I cleaned up extraneous whitespace changes and also fixed some problems...
The first thing I noted about the benchmark is that the cipher is initialized for every encryption/decryption (which are very small texts) with the same key. It's unnecessary to re-initialize...
We could look at improving checks for same-key initialization (for AES/GCM I think this is something of a known issue already), but you likely couldn't expect a new version of...
I've reviewed that commit and can't see how it can be causing an issue, but perhaps if you could collect the specific p, g values of this group I could...
1. It seems the server is simply using parameters that we don't recognize, and this is considered insecure by default (but can be accepted using the system property, as you...