Has anyone ever seen 'setupfake' when logging into shell?

[BostonDriver]

I just tried to log into my dedicated IP address as I always do.

I suddenly see:

Can't exec "/bin/bash": No such file or directory at /usr/sec/bin/setupfake line 359.

and my ssh connection is ended.

Anyone have an idea what this is?

I've searched here on 'setupfake' and found no hits

I've already opened a ticket.

Thanks

[Basil]

I believe it's a security protocol in place to provide a restricted shell. Not being able to execute bash is another story..

[markwhite]

I've just experienced the same thing and was wondering if you got a reply to the ticket?

A couple of days ago I setup SVN and was editing ~/.ssh/authorized_keys but everything tested fine after these changes so I'm not convinced it's something I've done. I've only found this other relevant info:

http://blog.paradoxthemusical.com/?p=49

"I’ve recently seen this happen on a system running gentoo-hardened with grsecurity. The line number on mine’s different, but it’s still complaining about bash being missing. Here’s what I’m getting:

Can’t exec “/bin/bash”: No such file or directory at /usr/sec/bin/setupfake line 359.
shell failed at /usr/sec/bin/setupfake line 359.

As it turned out, our hosting provider (HostV) had “accidentally” enabled a security feature that they really didn’t understand, and subsequently went and turned that feature off. "

I eagerly await a reply to my ticket...

[markwhite]

After the ticket had been up for about 40 hours, a reply said it had been fixed and it was. It also said to use Live Chat to report this in the future if it happens again as it's a quick fix, but Live Chat were the ones who had told me to raise a ticket, so who knows.