On 2019-03-07 01:53, Corinna Vinschen wrote:
> On Mar 6 23:15, Brian Inglis wrote:
>> On 2019-03-06 13:59, Corinna Vinschen wrote:
>>> I'm reasonably sure there won't be any fix for these systems for at
>>> least two reasons:
>>> - All affected systems are EOLed or in the last year of their Extend
On Mar 6 23:15, Brian Inglis wrote:
> On 2019-03-06 13:59, Corinna Vinschen wrote:
> > I'm reasonably sure there won't be any fix for these systems for at
> > least two reasons:
> > - All affected systems are EOLed or in the last year of their Extended
> > Support Cycle, all ending on 2020-01-14
On 2019-03-06 13:59, Corinna Vinschen wrote:
> I'm reasonably sure there won't be any fix for these systems for at
> least two reasons:
> - All affected systems are EOLed or in the last year of their Extended
> Support Cycle, all ending on 2020-01-14.
> - I opened a support case for an older Wind
On Wed, Mar 06, 2019 at 03:44:36PM -0800, Stephen Paul Carrier wrote:
> PW=`dd if=/dev/random bs=15 count=1 | base 64`
That should be 'base64' of course, without the space.
--S
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On Wed, Mar 06, 2019 at 02:24:59PM -0700, Bill Stewart wrote:
...
> For my part, I'm writing a PowerShell script that does the following:
>
> 1) Create a local user account
> 2) Grant it SeBatchLogonRight
> 3) Create a scheduled task for it
Powershell is probably more elegant if you're familia
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" (SeBatchLogo
On Mar 6 13:47, Bill Stewart wrote:
> 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
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 alr
On Mar 6 09:45, Bill Stewart wrote:
> 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
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 nice.
> > > >
> > > > - On Vista an
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 ot
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 nice.
> > >
> > > - On Vista and Windows 7 WOW64, MsV1_0S4ULogon isn't implemented
> > > at all,
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 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
> available
>
> - On Vista and Windows 7 MsV1_0S4ULogon does not
On Mar 6 13:48, Corinna Vinschen wrote:
> On Mar 6 13:11, Corinna Vinschen wrote:
> > On Mar 5 17:02, Stephen Carrier wrote:
> > > Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
> > > fail unless some user logs into Windows first. In this case, that is by
> > > RDP,
On Mar 6 13:11, Corinna Vinschen wrote:
> On Mar 5 17:02, Stephen Carrier wrote:
> > Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
> > fail unless some user logs into Windows first. In this case, that is by
> > RDP, and it doesn't need to be the same user as the one
On Mar 5 17:02, Stephen Carrier wrote:
> Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
> fail unless some user logs into Windows first. In this case, that is by
> RDP, and it doesn't need to be the same user as the one logging in by ssh.
> After logging out of the win
Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
fail unless some user logs into Windows first. In this case, that is by
RDP, and it doesn't need to be the same user as the one logging in by ssh.
After logging out of the windows-native session, ssh continues to work.
Win
18 matches
Mail list logo
