> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dave Korn
> Sent: Wednesday, January 18, 2006 6:15 PM
> To: cygwin@cygwin.com
> Subject: RE: Wich privileges required by ssh-host-config running user?
>
>
> Manel Rodero wrote:
>
> > Why? Bec
Hi all,
SOLVED!
If I use the 'Administrator' local account the script ssh-host-config fails
when trying to chown the /etc/ssh* files.
But, if I use the 'Administrator' domain account then the script works (i.e.
this user can chown the files to the SYSTEM account). The only thing this
domain acco
, printers,
registry keys, services, processes, and threads.
Default setting: Administrators.
So, I don't know why the new files created by ssh-host-config can be changed
to be owned by SYSTEM...
Any idea?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] O
>
> Because your are bound by the laws of ntfs access control
> entrys. Having rights to write to a file doesn't mean you are
> allowed to change its owner. You need permissions to change
> the directory the files are in.
> And getting this right is easier in windows than in cygwin.
> Use cacls
en these 4 servers is that 2 of them are Domain Controllers and the
other 2 are members of this domain. In the servers where the ssh-host-config
script works perfectly all of them are standalone servers.
So the question is: Why the Administrator can't change/chown the owner of
the /etc/ssh* files
5 matches
Mail list logo
