The cosign development team has released cosign 3.1.1. Cosign 3.1.1 corrects a potential crash in cosignd 3.1.0 caused by an argument formatting bug, triggered when a pre-2.0 client filter performs a service cookie CHECK. This bug is only present in cosignd 3.1.0, not in any previous cosign 3.0.x release.
The filters are unchanged. * Download <https://sourceforge.net/projects/cosign/files/cosign/cosign-3.1.1/cosign-3.1.1.tar.gz/download> * Checksums SHA256(cosign-3.1.1.tar.gz)= 9ae6ad4560d744050673e0a0714e25421e948154cd27edfe6ed938bb9c635b30 SHA1(cosign-3.1.1.tar.gz)= 631f89fb3be33d4133ae30b2fd410575dfc0ff8a RIPEMD160(cosign-3.1.1.tar.gz)= 5c76dd9cbb3e8136d6e36ae19f74d53486496668 * Git tag signing A GPG-signed cosign-3.1.1 tag is in the cosign git repository [1]. You may verify the tag with the public key for [email protected], available onpgp.mit.edu and keyserver.pgp.com. Please report bugs on the SF.net tracker. Thanks for your support of cosign. andrew -- Changes since 3.1.0: * daemon: correct format for arguments when handling CHECKs from clients using protocol 0. This problem does not affect cosignd 3.0.x ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
