| 1 |
* Michał Górny schrieb am 06.07.18 um 11:33 Uhr: |
| 2 |
> W dniu pią, 06.07.2018 o godzinie 11∶08 +0200, użytkownik Marc |
| 3 |
> Schiffbauer napisał: |
| 4 |
> > * Michał Górny schrieb am 05.07.18 um 20:25 Uhr: |
| 5 |
> > > W dniu czw, 05.07.2018 o godzinie 17∶37 +0200, użytkownik Marc |
| 6 |
> > > Schiffbauer napisał: |
| 7 |
> > > > +1 for 5 years or at least 3. |
| 8 |
> > > > |
| 9 |
> > > > Having to renew/edit the key each year seems crazy to me. |
| 10 |
> > > > |
| 11 |
> > > > I have my primary key offline only, so renewing/editing it is a much |
| 12 |
> > > > more time consuming matter than if I had my primary key always with me |
| 13 |
> > > > which I consider a bad idea because you do not need to. |
| 14 |
> > > > |
| 15 |
> > > |
| 16 |
> > > ...and you consider it a good idea to keep the primary key untouched for |
| 17 |
> > > 5 years? You don't even know if the medium holding it still works. |
| 18 |
> > |
| 19 |
> > Yes. Backup media exists at a different place. |
| 20 |
> |
| 21 |
> If you don't see it for 5 years, how can you be sure that it is even |
| 22 |
> still there? |
| 23 |
|
| 24 |
Are you serious? Who tells you that I do not check from time to time? |
| 25 |
|
| 26 |
I am sure there will always be some scenario which makes a key |
| 27 |
unacessible in some way. I do not disagree with that. Its a matter of |
| 28 |
propability. |
| 29 |
And for the worst case there is a revoke-Certificate which can be used. |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
0xCA3E7BF67F979BE5 - F7FB 78F7 7CC3 79F6 DF07 |
| 34 |
6E9E CA3E 7BF6 7F97 9BE5 |
Archives