Slightly related to  .NET CF I have been able to port a limited subset to 
Xamarin’s API and am having zero issues on Android.  I’m compiling tonight on 
iOS and debugging now.

The Shared Profiles subset API seems to leave out Android and iOS specific 
implementations of SecureRandom.  I have been able to simply paste the relevant 
BC code into an Android or iOS project and have success (assuming the 
references to mono are added).

I don’t know how highly utilized .NET CF is, but I hope to get some more 
mono/Xamarin support.  I will contribute if I can figure out how to slice off a 
piece of work that can be imported as a unit.

My fundamental limitation in contributing is that there are so many 
dependencies and related files that I can’t figure out my “commit unit of work”.

If you can help me scope my efforts into a manageable workload, I would be glad 
to contribute and map Xamarin compiler directives to BC

From: Peter Dettman 
<peter.dett...@bouncycastle.org<mailto:peter.dett...@bouncycastle.org>>
Reply-To: Peter Dettman 
<peter.dett...@bouncycastle.org<mailto:peter.dett...@bouncycastle.org>>
Date: Tuesday, March 31, 2015 at 1:33 AM
To: 
"announce-crypto-csh...@bouncycastle.org<mailto:announce-crypto-csh...@bouncycastle.org>"
 
<announce-crypto-csh...@bouncycastle.org<mailto:announce-crypto-csh...@bouncycastle.org>>,
 
"dev-crypto-csharp@bouncycastle.org<mailto:dev-crypto-csharp@bouncycastle.org>" 
<dev-crypto-csharp@bouncycastle.org<mailto:dev-crypto-csharp@bouncycastle.org>>
Subject: [dev-crypto-csharp] Release 1.8.0-RC.1 now available

Hi All,
A release candidate for 1.8.0 is now available at 
http://downloads.bouncycastle.org/betas/ .

The most notable changes:
- DTLS client/server support.
- Improved TLS_PSK, including server-side support.
- Improved TLS_SRP, including server-side support and group validation 
(defaults to RFC 5054 Appendix A groups).
- Added further precautions against smacktls-type TLS state-machine attacks.
- Added custom elliptic curve implementations (via CustomNamedCurves registry) 
for all the binary-field curves in SEC (with aliases for the NIST B-??? and 
K-??? equivalents). Also for a few of the smaller prime-field curves.

Now a request for help with .NET Compact Framework: we would like to maintain 
support for .NET CF 1.0 in 1.8.0, but I have concluded that I no longer have an 
environment in which to develop for this (the SDK appears to not be separately 
downloadable). I doubt that the needed changes are very extensive, but they are 
there. If there's anyone out there that can help with this, please contribute 
your patches! (preferably at https://github.com/bcgit/bc-csharp).

Regards,
Pete Dettman

**********************************************************************
This e-mail may contain information that is privileged, confidential or 
protected under state or federal law. If you are not an intended recipient of 
this email, please delete it, notify the sender immediately, and do not copy, 
use or disseminate any information in the e-mail. Any tax advice in this email 
may not be used to avoid any penalties imposed under U.S. tax laws. E-mail sent 
to or from this e-mail address may be monitored, reviewed and archived.

Reply via email to