[Info-vax] stumped by SSH

[Simon Clubley]

On 2016-02-07, Paul Sture <nospam at sture.ch> wrote:
> On 2016-02-06, Craig A. Berry <craigberry at nospam.mac.com> wrote:
>>
>> Does either account have a sys$login:ssh2.DIR and if so, are ownership
>> and protection set correctly for the directories and the files in them?
>> You wouldn't normally need these for password authentication, but it is
>> something SSH will look at (don't know how early in the authentication
>> process).
>
> If sys$login:ssh2.DIR exists, then ssh will try to write to the knowm_hosts
> file in it when using ssh to login to a remote system.  If the protection
> on that is too weak (e.g. it has group write), that might cause problems.
>

Phillip says there's nothing called *ssh*.* in the account's login
directory so I've run out of ideas why he's having account specific
problems.

BTW, Phillip, I assume there are no oversights in the UAF such as
_both_ the disk and directory pointing to the correct place ?
Sorry to ask such a basic question, but I really have run out of
ideas otherwise given that you don't have anything called *ssh*.*
in the login directory.

When you login to the account using telnet, I assume you can
successfully read existing files and create new ones in that directory.

Paul's comment about permissions being _too_ permissive also raised
some memories. Have you checked the file permissions in the parent
directory of the login directory itself to make sure they are identical
to the login directory for an account you can log into over SSH ?

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world