Re: Landing a larger-than-release change (distrusting SHA-1 signatures)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 9, 2022 at 7:19 PM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote:
>
> On Wed, Mar 09, 2022 at 01:05:38PM -0500, Matthew Miller wrote:
> > On Wed, Mar 09, 2022 at 05:40:50PM +0000, Daniel P. Berrangé wrote:
> > > > But: maybe if we logged it _and_ had a tool people could run to
> > > > look specifically for those log entries, we could do something like a Test
> > > > Day where people could send in reports?
> > >
> > > Or just have it logging in rawhide, not in the final release.
> >
> > Yes, but we still need someone to look at those logs.
>
> Don't hate me for suggesting this, but the warning message on stderr
> could suggest/request reporting the problem to bugzilla to bring it
> to maintainer's attention.
>
>    *** NOTICE: pid 1234 (firefox) used cryptographic signature
>    *** NOTICE: with deprecated SHA-1 algorithm. This usage
>    *** NOTICE: will be prevented by future policy. Please report
>    *** NOTICE: this problem to https://bugzilla.redhat.com
>
> Make it a one time message per process to avoid producing
> pages of repeated text, and allow 'touch /etc/crypto-policies/dont-warn-me'
> to hide it system wide.
>
> It would be irritating enough

I've just checked and it's not just that
my firefox already prints ~20 variations on "FAIL" on startup
but I'm also pretty sure I see these for the first time,
meaning I've never cared to check before.

> to make at least some subset of rawhide
> users followup with reporting bugs, and thus let maintainers understand
> how badly they are impacted.
>
> With regards,
> Daniel
> --
> |: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org         -o-            https://fstop138.berrange.com :|
> |: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux