diff options
| author | Colin Watson <cjwatson@debian.org> | 2008-05-13 11:33:14 +0000 |
|---|---|---|
| committer | Colin Watson <cjwatson@debian.org> | 2008-05-13 11:33:14 +0000 |
| commit | 7256d9e880a09bbc57de08a308907c924d3e6752 (patch) | |
| tree | 027243bccb1dde3f8d241f27de1c60581c59498f /debian/README.compromised-keys | |
| parent | f2a7626a59e3df619d04082c7c7942492e886c03 (diff) | |
changed ssh-vulnkey output
Diffstat (limited to 'debian/README.compromised-keys')
| -rw-r--r-- | debian/README.compromised-keys | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/debian/README.compromised-keys b/debian/README.compromised-keys index 048aadd04..bfffc154a 100644 --- a/debian/README.compromised-keys +++ b/debian/README.compromised-keys | |||
| @@ -101,9 +101,9 @@ OpenSSH: | |||
| 101 | 101 | ||
| 102 | ssh-vulnkey /path/to/key | 102 | ssh-vulnkey /path/to/key |
| 103 | 103 | ||
| 104 | If ssh-vulnkey says "No blacklist file", then it has no information | 104 | If ssh-vulnkey says "Unknown (no blacklist information)", then it has no |
| 105 | about whether that key is affected. If in doubt, destroy the key and | 105 | information about whether that key is affected. If in doubt, destroy the |
| 106 | generate a new one. | 106 | key and generate a new one. |
| 107 | 107 | ||
| 108 | 4. Regenerate any affected user keys | 108 | 4. Regenerate any affected user keys |
| 109 | 109 | ||