On 3/12/2012 5:46 PM, Jan Friesse wrote: > Tomcrypt in corosync is for long time not updated. Because we have > support for libnss, libtomcrypt can be removed. > > Also few leftovers (AES is 256 bits, not 128, ...) are removed. > > Signed-off-by: Jan Friesse <jfriesse@xxxxxxxxxx> Patch looks good to me to start but: 1) cfgtool -c0 -> disable crypto, -c1 -> enable crypto 2) we might want to consider the option to allow users to configure nss encryption level and maybe the digest (not sure those are the right terms in the crypto world). It doesn´t have to be now or urgent but some environment might require higher standards than our defaults. Allow them to change them on the fly by upgrading nss and issuing a cmap call would be a major winner. Fabio _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
