I installed the OpenSSH server as a service using ssh-host-config, and all
is working.
I'm running Windows 10 (1803).
I renamed the sshd privilege separation (privsep) account to something else
and restarted the sshd service.
Everything still works - no errors.
Is the sshd disabled user
Hello,
Any plans to update rsync to version 3.1.3?
https://download.samba.org/pub/rsync/src/rsync-3.1.3-NEWS
Above indicates version 3.1.3 has some security fixes and enhancements.
Regards,
Bill
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Greetings,
/usr/share/doc/csih/ChangeLog has the following note for 2015-04-02:
* cygwin-service-installation-helper.sh
(csih_create_privileged_user): Also add SeDenyInteractiveLogonRight to the
service user. otherwise it will be shown on the logon screen in some
versions of Windows.
>From this
On Thu, Jan 24, 2019 at 1:23 PM Corinna Vinschen
wrote:
> I should have tested pubkey auth as well but as it was I just tested
> with pathword auth. These methods take slightly different paths in
> Cygwin when trying to switch the user account.
>
> I pushed another patch and created new
On Mon, Jan 28, 2019 at 2:59 AM Corinna Vinschen
wrote:
> Can you please test again with the latest snapshot from
> https://cygwin.com/snapshots/? The new S4U authentication method
> used in this snapshot automatically applies the Windows account rules so
> in my testing the patch I applied
On Mon, Jan 28, 2019 at 9:52 AM Corinna Vinschen
wrote:
>
> On Jan 28 08:02, Bill Stewart wrote:
> > On Mon, Jan 28, 2019 at 2:59 AM Corinna Vinschen
> > wrote:
> >
> > > Can you please test again with the latest snapshot from
> > > https://cygwin.c
On Fri, Mar 29, 2019 at 4:00 AM Corinna Vinschen wrote:
> > On 2019-03-28 15:36, Bill Stewart wrote:
> > I am trying to understand the limitations when running sshd using the
> > SYSTEM account.
> >
> > Is the following complete and correct?
> >
> >
It seems it would be useful to have a hostname token for use in the
sshd_config file.
Example usage (supposing %H expands to the hostname):
AllowGroups "%H+SSH Users"
This would permit access on the local computer (no matter its name) if the
account is a member of the SSH Users group (if it's a
I am trying to understand the limitations when running sshd using the
SYSTEM account.
Is the following complete and correct?
==
OS_version* OS_bitness sshd_bitness Notes
--
< 6.364-bit 32-bitNote 1
< 6.3
On Mon, Mar 4, 2019 at 9:39 AM Corinna Vinschen wrote:
> I reverted the entire patchset and uploaded new developer snapshots
> to https://cygwin.com/snapshots/.
>
> Incidentally, Microsoft's OpenSSH port calls LoadUserProfile, but it
> never calls UnloadUserProfile. I guess they know why.
>
> It
On Thu, Feb 14, 2019 at 9:04 AM Bill Stewart wrote:
> From an OpenSSH perspective, IMO, it would seem that the most
> straightforward solution would be, if possible, for sshd to ignore
> username case for incoming connections when it's running on Windows.
Any chance for a fix i
On Wed, Feb 20, 2019 at 11:53 AM scowles wrote:
> i can confirm the same behaviours on a 3.0.0 system. i've done several checks
> and have been unable to find the source of the problem. ssh -vvv shows that
> the
> connection proceeds all the way through the connection process, sends the
>
On Wed, Mar 6, 2019 at 8:34 AM Corinna Vinschen wrote:
> > What precisely happens when Cygwin uses MSV1 S4ULogon on versions older
> > than 6.3 before a user has logged on?
>
> MsV1S4ULogon returns with STATUS_NOT_SUPPORTED. Funny status code,
> given it works if some user already logged in by
On Wed, Mar 6, 2019 at 7:34 AM Corinna Vinschen wrote:
> On Mar 6 15:17, Corinna Vinschen wrote:
> > But the old Systems like Windows 7 don't want to play nice.
> >
> > - On Vista and Windows 7 WOW64, MsV1_0S4ULogon isn't implemented
> > at all, which required to keep the create_token method
>
On Wed, Mar 6, 2019 at 8:34 AM Corinna Vinschen wrote:
> On Mar 6 08:38, Bill Stewart wrote:
> > On Wed, Mar 6, 2019 at 7:34 AM Corinna Vinschen wrote:
> > > On Mar 6 15:17, Corinna Vinschen wrote:
> > > > But the old Systems like Windows 7 don't want to play ni
On Wed, Mar 6, 2019 at 1:14 PM Corinna Vinschen wrote:
> > > > What precisely happens when Cygwin uses MSV1 S4ULogon on versions
older
> > > > than 6.3 before a user has logged on?
> > >
> > > MsV1S4ULogon returns with STATUS_NOT_SUPPORTED. Funny status code,
> > > given it works if some user
On Wed, Mar 6, 2019 at 2:00 PM Corinna Vinschen wrote:
> > Whether this workaround is feasible likely depends on the end user. The
> > workaround has its own limitations. Here are at least 2 that I can
think of
> > right now:
> >
> > 1. The local user must have "Log on as a batch job"
On Fri, Feb 22, 2019 at 2:36 AM Corinna Vinschen wrote:
> The case-insensitivity patch has been accepted now so the upcoming
> OpenSSH 8.0 will allow case-insensitive user and group names.
This is greatly appreciated - thank you!
Bill
--
Problem reports: http://cygwin.com/problems.html
On Wed, Feb 20, 2019 at 1:25 PM Corinna Vinschen wrote:
> Sorry guys, but I can't reproduce this problem at all. I tested ssh
> login on Vista, W7 and W10 1809, in each case on 64 bit and under
> WOW64. On all systems I can login with domain as well as local
> accounts.
>
> For completeness
On Tue, Mar 12, 2019 at 8:02 PM David Dombrowsky wrote:
> > Surely you don't mean they have a plain-text copy of your password?
>
> If only I were kidding. Security through Oblivity :)
(?!) There is no reason that anyone else should have your password.
This means (among other things) that
On Tue, Mar 12, 2019 at 6:19 PM David Dombrowsky wrote:
> For me, this is acceptable risk since this is a single user machine and
> the administrators of the domain already know my domain password :)
I hope you really mean that they can _reset_ your domain password if needed?
Surely you don't
On Wed, Mar 13, 2019 at 2:57 AM Corinna Vinschen wrote:
> > a) Why is it necessary to specify SYSTEM as user number 0 in the
> > /etc/password file?
> >
> > b) Why is the sshd account required?
>
> sshd checks for uid 0 and requires the sshd account when chroot is
> requested.
>
> > c) Why are
On Wed, Mar 13, 2019 at 9:29 AM Corinna Vinschen wrote:
> > However: It's still the case that the user cannot bypass OS security
even
> > if he or she "escapes" from the jail, right?
> >
> > My goal is to restrict sftp browsing on the client side.
> >
> > Using ChrootDirectory with "ForceCommand
On Wed, Mar 20, 2019 at 8:53 AM Bruce Halco wrote:
> The problem is I have 8 customers failing PCI network scans because of
> CVE-2019-6111, so I don't think the patch for CVE-2018-20685 is going to
> help.
>
> If 8.0 is close (maybe weeks?) I can afford to wait a while. Otherwise
> I'll have to
On Thu, 17 Jan 2019 Corinna Vinschen wrote:
> > Is the sshd disabled user account still required?
>
> No, actually it isn't. These days the sshd server checks if the
> the privsep chrrot environment should be used and that the process
> is started under "root:root". This never matches under
On Thu, Feb 28, 2019 at 2:39 AM Corinna Vinschen wrote:
> > Since windows seems to adhere to the rule:
> > "Case preserving", but "case ignoring", what does it
> > mean to make sure all user and group names are
> > case-correct?
>
> This all started here:
>
On Thu, Mar 21, 2019 at 9:58 AM Garber, Dave (BHGE, Non-GE) wrote:
> But Windows command 'wmic process get name, creationdate' in a
non-elevated command prompt also works. So it looks like it should be
possible.
This might be because WMIC uses WMI which runs as a system service (which
runs as
Good day,
I am testing sshd using the cygwin1.dll 3.x version (run as SYSTEM -
S4U logon - works great!).
One thing I've noticed is that if I use ssh log onto a remote
domain-joined machine (e.g., connect with COMPUTER+localname), the
'COMPUTER' prefix must be uppercase - if I specify
On Wed, Feb 13, 2019 at 9:10 AM Corinna Vinschen
wrote:
> This can't work correctly with OpenSSH. The decision to allow only
> the correct case in OpenSSH was made back in 2010, because otherwise
> we would need a lot of special rules in OpenSSH just for Cygwin.
> Sorry, but that's how it is.
On Wed, Feb 13, 2019 at 1:25 PM Corinna Vinschen
wrote:
> > (a) Domain or computer name portion to the left of the "+" must always
> > be uppercase
>
> No, the case must match the case of the domain or computername.
>
> > (b) Username after "+" sign (or username alone, without "+" sign) must
> >
On Wed, Feb 13, 2019 at 10:56 AM Corinna Vinschen
wrote:
> The complete string "domain+samaccountname" is the Cygwin username,
> see the output of `getent passwd ' The entire Cygwin username
> should always use the same case, otherwise case sensitive pattern
> matching on the name returned in the
On Thu, Feb 14, 2019 at 6:14 AM Corinna Vinschen wrote:
> > From this reference, it seems that a POSIX-compliant username cannot
> > contain the + character?
>
> *should*, not *must*. It may be a portabiliy problem but it's not
> strictly disallowed. I'm also not sure what this has to do with
On Thu, Feb 14, 2019 at 6:43 AM Bill Stewart wrote:
> I think this is the difficulty: When a computer name is not uppercase,
> how do we find out the correct case when we specify an authority name
> (before the +)?
Upon reflection, here's what comes to mind from a purely Cygwin pe
On Thu, Feb 14, 2019 at 12:49 PM Eric Blake wrote:
> Depending on the shell, ~ is expanded to $HOME prior to invoking a
> program. But if you want to take the shell's expansions out of the
> equation, you could use:
>
> cygpath -w "$HOME"
Ah. I'm not using a Cygwin shell (PowerShell actually).
According to this:
https://stackoverflow.com/questions/42841907/
cygpath -w ~
...formerly produced to stdout the home directory path for the current user.
This seems not be the case any more: When I run cygpath -w ~, I get just ~.
Is this by design? If so, what's the way to programmatically
On Thu, Feb 14, 2019 at 2:15 PM Eric Blake wrote:
> If you want tilde-expansion to happen, you have to use a shell that does
> tilde-expansion. bash and dash do, PowerShell does not. It is not
> cygpath's fault, but your choice of shell, that determines whether ~ is
> expanded. And, since the
On Wed, Feb 13, 2019 at 9:26 AM Corinna Vinschen
wrote:
> No, that was a bug. With case insenitive usernames, the pattern
> matching in OpenSSH won't work and you create a potential security
> problem.
I see - interoperability issue.
Therefore it becomes imperative on the Windows side to match
On Wed, Feb 13, 2019 at 5:25 AM Corinna Vinschen
wrote:
> > sshd checks usernames case-sensitive against their name stored in the
> > user DB. The problem that you can use differently cased usernames
> > here is that the Windows function for checking the name is case-
> > insensitive, so it
On Fri, Feb 15, 2019 at 2:32 AM Sam Edge (Cygwin) wrote:
> https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-how explains
> in more detail.
I had already read that, and it seems to indicate that it asks the
local machine first, but that doesn't seem to be happening when
there's a
On Fri, Feb 15, 2019 at 9:38 AM Corinna Vinschen wrote:
> There's a documented ruleset which is strictly followed
> https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-how:
>From that reference, we have the following order:
* Well-known SIDs in the NT_AUTHORITY domain of the S-1-5-RID
See https://cygwin.com/ml/cygwin/2019-02/msg00184.html
cygcheck.out attached.
Regards,
Bill
cygcheck.out
Description: Binary data
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
On Fri, Feb 15, 2019 at 4:50 AM Andrey Repin wrote:
> Not as good as bash. Just so you know.
We'll just agree to disagree on that (particularly on Windows).
> Setup your system to use %USERPROFILE% as $HOME and forget this problem
> altogether.
> For interoperability's sake! (q)
That won't
On Fri, Feb 15, 2019 at 9:14 AM Takashi Yano wrote:
> If you don't want to use "shell", you can:
> c:/cygwin/bin/cygpath -w $(c:/cygwin/bin/getent passwd $env:USERNAME |
> c:/cygwin/bin/cut -d: -f6)
> but I'm not sure if you think this is "awkward" as well.
Why cut if you are already using
On Fri, Feb 15, 2019 at 1:29 PM Corinna Vinschen wrote:
> you didn't really read it. Try again.
Can you be more specific?
Bill
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
On Fri, Feb 15, 2019 at 2:38 PM Brian Ingliswrote:
> Windows normally allows "." to be used to refer to the local machine name in a
> domain context - can anyone confirm or deny whether this works in Cygwin or
> with
> getent?
AFAICT, the "." shortcut does not work in Cygwin.
Regards,
Bill
On Fri, Feb 15, 2019 at 2:32 PM Corinna Vinschen wrote:
> What is a "typical" order?!?
>
> If you login locally to a domain member machine the default domain is
> the logon domain of this machine. If that's not what you want you have
> to choose the logon domain of your account explicitely, even
On Fri, Feb 15, 2019 at 1:43 PM Corinna Vinschen wrote:
> More specific as the original text? I'm hard pressed to accomplish
> that. Take note of the "domain member machine" property.
I think I see the problem. The list I posted (above the one you are
apparently referring to) has the search in
On Fri, Feb 15, 2019 at 2:32 PM Corinna Vinschen wrote:
> > The section that starts with "Let's discuss the SID<=>uid/gid mapping
> > first. Here's how it works." states this order:
>
> It doesn't state an order. It describes the mapping from SID to
> uid/gid, and there's *no* order at all to
On Thu, Feb 14, 2019 at 3:14 PM Vince Rice wrote:
> There is -- use a cygwin shell. As Eric has already explained, expansion is
> the
> shell's responsibility. Powershell doesn't do it. If you want expansion, use
> one
> that does.
So let's consider, for a bit, that not everybody uses a Cygwin
On Thu, Feb 14, 2019 at 4:57 PM Vince Rice wrote:
> Here, you say "forget about the ~ character." We can't "forget" about the
> tilde. This whole
> conversation is about the tilde, specifically tilde expansion.
Eric Blake seems to have understood (see his response if it's still unclear).
On Thu, Feb 14, 2019 at 4:32 PM Vince Rice wrote:
> I didn't suggest everyone did. But people who want tilde expansion do,
> because it's
> the shell that is responsible for tilde expansion.
> ...
> No, it isn't "oddly" absent. As has been said repeatedly in this thread,
> tilde expansion
> is
Consider the case where you have a local account and a domain account
with the same username.
If you supply just the username to Windows without an authority name,
Windows returns the local account. To get the domain account, you'd
have to specify an authority (e.g. domain\username).
It seems
On Fri, Feb 15, 2019 at 3:48 PM Bill Stewart wrote:
> This means that when I test getent using the name "Admin", Cygwin
> finds the domain group:
>
> PS C:\> getent -w passwd admin
> admin::DOMAINNAME\admin:S-1-5-21-nn-n-n-nn
>
On Fri, Feb 15, 2019 at 11:09 PM L A Walsh wrote:
> Vince, I think What Bill is trying to ask is how does
> the cygwin shell might do it (answer: look at the source! ;-)).
Or rather more succinctly: "Cygwin, what is the path to the current
user's home directory?"
IMO it would be simpler for
On Tue, Feb 19, 2019 at 8:47 AM Bill Stewart wrote:
> (a) Is this correct?
>
> (b) Is there a particular reason this order was chosen (instead of
> local first, then domain, i.e., the usual Windows order)?
Please disregard. I forgot the reason was to have the same behavior as
the W
On Tue, Feb 19, 2019 at 12:28 PM John Oxley wrote:
> I started off with PowerShell but re-wrote to schtasks to make this post
> shorter. Exactly the same thing happens:
>
> > Register-ScheduledTask -TaskName $taskName -Action $action -Trigger
> > $trigger -RunLevel Highest -User foo -Password
On Tue, Feb 19, 2019 at 12:02 PM John Oxley wrote:
> I'm running a Windows 10 VM with a fairly recent installation of Cygwin (last
> month or so).
>
> If I ssh into the box as the user "foo", I cannot create a scheduled task for
> the user:
>
> foo@host $ schtasks /create /ru foo /rp
On Tue, Jan 29, 2019 at 10:05 AM Corinna Vinschen
wrote:
> Please try the snapshots I just uploaded to https://cygwin.com/snapshots/
> They should fix the problem. It turned out that I restricted the
> permissions of processes too much for Windows 7. The same code works
> fine since Windows 8.
On Mon, Jan 28, 2019 at 11:39 AM Corinna Vinschen
wrote:
> Along these lines I have an OpenSSH patch in the loop which reverts
> the ssh-host-config script back to using the SYSTEM user, just as
> in the olden Windows XP days. I'll send it upstream as soon as
> Cygwin 3.0 is officially
On Mon, Jan 28, 2019 at 1:14 PM Bill Stewart wrote:
> Thank you. I wanted to point out that I have not had a chance to test
> using a non-domain computer yet. I will try that scenario as well.
Hi Corinna,
I unjoined a Windows 7 machine from the domain and tested as follows:
1. Ran
On Mon, Jan 28, 2019 at 2:49 PM Bill Stewart wrote:
> I unjoined a Windows 7 machine from the domain and tested as follows:
>
> 1. Ran setup and installed cygwin
>
> 2. Ran sshd-host-config and answered "no" to install as service
>
> 3. Installed service using this
On Fri, Jan 25, 2019 at 3:36 AM Stefan Baur wrote:
> Not on Linux (and possibly other Unices). There, it's perfectly valid
> to disable an account's password login (both locally and remote), but to
> at the same time allow ssh key file based logins for the same account.
But disabling _password
On Fri, Jan 25, 2019 at 10:48 AM Stephen Paul Carrier
wrote:
> There are different paths to access and to completely disable the account
> you need to close all of them. There are many reasons to disable some
> paths without disabling all paths and converting the switch that can
> disable one
I am running Windows 10 (1803) and experimenting with sshd installed as a
Windows service.
The computer is a domain member. I created a local computer account for
testing.
I created host keys and a public/private key pair to use to log on the user.
This works, except I notice that if I disable
account.
Thanks,
Bill
On Thu, Jan 24, 2019 at 8:45 AM Corinna Vinschen
wrote:
> On Jan 24 06:28, Bill Stewart wrote:
> > I am running Windows 10 (1803) and experimenting with sshd installed as a
> > Windows service.
> >
> > The computer is a domain member. I creat
Hello,
Are there any plans to update rsync to version 3.1.3 any time soon?
https://download.samba.org/pub/rsync/src/rsync-3.1.3-NEWS
Above indicates version 3.1.3 has some security fixes and enhancements.
Regards,
Bill
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Corinna Vinschen wrote:
> This description sounds extremly artificial to me. We should work under
the
> assumption that the admin is the good guy. Usually a user locks itself
out,
> or is locked out by a malicious login attempt. The admin can only define
> rules for locking out, other than
On Thu, Jan 24, 2019 at 10:58 AM Stefan Baur wrote:
That sounds like the total opposite - allowing login without a password.
>
> Now, if there was a flag PASSWD_NOTPERMITTED or something like that,
> then we'd be able to emulate what can be done on Linux with "passwd -l
> username" and an ssh
It's here:
https://lists.mindrot.org/pipermail/openssh-unix-dev/2019-April/037747.html
Looking forward to using the latest version in Cygwin now that it has
case-insensitive account name matching.
Thank you, Cygwin maintainers (Corinna, et al.), for all you do for the
community!
Bill
--
On Mon, Mar 11, 2019 at 3:38 PM Achim Gratz wrote:
> Try it with a group that has several hundred members. Then try with
> several hundreds of such groups. Then try it again over a DSL line or
> some VPN routing you across the globe that has a roundtrip measured in
> tenths of seconds.
On Mon, Jun 10, 2019 at 2:13 PM Chris Wagner wrote:
> I didn't know about run, thanks for the tip. However when I use it to
> launch something from the Start Menu Run command, it still pops open a
> terminal window of some kind for a fraction of a second. I'm on Windows
> 7.
I wrote a little
On Thu, May 9, 2019 at 6:20 AM Andrey Repin wrote:
> Again, there's simply no equivalent of "god user" from *NIX in Windows
> permissions system.
That's not really correct. An account that is a member of the
Administrators local group (localized name can be different, SID is
S-1-5-32-544) is a
On Sun, May 12, 2019 at 8:31 AM L A Walsh wrote:
> This has been a feature of Windows since win98. Not officially, mind
> you, but any scheduled task in windows would eventually become
> unscheduled and stop running with out any notification.
I've never seen this behavior on any Windows machine
On Thu, Apr 18, 2019 at 8:46 AM Corinna Vinschen wrote:
> I know, I'm subscribed to the openssh-dev mailing list.
Understood - the intent was to inform those subscribed to the Cygwin list
who might not know already that there's something good to look forward to.
My apologies for any annoyance.
e useful:
https://github.com/Bill-Stewart/Cygwin-OpenSSH
Bill
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
On Tue, Aug 6, 2019 at 10:25 AM Corinna Vinschen wrote:
> https://en.wikipedia.org/wiki/Environment_variable#Windows claims that
> "The %SystemDrive% variable is a special system-wide environment
> variable found on Windows NT and its derivatives. Its value is the drive
> upon which the system
On Tue, Aug 6, 2019 at 9:53 AM Corinna Vinschen wrote:
> How so? SYSTEMDRIVE is the drive SYSTEMROOT is installed on, no?
https://support.microsoft.com/en-us/help/314470/
"The system volume refers to the disk volume that contains the
hardware-specific files that are needed to start Windows,
On Tue, Aug 6, 2019 at 9:42 AM Corinna Vinschen wrote:
>
> On Aug 6 17:20, Michael Haubenwallner wrote:
> > Now what I've failed to find is how to query the value for the "SystemDrive"
> > environment variable.
>
> Just strip it off SYSTEMROOT?
IIRC, that will not give the expected value if
On Sun, Feb 23, 2020 at 3:33 AM jinsu mathew wrote:
I've setup Cygwin and want to ssh with domain user account on windows
> server 2012 R2. It works fine if I start the sshd service with "Local
> system account" but if I start the service with a "cygserver" local account
> or "domain\cygserver"
I have updated the package:
https://github.com/Bill-Stewart/Cygwin-OpenSSH
Installer is available on the 'Releases' tab.
Description:
Cygwin-OpenSSH is a convenient packaging of the Cygwin version of OpenSSH
for Windows systems.
Notable changes:
- Updated OpenSSH to version 8.2
- Updated
On Wed, Mar 4, 2020 at 6:32 AM Jon Turney wrote:
> If a package is listed for both -x and -P, it is reinstalled, so while
> not ideal, you might be able to achieve something like what you want
> with 'setup -I -x "package1,package2,package3" -P
> "package1,package2,package3"'
This does what I
On Mon, Mar 2, 2020 at 11:08 PM Robert McBroom wrote:
Details in attached file
Hint: When asking for help in a mailing list, the less effort respondents
have to go through, the better.
It is better to put your information directly in the message rather than
attaching a file.
(Why attach a
I would like to reinstall a set of packages and automatically install the
source for only those packages.
The packages are currently installed, and I am using a Setup command line
like this:
-I -P "package1,package2,package3"
The description in --help for -I states "Automatically install
On Wed, Feb 26, 2020 at 11:47 PM ASSI wrote:
You will perhaps want to read the Cygwin licensing terms
> plus the licensing terms of each of the packages you distribute.
>
The relevant licenses are provided as links in the installer and referenced
in the User's Guide.
Bill
--
Problem reports:
On Thu, Feb 27, 2020 at 3:31 PM Brian Inglis wrote:
No, you must backport all sources to the current and all previous versions
> and
> redistribute, or at least make them visible and available on your site,
> otherwise you are in breach of the licence and must withdraw all
> distributions
>
I
On Thu, Feb 27, 2020 at 4:10 PM TestUser1 wrote:
So is this expected to work fine in my environment, Windows Server 2016 (OS
> Version 10.0.14393), without the workaround?
>
I can't reproduce on Windows Server 8.1/Server 2012 R2 or later.
But you can certainly try the workaround.
Bill
--
On Thu, Feb 27, 2020 at 11:09 AM n0nc3 wrote:
It appears Cygwin SSHD's functionality is partially broke in the later
> versions, where SSHD runs as SYSTEM (no longer cyg_server).
>
> On reboot, any attempt to SSH into the server *before* any previous logon
> attempt (RDP/locally/etc) is quickly
On Thu, Feb 27, 2020 at 11:52 AM Achim Gratz wrote:
But more to the point: since you include GPL components, a binary-only
> distribution is not OK. The sources for at least the GPL licensed
> utilities and libraries is missing. It's not enough to say what these
> are and roughly where to get
On Mon, Jan 27, 2020 at 9:19 AM Bill Stewart wrote:
> > Any ideas why Restart Manager doesn't work for cygrunsrv services?
> ...
> Question also posted on StackOverflow:
>
> https://stackoverflow.com/questions/59902201/
>
> Any insights appreciated.
Accor
On Sun, Jan 26, 2020 at 9:33 PM aimedtech wrote:
> Okay, this is a complaint. I've spent the past few days trying to download
> the Cygwin system and gotten nowhere. I've tried several download
> environments, using different protocols, nothing works.
Remember that we can't see your screen.
Thank you for the assistance!
I released the latest version of my installer, now available (under
"Releases" tab) here:
https://github.com/Bill-Stewart/Cygwin-OpenSSH
Bill
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Doc
I have created an OpenSSH installer for Windows users:
https://github.com/Bill-Stewart/Cygwin-OpenSSH
Basically it includes only the minimum files from Cygwin needed to run
OpenSSH and has some additional conveniences (the foremost of which is
to automatically install the service).
The problem
On Thu, Jan 30, 2020 at 9:46 AM Takashi Yano wrote:
> Bill Stewart wrote:
> >
> > When I use cygwin1.dll versions newer than 3.0.7, sshd.exe hangs
> > whenever establishing a connection.
> > ...
> > Any ideas?
>
> You need cygwin-console-helper.exe for n
On Thu, Jan 30, 2020 at 12:33 PM Bill Stewart wrote:
> I added cygwin-console-helper.exe and this resolved it, at least on
> Windows 10. My next step is to test on Server 2012 R2.
Tested, and works fine also on Server 2012 R2. Thanks for the help!
Bill
--
Problem reports:
Good day,
Application installers (such as Windows Installer or Inno Setup) can
use the Windows Restart Manager APIs[1] it to determine if a program
or service is running, and automatically stop/restart as appropriate.
This is useful when reinstalling or upgrading a service from an
installer, as
On Thu, Jan 23, 2020 at 10:44 AM Bill Stewart wrote:
> However it seems that when running a service using cygrunsrv, the
> Restart Manager RmGetList API[2] returns RmRebootReasonSessionMismatch
> (2) for the lpdwRebootReasons output parameter.
>
> This parameter retu
On Mon, Mar 9, 2020 at 4:09 PM Robert McBroom wrote:
> > Did you search the most obvious place for information?
> > https://cygwin.com/mirrors.html
> >
> That is the list of mirrors not a howto on becoming a mirror
That page formerly had a blurb at the bottom on how to become a
mirror. This
On Fri, Mar 6, 2020 at 3:04 PM Bill Stewart wrote:
> > As Takashi explained, there is no fix on the cygwin side. It could be
> > fixed on the Windows side, within the ConPTY API.
> > You could report it there...
>
> Thanks - found this:
>
> https://github.co
On Thu, Mar 5, 2020 at 8:52 AM Takashi Yano wrote:
> Thomas Wolff wrote:
> > With ConPTY support, the following command results in output that
> > contains an explicit newline at the auto-wrap position:
> > cmd /c echo a line which is wider than your terminal ...
> >
> > For copy/paste, this is
On Fri, Mar 6, 2020 at 1:43 PM Thomas Wolff wrote:
> > With disable_pcon set:
> >
> > echo "$PATH" -- wraps correctly
> > cmd /c echo %PATH% -- wraps correctly
> > winpty cmd /c echo %PATH% -- wrapping broken
> >
> > Without disable_pcon set:
> >
> > echo "$PATH" -- wraps
1 - 100 of 182 matches
Mail list logo
