When checking to see whether we have to rebind a new key and/or
authorArt Cancro <ajc@citadel.org>
Wed, 5 Jan 2022 18:49:17 +0000 (13:49 -0500)
committerArt Cancro <ajc@citadel.org>
Wed, 5 Jan 2022 18:49:17 +0000 (13:49 -0500)
commit8e09a2927df885bd83dd6361b6a70242069083ce
tree312608c157e1ee12fbf080da1b3bd172892c04ea
parent9e24fd4e798bd6871d71531015b839d04c0dbd22
When checking to see whether we have to rebind a new key and/or
certificate, the stored "previous value" is now the sum of the
existing key *and* certificate modification times.  This causes a
rebind to occur if either file's modification time is touched.
It does not matter if this rolls over on 32-bit systems because
we are only checking to see if the value changed, not for any
particular date comparison.
citadel/COPYING
citadel/modules/crypto/serv_crypto.c
citadel/msgbase.c
citadel/room_ops.c
citadel/server_main.c
citadel/support.c
webcit-ng/Makefile
webcit-ng/ssl.c [deleted file]
webcit-ng/static/js/main.js
webcit-ng/tls.c [new file with mode: 0644]
webcit/crypto.c