As an Azure advocate, I appreciate that someone from Microsoft is contributing pulls to Bouncy Castle... KeyVault is a great resource.
-----Original Message----- From: Stephan Adler [mailto:stephan.ad...@microsoft.com] Sent: Thursday, August 13, 2015 4:42 PM To: dev-crypto-csharp@bouncycastle.org Subject: [dev-crypto-csharp] Extending Org.BouncyCastle.Security.SignerUtilities.GetSigner Hi, I'm looking for a way to extend/change the behavior of the SignerUtilities.GetSigner factory in order to add new algorithms or replace existing ones. I my case I'm implementing a time stamping authority. Thanks to BouncyCastle this is rather straight forward. But instead of having to secure the key material on the servers I'd like to offload that task to Azure KeyVault. Modifying the behavior of SignerUtilities.GetSigner would allow me to replace the implementation of SHA-256 or other signing algorithms with one that is using Azure KeyVault. I have a change available (https://github.com/bcgit/bc-csharp/compare/master...stephanadler1:dev/Stephan/factory) but was wondering if there are other mechanisms in BouncyCastle available that I didn't realize. Thanks, Stephan ********************************************************************** 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.
