Thanks- that did the trick after restarting sshd!
RE: the security issues, I'm not too concerned by them at this point as
it's currently a VM inside a NAT which isn't DNS registered. The next
step is probably to use a "real" VM with a non-NATed IP and a DNS
registration which shouldn't be affected by this issue.
On 11/04/13 10:10, Sam Hartman wrote:
>
>> debug1: Invalid token was supplied
>> Acceptor identity different than expected
>
>
> This output means that the client believes the server identity is
> different than what the client is expecting.You can set
> GssapiStrictAcceptorCheck in /etc/ssh/sshd_config to no
> and you'll probably get around this.
>
> Long term, though, you need to figure out what name the server is
> expecting. For the system to be secure, either the server or a proxy in
> your organisation needs to enforce the requirement that the server is
> properly identified.
>
--
/****************************
Mark Cairney
ITI UNIX Section
Information Services
University of Edinburgh
Tel: 0131 650 6565
Email: [log in to unmask]
*******************************/
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
|