<div dir="ltr">I think this is what you're looking for<br><br><a href="http://lists.fedoraproject.org/pipermail/rel-eng/2008-August/001627.html">http://lists.fedoraproject.org/pipermail/rel-eng/2008-August/001627.html</a><br>
<br><div class="gmail_quote">2008/8/29 Axel Thimm <span dir="ltr"><<a href="mailto:Axel.Thimm@atrpms.net">Axel.Thimm@atrpms.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Fri, Aug 29, 2008 at 12:15:23AM -0400, Warren Togami wrote:<br>
> Jeroen van Meeuwen wrote:<br>
>> I'm not sure how that solves the net install use case, especially if<br>
>> mirrormanager is going to redirect to os.newkey/, as signatures used on<br>
>> os.newkey/ packages will not meet what the installer expects the<br>
>> signature to be on these files.<br>
>><br>
><br>
> You misunderstand the New Key plan. Mirrormanager for the existing<br>
> repos fedora, updates and updates-testing will not redirect to the new<br>
> location. Please read the plan again carefully.<br>
<br>
</div>Hi,<br>
<br>
where can this plan be read, I didn't see it in this list or any URL<br>
pointing to it.<br>
<br>
W/o knowing all details, why not move os to os.oldkey and use os as<br>
the new key's content? If the key is considered compromised what<br>
mirror admin would like to keep the old signed packages around anyhow?<br>
<font color="#888888">--<br>
Axel.Thimm at ATrpms.net<br>
</font><br>_______________________________________________<br>
Fedora-infrastructure-list mailing list<br>
<a href="mailto:Fedora-infrastructure-list@redhat.com">Fedora-infrastructure-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list</a><br>
<br></blockquote></div><br></div>