Re: SSH issue?
Don Armstrong wrote:
> On Thu, 18 Feb 2016, Chris wrote:
>> after the following entry
>>
>> Feb 18 17:48:05 jupiter sshd[30204]: pam_unix(sshd:auth): authentication
>> failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.88.177.93
>> user=root
>> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^
>>
>> my Jessie Server was down.
>>
>> Has anyone seen this? Went it accidentally down? Is this already an
>> libc exploit?
>
> This just looks like the serial terminal line got screwed up (probably
> due to the restart/failure) some time after that line was printed.
Ok, thank you. Just wondered, because this server normally doesn't crash.
- Chris
Reply to: