On Tue, Apr 11, 2023 at 6:28 PM Philippe Cerfon via Cygwin
wrote:
> I've just wondered whether Cygwin packages could be changed to
> place/expect any SSH config files in /etc/ssh, just as virtually any
> Linux distribution seems to do? :-)
Symlinks are your friend. You can even use
Hey.
I've just wondered whether Cygwin packages could be changed to
place/expect any SSH config files in /etc/ssh, just as virtually any
Linux distribution seems to do? :-)
Regards,
Philippe
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.co
>
> It's not perfect but I've always had trouble with all of the
> modifications Cygwin makes to a file's permissions to support
> POSIX-style ACLs. I do miss being able to manage them with chmod and
> setfacl though.
>
> For those wishing to set their ssh c
On 2017-11-04 12:25, Achim Gratz wrote:
> Matt D. writes:
>> It's not perfect but I've always had trouble with all of the
>> modifications Cygwin makes to a file's permissions to support
>> POSIX-style ACLs. I do miss being able to manage them with chmod and
>> setfacl though.
>
> Just remove any
Matt D. writes:
> It's not perfect but I've always had trouble with all of the
> modifications Cygwin makes to a file's permissions to support
> POSIX-style ACLs. I do miss being able to manage them with chmod and
> setfacl though.
Just remove any ACL inheritance on the home directory before popul
t I've always had trouble with all of the
> modifications Cygwin makes to a file's permissions to support
> POSIX-style ACLs. I do miss being able to manage them with chmod and
> setfacl though.
>
> For those wishing to set their ssh config to 600 (as recognized by
> Cygwin's
On 11/4/2017 12:37 PM, Corinna Vinschen wrote:
If your build does not show the same values, then I *bet*, your test
application is not using the same path as if you're using the coreutils
stat tool. Apparently they access the file via different mount points,
one of them "acl", the other "noacl".
o a file's permissions to support
POSIX-style ACLs. I do miss being able to manage them with chmod and
setfacl though.
For those wishing to set their ssh config to 600 (as recognized by
Cygwin's ssh), use the following:
Reset file permissions:
icacls config /t /q /c /reset
In
on't need ACLs for my purposes and prefer
> > > > > to
> > > > > leave everything up to Windows permissions.
> > > > >
> > > > > The problem with this is that ssh insists that ~/.ssh/config be less
> > > > > permis
Matt D. writes:
> This makes sense because Cygwin is pulling the NTFS permissions as
> there are no Cygwin ACLs defined.
>
> The only workaround is to use Window's Security diaglog to disable
> inherited permissions and remove the Users group. This does seem to
> satisfy things.
That's the correct
em with this is that ssh insists that ~/.ssh/config be less
permissive. But this file is bound to --rw-r--r-- for this option.
Would it be appropriate to request ssh to ignore this requirement when
"noacl" present on the mounted volume?
Yes, in theory. However, this shouldn't
On 11/4/2017 7:47 AM, Matt D. wrote:
On 11/4/2017 7:37 AM, Corinna Vinschen wrote:
On Nov 4 05:47, Matt D. wrote:
I mount with "noacl" as I don't need ACLs for my purposes and prefer to
leave everything up to Windows permissions.
The problem with this is that ssh insists tha
On 11/4/2017 7:37 AM, Corinna Vinschen wrote:
On Nov 4 05:47, Matt D. wrote:
I mount with "noacl" as I don't need ACLs for my purposes and prefer to
leave everything up to Windows permissions.
The problem with this is that ssh insists that ~/.ssh/config be less
permissive. B
On Nov 4 05:47, Matt D. wrote:
> I mount with "noacl" as I don't need ACLs for my purposes and prefer to
> leave everything up to Windows permissions.
>
> The problem with this is that ssh insists that ~/.ssh/config be less
> permissive. But this file is bound
I mount with "noacl" as I don't need ACLs for my purposes and prefer to
leave everything up to Windows permissions.
The problem with this is that ssh insists that ~/.ssh/config be less
permissive. But this file is bound to --rw-r--r-- for this option.
Would it be appropriate
; > command -- which works for me
> > 2. add "Host * KexAlgorithms +diffie-hellman-group1-sha1" to
> > ~/.ssh/config -- which does not work for me
> >
> > What's the trick for getting the KexAlgorithms param in ~/.ssh/config to
> work?
> >
>
heir offer: diffie-hellman-group1-sha1
>
> http://www.openssh.com/legacy.html has two work-arounds:
> 1. add "-oKexAlgorithms=+diffie-hellman-group1-sha1" to the ssh
> command -- which works for me
> 2. add "Host * KexAlgorithms +diffie-hellman-group1-sha1&qu
work-arounds:
1. add "-oKexAlgorithms=+diffie-hellman-group1-sha1" to the ssh
command -- which works for me
2. add "Host * KexAlgorithms +diffie-hellman-group1-sha1" to
~/.ssh/config -- which does not work for me
What's the trick for getting the KexAlgorithms param in ~/.s
Hi All...
From: Brian Dessent Subject: Re: ssh config
Date: Mon, 02 Jul 2007 15:23:05 -0700
René Berber wrote:
> What you did in ~/.ssh/config was add the parameter (-X) for the
specific host,
> that AFAIK cannot be done globally (unless globing is accepted in the
same
> co
René Berber wrote:
> What you did in ~/.ssh/config was add the parameter (-X) for the specific
> host,
> that AFAIK cannot be done globally (unless globing is accepted in the same
> config file).
Sure you can, the following in ~/.ssh/config:
Host = *
ForwardX11 = yes
ForwardX11T
used by X11.
> I found a way for me to do it via a ~/.ssh/config file but I'm looking
> for a way to do it globally. I have seen it (on Linux systems) in
> /etc/ssh/ssh_config before...I tried it on cygwin with no success.
> Does openssh on cygwin look for the global configurati
On Mon, 2 Jul 2007, Frederich, Eric P21322 wrote:
> Is there a way to enable X11 forwarding by default so that I don't have
> to run "ssh -XY hostname" and can just run "ssh hostname"?
> I found a way for me to do it via a ~/.ssh/config file but I'm looking
Is there a way to enable X11 forwarding by default so that I don't have
to run "ssh -XY hostname" and can just run "ssh hostname"?
I found a way for me to do it via a ~/.ssh/config file but I'm looking
for a way to do it globally. I have seen it (on Linux systems)
On Mon, Nov 03, 2003 at 10:40:43PM +0100, Corinna Vinschen wrote:
> I'm running a 2003 Server as standalone (non-domain) server. In that
> setting, password complexity is disabled by default, so I missed that one,
> too. Thanks for the heads up. I changed the password to SSHD_server,
> which see
On Mon, Nov 03, 2003 at 04:05:43PM -0600, DePriest, Jason R. wrote:
> User Accounts have a USER_FLAGS attribute that can be any combination of
> a couple of values. One of these can be UF_DONT_EXPIRE_PASSWORD. If it
> is present, the password never expires.
>
> I typically manipulate it using Da
On Mon, Nov 03, 2003 at 09:34:04PM -0500, Alan Dobkin wrote:
> I use Dave Roth's perl module for more complex user flag settings,
> but the hands down easiest way to do this is with the NET command:
>
> NET USER username /EXPIRES:NEVER
Unfortunately that's not right. I thought the same and used
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hallo,
I proceeded as described and sshd works according to /etc/passwd and
ntsec after starting manually in the environment listed below.
Regards, Alexander.
8< >8
$ cygcheck -sr
Cygwin Win95/NT
I use Dave Roth's perl module for more complex user flag settings,
but the hands down easiest way to do this is with the NET command:
NET USER username /EXPIRES:NEVER
This command is built-in on all Windows NT/2K/XP systems. For more
details see NET HELP USER.
Alan
--On Monday, November 03, 2003
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Corinna Vinschen
> Sent: Monday, November 03, 2003 3:41 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Take 2: Testers for new ssh-*-config scripts wanted!
[--]
> However, I have s
On Mon, Nov 03, 2003 at 06:51:04PM +0100, Philippe Torche wrote:
> Hi,
>
> 1. Line 488 (you will hate me !?) : read _cygwin --->>> read -e _cygwin
Uh, yes, I missed that one.
> 2. If password complexity is enabled (yes per default) use a more complex
> password : length of 7 min (max 14 to avoid
-Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> De la part de Corinna Vinschen
> Envoyé : lundi, 3. novembre 2003 17:22
> À : [EMAIL PROTECTED]
> Objet : Take 2: Testers for new ssh-*-config scripts wanted!
>
> Hi,
>
> I'd like t
Hi,
I'd like to ask for more testing of the new ssh-host-config and
ssh-user-config scripts.
The new thing here is, that the ssh-host-config script now tries to
figure out if the machine is a 2003 Server or newer system. If so,
the script asks, if it should create a new account "sshd_server"
to
On Mon, Nov 03, 2003 at 09:38:16AM +0100, Philippe Torche wrote:
> Sorry but,
>
> The doc of bash explains this behavior (help read). You can experiment the
> same think on Redhat per exemple. And don't forget to use "echo $_cygwin |
> od -t x1" to show what is stored in the variable.
I did, of c
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> De la part de Corinna Vinschen
> Envoyé : vendredi, 31. octobre 2003 18:24
> À : [EMAIL PROTECTED]
> Objet : Re: Testers for new ssh-*-config scripts wanted!
>
> On Fri, Oct 31, 2003 at 05:07:18PM +0100, Philippe Torche wr
On Fri, Oct 31, 2003 at 05:07:18PM +0100, Philippe Torche wrote:
> Nope,
>
> read from bash don't reconize control caracters without -e parameter:
> $ read _cygwin
> Ntser[Backspace]c
> $ echo $_cygwin | od -t x1
> 000 6e 74 73 65 72 08 63 0a
> 010
>
> BUT OK with "-e"
>
> $ read -e _cyg
5 63 0a
006
Thanks, Philippe.
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> De la part de Corinna Vinschen
> Envoyé : vendredi, 31. octobre 2003 12:08
> À : [EMAIL PROTECTED]
> Objet : RE: Testers for new ssh-*-config scripts wanted!
&
On Fri, Oct 31, 2003 at 09:55:04AM +0100, Philippe Torche wrote:
> Script ssh-host-config works for me, but when I've entered the CYGWIN env
> var, I've do a error and type "ntser", then backspace and then the correct
> "c" caracters.
> Thus CYGWIN key in the registry has now "ntser\x08c" instead o
aused by the read command!
Thanks.
PS Wait for a "Windows 2003 Server" version
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> De la part de Corinna Vinschen
> Envoyé : jeudi, 30. octobre 2003 18:11
> À : [EMAIL PROTECTED]
>
Sent: Thursday, October 30, 2003 5:35 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Testers for new ssh-*-config scripts wanted!
>
>
> On Thu, 30 Oct 2003, Harig, Mark wrote:
>
> > I have OpenSSH 3.7.1p2-1 installed, but I
> > do not have the 'ssh_config'
On Thu, 30 Oct 2003, Harig, Mark wrote:
> I have OpenSSH 3.7.1p2-1 installed, but I
> do not have the 'ssh_config' or 'sshd_config'
> template files that the 'ssh-host-config' script
> expects. Am I missing a step here that I should
> have taken to generate these files?
>
Yes, see:
> Corinna Vin
PM
> To: [EMAIL PROTECTED]
> Subject: Testers for new ssh-*-config scripts wanted!
>
>
> Hi,
>
> is anybody here willing to give my new ssh-host-config and
> ssh-user-config
> shell scripts a thorough test? I tested them by myself but I
> have this
> nagging f
; -Original Message-
> From: Corinna Vinschen [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 30, 2003 12:11 PM
> To: [EMAIL PROTECTED]
> Subject: Testers for new ssh-*-config scripts wanted!
>
>
> Hi,
>
> is anybody here willing to give my new ssh-ho
Hi,
is anybody here willing to give my new ssh-host-config and ssh-user-config
shell scripts a thorough test? I tested them by myself but I have this
nagging feeling I missed something important.
The important changes:
- On NT, try to set permissions on files and directories to a useful value.
43 matches
Mail list logo
