If your ssh server is not up to date then yes, a controlled but vigorous
panic may be in order.
Kurt Seifried, kurt@seifried.org
A15B BEE5 B391 B9AD B0EF
AEB0 AD63 0B4E AD56 E574
http://www.seifried.org/security/
----- Original Message -----
From: "Avi Schwartz"
I found the following messages in my logs:
Dec 12 18:36:25 coral sshd[7394]: Did not receive identification string from IP. Dec 12 18:36:26 coral sshd[7395]: scanned from IP with SSH-1.0-SSH_Version_Mapper. Don't panic
Should I or shouldn't I panic?
Thanks, Avi -- Avi Schwartz avi@CFFtechnologies.com
"I have to share the credit. I invented it, but Bill made it famous." - IBM engineer Dave Bradley describing the control-alt-delete reboot sequence
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com