Re: Please help: public key authentication problem after PR1.2
 

I have done that unfortunately, but still no joy (and I can ssh fine using developer)

Re: Please help: public key authentication problem after PR1.2
 

Hi,

well, I think as my home network is fully behind my router and hence not visible to the outside world this should not conflict at all. Anyway due to some stupid setups of our company's administrator I was constrained to move my home's address range to something 'strange' as otherwise I was not able to set up VPN connections to the company's network. So, as I think that others my have done similar things and changed the home address ranges of theri networks to something not fitting which seems to be pre-configured in the sshd_config line I thought this might be a common problem, could that be validated by someone else yet ?

Regards,
Timm

Re: Please help: public key authentication problem after PR1.2
 

Make sure /home/user/ isn't world-writable, i.e.

You could also try even more restrictive permissions (e.g. 700), but not sure if that brings other problems - 755 should be fine. Also make sure that similar permissions are in effect for /home/user/.ssh/ (700) and /home/user/.ssh/authorized keys (600).

Don't know what the numbers mean? read me

Re: Please help: public key authentication problem after PR1.2
 

Bingo! thanks. of course.
And note that you cannot chmod as root (due to aegis), you must be logged in as user/developer.

But now I'm worried it will break something. They must have made it world-writable for a reason.