On Jan 31, 2014, at 10:40 AM, Graham Clinch <g.cli...@lancaster.ac.uk> wrote:
> Hello, > > Suffering the same problem as Ray Hodel in Jan 2012 (trying to use a server > https certificate with the same CN as the cosign client certificate), and > inspired by his post to this list, I've made a very small patch to the IIS > module that locates client certificate by the 'friendly name' set through the > certificate store in addition to locating it via common name. Thank you very much for the contribution. I've committed this to the cosignmodule master branch. > I've attached the patch in case it is useful to others - it's been running in > production for a couple of months on a few fairly high-traffic sites and > we've not seen any problems. > > In the process of developing this, I spotted that version 3.1.1 was available > on sourceforge > (http://sourceforge.net/projects/cosign/files/cosign-windows/), but that the > download page of weblogin.org is directing users to version 3.1.0. Apologies! I've corrected this. > I've also attached a patch to the visual studio sln file that simplifies the > build options (Release for x86 and Release for x64). I'd like to apply this one as well, but the patch fails to apply to the cosignmodule master branch. If you submit a patch applying cleanly, I'll apply it. Best, andrew
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________ Cosign-discuss mailing list Cosign-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cosign-discuss
