Hi Peter, thank you for the quick answer, I still have a few questions:
- In the past, the BouncyCastle version I used was usually the fork of Claire Novotny (https://github.com/novotnyllc/bc-csharp), as it has already been ported to netstandard a long time ago and there's an official NuGet package. Is your netstandard port derived from her work or was it done seperately (and if so, is there a reason for that)? - Are you planning to release BouncyCastle as an official NuGet Package (or is there one already)? That would make using and upgrading the library much easier. - If I understand correctly, the TLS implementation under Org.BouncyCastle.Tls is the current one, the one under Org.BouncyCastle.Crypto.Tls is the old/deprecated one, so I suppose the features should be added to Org.BouncyCastle.Tls? - In my opinion (as a C# dev) the code is written kinda weirdly in some places (abstract instead of static classes for lists of constants, lists of constants instead of enums, use of the non-generic IDictionary) which makes it hard to read sometimes. Is there a reason for that and would a (seperate) PR with these kinds of approvements be appreciated? Regards, Patrick Am Fr., 22. Juli 2022 um 06:40 Uhr schrieb Peter Dettman <peter.dett...@bouncycastle.org>: > > Hi Patrick, > We'd get to it eventually, but it would certainly be helpful to get a > PR. It's true that Org.BouncyCastle.Tls is a port from bc-java, but > unlike some other APIs this one is up-to-date (putting aside the absence > of JSSE and JCA/JCE equivalents). So PRing to bc-csharp is fine. > > Please ensure you are working from the latest in > https://github.com/bcgit/bc-csharp, which is now a netstandard20/net60 > project in preparation for a 2.0 release. > > Regards, > Pete Dettman > > On 7/21/2022 7:53 PM, monkey....@gmail.com wrote: [...]
