On 12/3/23 11:45, Peter Robinson wrote:
On Sat, Dec 2, 2023 at 7:33 PM Sean Anderson wrote:
Both SHA1 and (especially) MD5 are no longer as safe as they once were for
cryptographic use. Replaces examples which use them with examples using
SHA256 instead. This will provide more-secure defaults
On Sat, Dec 02, 2023 at 02:33:14PM -0500, Sean Anderson wrote:
> Both SHA1 and (especially) MD5 are no longer as safe as they once were for
> cryptographic use. Replaces examples which use them with examples using
> SHA256 instead. This will provide more-secure defaults for users who use
> documen
Hi Sean,
On Sat, 2 Dec 2023 at 12:38, Sean Anderson wrote:
>
> On 12/2/23 14:33, Sean Anderson wrote:
> > Both SHA1 and (especially) MD5 are no longer as safe as they once were for
> > cryptographic use. Replaces examples which use them with examples using
> > SHA256 instead. This will provide mo
On Sat, Dec 2, 2023 at 7:33 PM Sean Anderson wrote:
>
> Both SHA1 and (especially) MD5 are no longer as safe as they once were for
> cryptographic use. Replaces examples which use them with examples using
> SHA256 instead. This will provide more-secure defaults for users who use
> documentation ex
On 12/2/23 14:33, Sean Anderson wrote:
Both SHA1 and (especially) MD5 are no longer as safe as they once were for
cryptographic use. Replaces examples which use them with examples using
SHA256 instead. This will provide more-secure defaults for users who use
documentation examples as a base for t
Both SHA1 and (especially) MD5 are no longer as safe as they once were for
cryptographic use. Replaces examples which use them with examples using
SHA256 instead. This will provide more-secure defaults for users who use
documentation examples as a base for their own use. This is not too
necessary f
6 matches
Mail list logo
