[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: nmh 1.8?
From: |
Ralph Corderoy |
Subject: |
Re: nmh 1.8? |
Date: |
Wed, 28 Dec 2022 13:08:16 +0000 |
Hi Paul,
> > - The generation and verification of Content-MD5 headers is no
> > longer performed. The -check and -nocheck switches to various nmh
> > programs that would control this functionality still exist, but
> > are non-functional and will be removed in the next release.
> >
> > That it not deprecation. The user who thinks the MD5 is being
> > checked is being fooled by them silently becoming a no-op. They
> > should be removed so the user instead suffers an error and learns
> > of the change. I'll try to get this done.
>
> Removing the options entirely doesn't seem like deprecation either.
No, it's not. But it's better than the introduced security flaw.
> Seems like they should maybe emit warnings for a release
Yes, i.e. be deprecated. But that ship has sailed and I don't think Ken
would be pleased if I added them back in so they could be deprecated.
--
Cheers, Ralph.
- nmh 1.8?, David Levine, 2022/12/26
- Re: nmh 1.8?, Ken Hornstein, 2022/12/26
- Re: nmh 1.8?, Ralph Corderoy, 2022/12/28
- Re: nmh 1.8?, Paul Fox, 2022/12/28
- Re: nmh 1.8?, Ralph Corderoy, 2022/12/31
- Re: nmh 1.8?, David Levine, 2022/12/31
- Re: nmh 1.8?, Ralph Corderoy, 2022/12/31
- Re: nmh 1.8?, Ken Hornstein, 2022/12/31
- Re: nmh 1.8?, Ken Hornstein, 2022/12/31
- Re: nmh 1.8?, Ken Hornstein, 2022/12/31