| Summary: | When adding certificates to ssh-agent, use expiry date as upper bound for lifetime | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Adam Eijdenberg <adam> | ||||||||
| Component: | ssh-add | Assignee: | Assigned to nobody <unassigned-bugs> | ||||||||
| Status: | NEW --- | ||||||||||
| Severity: | enhancement | CC: | djm | ||||||||
| Priority: | P5 | ||||||||||
| Version: | 7.4p1 | ||||||||||
| Hardware: | All | ||||||||||
| OS: | All | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Adam Eijdenberg
2017-02-02 21:13:58 AEDT
Created attachment 2936 [details]
Patch with correct content type set
Created attachment 3085 [details]
automatically set lifetimes, add -C, -f and -v options
This attempts the same thing a little differently.
This only looks at the valid_before time - I don't think it is helpful to warn if the certificate isn't yet valid as adding a cert that starts a few seconds in the future seems like a pretty common thing to do. Maybe it could be a debug message?
I also added a short grace period for expiring certificates, a way to override the helpfulness (-f), more nuanced error checking (e.g. not skipping loading a key if the cert was expired), a -C flag to only load certs and a verbose (-v) flag to get at the new debug messages.
|