http://bugzilla.suse.com/show_bug.cgi?id=1006221 http://bugzilla.suse.com/show_bug.cgi?id=1006221#c5 Petr Cerny <pcerny@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #5 from Petr Cerny <pcerny@suse.com> --- (In reply to Adam Spiers from comment #4)
(In reply to Petr Cerny from comment #3)
It is, but producing a message depending on whether the port is standard 22 or something else will just inflate it.
It will inflate what? It would hardly be a huge inflation to the source code.
I was afraid it would inflate the patch by adding reverse logic to ssh-keygen argument parsing. Fortunately it didn't turn out to be the case, so it will be fixed in the next MU.
Mentioning the ssh-keygen(1) man page should be enough, imho.
Surely that's not as helpful as providing a command they can use directly via cut and paste?
Yes, yet it also makes one more thing to think of when ssh-keygen behaviour changes, thus making it prone to rotting. -- You are receiving this mail because: You are on the CC list for the bug.