Corinna Vinschen writes:
> What exactly doesn't work? If it's the ownership of the dirs and
> files, chown will do the trick, no?
Well, the whole Cygwin directory is owned by an administrative domain
account, so unless I can tell sshd that this account is the equivalent
of root it will always
On Apr 9 12:59, Corinna Vinschen wrote:
> On Apr 9 09:52, Corinna Vinschen wrote:
> > The problem on Cygwin is that we don't have a fixed uid owning the
> > entire system paths. It always depends on the account used to create
> > the system dirs, which can vary from installation to
On Apr 9 09:52, Corinna Vinschen wrote:
> On Apr 6 22:37, Achim Gratz wrote:
> >
> > I've got a new server for Cygwin @work and wanted to get the sshd to run
> > with StrictMode on (it's been off on the old server). Long story short,
> > some accounts used for administrative tasks are
On Apr 6 22:37, Achim Gratz wrote:
>
> I've got a new server for Cygwin @work and wanted to get the sshd to run
> with StrictMode on (it's been off on the old server). Long story short,
> some accounts used for administrative tasks are contrained so that I
> need to store the authorized_keys
I've got a new server for Cygwin @work and wanted to get the sshd to run
with StrictMode on (it's been off on the old server). Long story short,
some accounts used for administrative tasks are contrained so that I
need to store the authorized_keys file directly on the server, so I
added
