On May 8 19:17, Robert Pendell wrote:
> On Thu, May 8, 2014 at 4:09 PM, Corinna Vinschen wrote:
> > I created a new snapshot on http://cygwin.com/snapshots/ which
> > introduces the following behaviour, which is a bit less intrusive:
> >
> > If a local account is connected to a Microsoft Account,
Ken Brown cornell.edu> writes:
> This doesn't happen if you install the snapshot by the method suggested
> in the FAQ:
>
>http://cygwin.com/faq.html#faq.setup.snapshots
>
Or just make a package out of the snapshot and then install it via setup:
--8<---cut here---st
On Thu, May 8, 2014 at 8:12 PM, Ken Brown wrote:
> On 5/8/2014 7:17 PM, Robert Pendell wrote:
>>
>> On Thu, May 8, 2014 at 4:09 PM, Corinna Vinschen wrote:
>>>
>>> On May 7 16:46, Corinna Vinschen wrote:
On May 7 10:09, Chris J. Breisch wrote:
>
> Corinna Vinschen wrote:
>>
On 5/8/2014 7:17 PM, Robert Pendell wrote:
On Thu, May 8, 2014 at 4:09 PM, Corinna Vinschen wrote:
On May 7 16:46, Corinna Vinschen wrote:
On May 7 10:09, Chris J. Breisch wrote:
Corinna Vinschen wrote:
And here's a problem which I'm not sure how to solve at all:
When calling the latest mk
On Thu, May 8, 2014 at 4:09 PM, Corinna Vinschen wrote:
> On May 7 16:46, Corinna Vinschen wrote:
>> On May 7 10:09, Chris J. Breisch wrote:
>> > Corinna Vinschen wrote:
>> > >And here's a problem which I'm not sure how to solve at all:
>> > >
>> > >When calling the latest mkpasswd, the primary g
On May 7 16:46, Corinna Vinschen wrote:
> On May 7 10:09, Chris J. Breisch wrote:
> > Corinna Vinschen wrote:
> > >And here's a problem which I'm not sure how to solve at all:
> > >
> > >When calling the latest mkpasswd, the primary group of the local
> > >user account backing the Microsoft Accou
On May 7 10:09, Chris J. Breisch wrote:
> Corinna Vinschen wrote:
> >And here's a problem which I'm not sure how to solve at all:
> >
> >When calling the latest mkpasswd, the primary group of the local
> >user account backing the Microsoft Account will *still* be "None".
> >
> >The reason is that
On May 7 16:20, Corinna Vinschen wrote:
> On May 7 17:53, Andrey Repin wrote:
> > Greetings, Corinna Vinschen!
> >
> > > I toyed around with the Microsoft Account a bit more. And here's why
> > > the primary group SID being identical to the user SID is not a good
> > > idea:
> >
> > > Securi
On May 7 10:05, Chris J. Breisch wrote:
> Corinna Vinschen wrote:
> >I toyed around with the Microsoft Account a bit more. And here's why
> >the primary group SID being identical to the user SID is not a good
> >idea:
> >
> > Security checks.
> >
> >For instance:
> >
> > $ echo $USER
> > VM
On May 7 17:53, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> > I toyed around with the Microsoft Account a bit more. And here's why
> > the primary group SID being identical to the user SID is not a good
> > idea:
>
> > Security checks.
>
> > For instance:
>
> > $ echo $USER
> >
Corinna Vinschen wrote:
On May 7 13:57, Corinna Vinschen wrote:
I toyed around with the Microsoft Account a bit more. And here's why
the primary group SID being identical to the user SID is not a good
idea:
Security checks.
For instance:
$ echo $USER
VMBERT8164+local_000
$ scree
Greetings, Corinna Vinschen!
> I toyed around with the Microsoft Account a bit more. And here's why
> the primary group SID being identical to the user SID is not a good
> idea:
> Security checks.
> For instance:
> $ echo $USER
> VMBERT8164+local_000
> $ screen
> Directory /tmp/uscre
Corinna Vinschen wrote:
On May 6 14:22, Chris J. Breisch wrote:
Corinna Vinschen wrote:
On Windows, users and groups are identified not by uid/gid, but by
their SID. The SID is a unique value, but other than that, a SID can
be a user or a group and in lots of cases Windows doesn't care.
A gro
On May 7 14:26, vlado99 wrote:
> On 6.5.2014 15:01, Corinna Vinschen wrote:
> >Does anybody here use a Microsoft Account on a non-English Windows system?
> >If so, I'd like to see the output of
> >
> > /cygdrive/c/Windows/System32/whoami /groups | grep S-1-11-
> >
> >What I'm especially interest
On May 7 13:57, Corinna Vinschen wrote:
> I toyed around with the Microsoft Account a bit more. And here's why
> the primary group SID being identical to the user SID is not a good
> idea:
>
> Security checks.
>
> For instance:
>
> $ echo $USER
> VMBERT8164+local_000
> $ screen
> Dir
On 6.5.2014 15:01, Corinna Vinschen wrote:
Does anybody here use a Microsoft Account on a non-English Windows system?
If so, I'd like to see the output of
/cygdrive/c/Windows/System32/whoami /groups | grep S-1-11-
What I'm especially interested in is, if the domain name,
"MicrosoftAccount" i
On May 6 14:22, Chris J. Breisch wrote:
> Corinna Vinschen wrote:
> >On May 6 13:01, Chris J. Breisch wrote:
> >>Corinna Vinschen wrote:
> >>>Other than that, I'm open to discuss the necessity(?) to override
> >>>the primary group by default. But, in fact, I'm not sure this really
> >>>makes sen
Corinna Vinschen wrote:
On May 6 13:01, Chris J. Breisch wrote:
Corinna Vinschen wrote:
Other than that, I'm open to discuss the necessity(?) to override
the primary group by default. But, in fact, I'm not sure this really
makes sense. Linux systems default to creating a user-specific group
On May 6 13:01, Chris J. Breisch wrote:
> Corinna Vinschen wrote:
> >Other than that, I'm open to discuss the necessity(?) to override
> >the primary group by default. But, in fact, I'm not sure this really
> >makes sense. Linux systems default to creating a user-specific group
> >account and us
Corinna Vinschen wrote:
But, here's the deal. I eventually gave up and created a Microsoft
Account on my W8.1 machine. And this was definitely the right thing to
do, for a couple of reasons:
- For a start, it uncovered a case-sensitivity bug in my new SAM/AD
account code.
- In my case `id'
On May 6 14:52, Corinna Vinschen wrote:
> - One account in the user token's group list is a special SID for a
> user(!) account which apparently connects your local account with the
> Microsoft Account. Here's the output from Windows' own `whoami' tool:
>
> MicrosoftAccount\testu...@foob
On May 6 14:52, Corinna Vinschen wrote:
> - Alternatively, change the primary group in the Windows SAM, as
> described in the document attached to this mail. It's the latest
> version of the preliminary documentation of the new account handling
> in Cygwin. See the chapter "Cygwin
On May 5 14:56, Chris J. Breisch wrote:
> Corinna Vinschen wrote:
> >alloc_sd (the underlying function creating a security descriptor) gets
> >a uid 1001 and gid 513 as input, as usual. But the owner *and* group
> >SIDs of the file's existing security descriptor is
> >S-1-5-21-3514886939-17866863
23 matches
Mail list logo
