search for: logspam

...more keys than that? IMO it's probably ssh-copy-id that needs to change. It looks like it filters public keys by trying them against a target host. IMO it should check them directly against authorized_keys on the target system, as that wouldn't cause login failures and will result in less logspam for server operators. -d

Dear colleagues, Can we somehow improve the UX related to a relatively freshly introduced PerSourcePenalties option? A popular pattern implies installation of the users' keys to a freshly installed machine using ssh-copy-id script. The default settings don't allow this command to work normally and causes login failures. A reasonable workaround could be adding some threshold for a number

http://bugzilla.mindrot.org/show_bug.cgi?id=778 --- Comment #1 from Damien Miller <djm at mindrot.org> 2007-05-17 18:41:41 --- Created an attachment (id=1284) --> (http://bugzilla.mindrot.org/attachment.cgi?id=1284) Report error on read/write failures I'm not sure how much logspam this patch will generate, so I'm going to run with it for a little while. -- Configure bugmail: http://bugzilla.mindrot.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

...re the other end is openssh. ssh-copy-id is also supposed to work for things that are not running openssh, like dropbear, so I'm not sure what assumptions I can safely make about what the other end is doing to handle keys. > as that wouldn't cause login failures and will result in less logspam > for server operators. What I could do is notice when people have too many keys, and warn about the possibility that they'll get locked out. I may well be doing multiple redundant attempts with the same key (I'll have to check on that) in which case I could try harder to only test any...

https://bugzilla.mindrot.org/show_bug.cgi?id=1388 Summary: Parts of auth2-pubkey.c are completely devoid of debug logging Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component:

...and port forwards per direction (bz#1327) * sshd(8): ignore stderr output from subsystems to avoid hangs if a subsystem or shell initialisation writes to stderr (bz#1750) * Skip the initial check for access with an empty password when PermitEmptyPasswords=no (bz#1638) * sshd(8): fix logspam when key options (from="..." especially) deny non-matching keys (bz#1765) * ssh-keygen(1): display a more helpful error message when $HOME is inaccessible while trying to create .ssh directory (bz#1740) * ssh(1): fix hang when terminating a mux slave using ~. (bz#1758) * ssh-k...

...and port forwards per direction (bz#1327) * sshd(8): ignore stderr output from subsystems to avoid hangs if a subsystem or shell initialisation writes to stderr (bz#1750) * Skip the initial check for access with an empty password when PermitEmptyPasswords=no (bz#1638) * sshd(8): fix logspam when key options (from="..." especially) deny non-matching keys (bz#1765) * ssh-keygen(1): display a more helpful error message when $HOME is inaccessible while trying to create .ssh directory (bz#1740) * ssh(1): fix hang when terminating a mux slave using ~. (bz#1758) * ssh-k...

...and port forwards per direction (bz#1327) * sshd(8): ignore stderr output from subsystems to avoid hangs if a subsystem or shell initialisation writes to stderr (bz#1750) * Skip the initial check for access with an empty password when PermitEmptyPasswords=no (bz#1638) * sshd(8): fix logspam when key options (from="..." especially) deny non-matching keys (bz#1765) * ssh-keygen(1): display a more helpful error message when $HOME is inaccessible while trying to create .ssh directory (bz#1740) * ssh(1): fix hang when terminating a mux slave using ~. (bz#1758) * ssh-k...