| 1 |
On Fri, Feb 22, 2019 at 9:58 PM Matthew Thode <prometheanfire@g.o> wrote: |
| 2 |
> |
| 3 |
> Ok, after setting that up portage wants to update pgp keys, which fail |
| 4 |
> because keyservers suck. It doesn't look like we can change the |
| 5 |
> keyservers or disable the update entirely but we can set the retries to |
| 6 |
> 0 (which better disable it...). Robbat2 had a patch to allow disabling |
| 7 |
> the update but it doesn't look like it was applied. |
| 8 |
|
| 9 |
I assume that it proceeds after some timeout? Or does it completely |
| 10 |
bail? IMO failing successful makes more sense though it is less |
| 11 |
secure. |
| 12 |
|
| 13 |
It definitely makes sense to attempt a keyserver update since that is |
| 14 |
going to be the mechanism to catch key revocations. It also will make |
| 15 |
life easier on users using an older stage3 that happens to have |
| 16 |
expired keys. Well, assuming the keyserver works... |
| 17 |
|
| 18 |
-- |
| 19 |
Rich |
Archives