On Apr 17 10:07, Jim Reisert AD1C wrote:
> I'm having a little trouble with the db_home: setting at work
> (corporate network, not using /etc/passwd or /etc/group). Regarding:
>
> https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch-home
>
> I tried &quo
I'm having a little trouble with the db_home: setting at work
(corporate network, not using /etc/passwd or /etc/group). Regarding:
https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch-home
I tried "db_home: /%H" and although my MINTTY session started in the
co
On Sep 14 14:29, Dmitry Semyonov wrote:
> Hello all,
>
> I recently had to switch CYGWIN environment of sshd service from
> 'ntsec' to 'nontsec' (because of 'sed -i' breaking inherited access
> rights to some files used by native Windows apps). All se
Hello all,
I recently had to switch CYGWIN environment of sshd service from
'ntsec' to 'nontsec' (because of 'sed -i' breaking inherited access
rights to some files used by native Windows apps). All seem to work
fine after the change, including public key logins to
Thanks for your patience, Brian.
-Rob
Brian Dessent wrote:
Rob Walker wrote:
[RGW] Hm, looks simple... Why isn't this part of "cp -a" ?
You have to understand the history of things. In the classic unix
world, a file has an owner, a group, a mode, and several timestamps.
From the
Rob Walker wrote:
> [RGW] Hm, looks simple... Why isn't this part of "cp -a" ?
You have to understand the history of things. In the classic unix
world, a file has an owner, a group, a mode, and several timestamps.
>From the standpoint of what "cp -a" can manipulate portably, that's
basically i
Brian Dessent wrote:
Rob Walker wrote:
The output of the examination above shows me that "cp -a" doesn't
preserve Full Control for the owner on the copied file. Is this the
expected behavior under ntsec? If I use CYGWIN=nontsec, Full Control is
preserved.
Well cp is
t
preserve Full Control for the owner on the copied file. Is this the
expected behavior under ntsec? If I use CYGWIN=nontsec, Full Control is
preserved.
Well cp is a POSIX program and it has no idea what Windows style NT ACLs
are. It preserves the Unix modes of the file, in other words it
l Control for the owner on the copied file. Is this the
> expected behavior under ntsec? If I use CYGWIN=nontsec, Full Control is
> preserved.
Well cp is a POSIX program and it has no idea what Windows style NT ACLs
are. It preserves the Unix modes of the file, in other words it sees
0555 on
On Jan 26 12:00, Dave Korn wrote:
> On 26 January 2007 09:34, Corinna Vinschen wrote:
>
>
> > once in a while? It's outdated (Dave?)
>
> Hi, haven't forgotten but got a bit overloaded. I'll try and finish a first
> draft this weekend.
Cool, thanks!
Corinna
--
Corinna Vinschen
On 26 January 2007 09:34, Corinna Vinschen wrote:
> once in a while? It's outdated (Dave?)
Hi, haven't forgotten but got a bit overloaded. I'll try and finish a first
draft this weekend.
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe info: http
AM
Subject: Re: NTSEC documentation
put me at number 10 on your list. If you don't get a number 1-9, I
suppose I am it.
Jay
- Original Message -
From: "Corinna Vinschen"
To: the list
Sent: Monday, January 08, 2007 12:18 AM
Subject: NTSEC documentation
Is anybody here wi
put me at number 10 on your list. If you don't get a number 1-9, I
suppose I am it.
Jay
- Original Message -
From: "Corinna Vinschen" <[EMAIL PROTECTED]>
To:
Sent: Monday, January 08, 2007 12:18 AM
Subject: NTSEC documentation
Is anybody here with a deve
On Mon, 8 Jan 2007, Dave Korn wrote:
> (Plus I don't have any irc software installed...)
FYI, naim comes with an IRC client (called 'nirc').
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZ
On 08 January 2007 14:12, Corinna Vinschen wrote:
> On Jan 8 08:59, Christopher Faylor wrote:
>> On Mon, Jan 08, 2007 at 02:53:30PM +0100, Corinna Vinschen wrote:
>>>
>>> Other than that, bug me in PM if you think something's maybe not correct
>>> anymore.
>>
>> Would this be a good use of the
developer background, who likes writing
> >> > documentation?
> >> >
> >> > If so, would this person be interested in revamping the NTSEC
> >> > documentation with my input? It shows its age, my lacking knowledge of
> >> > the english language and it'
> > If so, would this person be interested in revamping the NTSEC
>> > documentation with my input? It shows its age, my lacking knowledge of
>> > the english language and it's also very strangly ordered.
>>
>> I've got some spare tuits coming up,
On Jan 8 12:29, Dave Korn wrote:
> On 08 January 2007 10:19, Corinna Vinschen wrote:
>
> > Is anybody here with a developer background, who likes writing
> > documentation?
> >
> > If so, would this person be interested in revamping the NTSEC
> > documentat
On 08 January 2007 10:19, Corinna Vinschen wrote:
> Is anybody here with a developer background, who likes writing
> documentation?
>
> If so, would this person be interested in revamping the NTSEC
> documentation with my input? It shows its age, my lacking knowledge of
> th
Is anybody here with a developer background, who likes writing
documentation?
If so, would this person be interested in revamping the NTSEC
documentation with my input? It shows its age, my lacking knowledge of
the english language and it's also very strangly ordered.
In general, if somebo
e dir to a local one (for default .ssh key
files to have the right permissions). with everything else i'm concerned
with being local this is acceptable.
*thank you*
--
View this message in context:
http://www.nabble.com/File-permissions-screwy-%28chown---chmod---ssh---rsync---ntsec--%29
kpasswd -d > /etc/passwd
mkgroup -d > /etc/group
i've set (in both .bash_profile [set CYGWIN=ntsec;export $CYGWIN;] and
global env for xp)
:: reboot ::
cygwin cmd line results..
//----//
[EMAIL PROTECTED] ~
$ echo $CYGWIN
ntsec
[EMAIL PROTECTED]
disregard my insistence that ssh and rsync do not exist in the setup list. i
just ran it again and it is there. i may just go home for the day. :/
--
View this message in context:
http://www.nabble.com/File-permissions-screwy-%28chown---chmod---ssh---rsync---ntsec--%29-tf2503531.html
yes, i have searched.
i've run:
mkpasswd -d > /etc/passwd
mkgroup -d > /etc/group
i've set (in both .bash_profile [set CYGWIN=ntsec;export $CYGWIN;] and
global env for xp)
:: reboot ::
cygwin cmd line results..
//----//
[EMAIL PROTECTED]
On 22 April 2006 22:59, Robert Thomas beau Hayes Link wrote:
> On Sat, Apr 22, 2006 at 12:52:41PM +0100, Dave Korn wrote:
>> Do you mean some magical force siezes control of your body and stops you
>> from typing every time you go to enter the word "chmod"?
> Thanks for your tongue-in-cheek tong
On Sat, Apr 22, 2006 at 12:52:41PM +0100, Dave Korn wrote:
> Do you mean some magical force siezes control of your body and stops you
> from typing every time you go to enter the word "chmod"?
Thanks for your tongue-in-cheek tongue-lashing. I'll spend some time
getting my head around cygcheck an
. Well,
that eliminates one possibility, only infinity minus one left to go!
> I believe this is
> an ntsec issue, but just haven't been able to get my head around exactly
> what is going on.
If you have no idea what's going on, what are your grounds for thinking i
Greetings,
I've poked around in the faqs and other docs but have not been able to
solve my proble, which is that for the first time in serveral cygwin
installs I a not able to chmod 755 any of my files. I believe this is
an ntsec issue, but just haven't been able to get my head arou
Terrence Brannon wrote:
> [EMAIL PROTECTED] ~/.ssh
> $ export CYGWIN=ntsec
In addition to what Dave and Eric already mentioned, "ntsec" is the
default behavior (and has been for many years) so setting "CYGWIN=ntsec"
does essentially nothing.
Brian
--
Unsubscribe info:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Terrence Brannon on 3/24/2006 10:05 AM:
> Why won't chmod work even after setting CYGWIN properly?
>
> [EMAIL PROTECTED] ~/.ssh
> $ ls -l
> total 9
> -rw-r--r-- 1 terrence mkgroup-l-d 1675 Mar 14 10:02 id_rsa
> -rw-r--r-- 1 terrence mkgro
On 24 March 2006 17:05, Terrence Brannon wrote:
> Why won't chmod work even after setting CYGWIN properly?
>
> [EMAIL PROTECTED] ~/.ssh
> $ ls -l
> total 9
> -rw-r--r-- 1 terrence mkgroup-l-d 1675 Mar 14 10:02 id_rsa
> -rw-r--r-- 1 terrence mkgroup-l-d 396 Mar 14 10:02 id_rsa.pub
> -rw-r--r-- 1
EMAIL PROTECTED] ~/.ssh
$ echo $CYGWIN
[EMAIL PROTECTED] ~/.ssh
$ export CYGWIN=ntsec
[EMAIL PROTECTED] ~/.ssh
$ echo $CYGWIN
ntsec
[EMAIL PROTECTED] ~/.ssh
$ chmod -v 600 id_rsa
mode of `id_rsa' changed to 0600 (rw---)
[EMAIL PROTECTED] ~/.ssh
$ ls -l id_rsa
-rw-r--r-- 1 terrence mkgroup-l-
On 03 March 2006 20:28, Corinna Vinschen wrote:
>
> I've applied a fix. Please test.
>
WJFFM.
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Do
On Mar 3 21:28, Corinna Vinschen wrote:
> At one point in opendir() a file handler is added to the descriptor
> table. This happened at a point at which it was already clear that
> opendir would succeed. Due to my changes from end of January this
> wasn't true anymore. The entry in the descript
On Mar 3 17:38, Christian Franke wrote:
> Hi,
>
> with the current cygwin1.dll 20050203, ls.exe hangs on access of an
> inaccessible directory if ntsec is turned off.
>
> Steps to reproduce on XP Prof:
>
> $ CYGWIN=ntsec ls "/cygdrive/c/System Volume Informat
On 03 March 2006 19:39, Dave Korn wrote:
> On 03 March 2006 17:13, Dave Korn wrote:
>
>> On 03 March 2006 16:39, Christian Franke wrote:
>
>>> Steps to reproduce on XP Prof:
>
>>> $ CYGWIN=nontsec ls "/cygdrive/c/System Volume Information"
>>> ls: /cygdrive/c/System Volume Information: Permissi
On 03 March 2006 17:13, Dave Korn wrote:
> On 03 March 2006 16:39, Christian Franke wrote:
>> Steps to reproduce on XP Prof:
>> $ CYGWIN=nontsec ls "/cygdrive/c/System Volume Information"
>> ls: /cygdrive/c/System Volume Information: Permission denied
>> # *** ls hangs with 100% CPU ***
>>
>> B
On 03 March 2006 16:39, Christian Franke wrote:
> Hi,
>
> with the current cygwin1.dll 20050203, ls.exe hangs on access of an
> inaccessible directory if ntsec is turned off.
>
> Steps to reproduce on XP Prof:
>
> $ CYGWIN=ntsec ls "/cygdrive/c/System Volume I
Hi,
with the current cygwin1.dll 20050203, ls.exe hangs on access of an
inaccessible directory if ntsec is turned off.
Steps to reproduce on XP Prof:
$ CYGWIN=ntsec ls "/cygdrive/c/System Volume Information"
ls: /cygdrive/c/System Volume Information: Permission denied
# OK
$ CYGWIN=
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of Igor Peshansky
> Sent: Thursday, 12 January 2006 1:54 PM
> To: Matthew Pittman
> Cc: cygwin@cygwin.com
> Subject: RE: chmod not working with ntsec set
>
>
> Ugh, top-posti
;http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Thanks.
> Subject: Re: chmod not working with ntsec set
>
> > On Thu, 12 Jan 2006, Matthew Pittman wrote:
> >
> > > I know this is a dumb question but I have made genuine efforts to
> > > understand what I'
But this is a WAG too.
Any ideas where I go from here?
Regards,
Matt.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
Of Igor Peshansky
Sent: Thursday, 12 January 2006 12:54 PM
To: Matthew Pittman
Cc: cygwin@cygwin.com
Subject: Re: chmod not working with ntse
pressed on regardless but I found I couldn't get chmod to work so I
> searched the documentation, web and mailing list archives and found that
> I should set the CYGWIN environment variable to "ntsec". I also noted
> that this should now be the default anyway but I set it
entation, web and mailing list archives and found that I
should set the CYGWIN environment variable to "ntsec". I also noted that
this should now be the default anyway but I set it anyway and it hasn't
solved the problem.
$ echo $CYGWIN
ntsec
$ chmod -v u+x .bas
On May 25 09:08, Igor Pechtchanski wrote:
> On Wed, 25 May 2005, Corinna Vinschen wrote:
> > This is a change to sshd which had been requested upstream. The main
> > developers felt that propagating all SYSTEM environment to the
> > unprivileged child applications has to be treated as unsecure.
>
On Wed, 25 May 2005, Corinna Vinschen wrote:
> On May 24 22:27, Brian Dessent wrote:
> > David Rothenberger wrote:
> >
> > > I have CYGWIN set in my sshd service and globally to "server", but when
> > > I ssh to my machine, CYGWIN is empty:
> > >
> > > % echo $CYGWIN
> > > server
> > > % ssh local
On May 24 22:27, Brian Dessent wrote:
> David Rothenberger wrote:
>
> > I have CYGWIN set in my sshd service and globally to "server", but when
> > I ssh to my machine, CYGWIN is empty:
> >
> > % echo $CYGWIN
> > server
> > % ssh localhost
> > Last login: Wed May 4 20:20:04 2005 from localhost
>
David Rothenberger wrote:
> I have CYGWIN set in my sshd service and globally to "server", but when
> I ssh to my machine, CYGWIN is empty:
>
> % echo $CYGWIN
> server
> % ssh localhost
> Last login: Wed May 4 20:20:04 2005 from localhost
> % echo $CYGWIN
Hmm, weird. I see the same thing here
On 5/24/2005 10:04 PM, Brian Dessent wrote:
I could be wrong here but I thought that setting of $CYGWIN for the
service affects only the environment of the actual service, not for the
general cygwin environment. If you want the CYGWIN environment variable
set to a certain value globally, just se
Tom Rodman wrote:
> I've upgraded to 1.5.16, and installed the latest openssh, using
> the "ssh-host-config -y" script. I specified CYGWIN be set to:
>
> binmode tty ntsec smbntsec
>
> When I logon w/simple password authentication, CYGWIN is undefined:
>
I've upgraded to 1.5.16, and installed the latest openssh, using
the "ssh-host-config -y" script. I specified CYGWIN be set to:
binmode tty ntsec smbntsec
When I logon w/simple password authentication, CYGWIN is undefined:
bash-2.05b $ ssh localhost -l adm_tsr
[EMA
I'm using ntsec on ntfs. The thing is when users restrict group and world
access to their files (umask 077 or chmod g-rwx,o-rwx), the administrators
group is also locked out. Very unpractical for automated backups running from
the administrator account.
Now, I would like every file/dir cr
N
Sent: Monday, December 27, 2004 3:19 PM
To: Bryan Love; cygwin@cygwin.com
Subject: RE: SSH, SFTP, and NTSEC
>My problem is simple... I have users that I created that cannot log in via
>SSH unless I make them >members of the Windows ADMINISTRATORS group on the
>Windows 2003 server tha
My problem is simple... I have users that I created that cannot log in via
SSH unless I make them >members of the Windows ADMINISTRATORS group on the
Windows 2003 server that is running >Cygwin. I've tried everything I can
think of and lots of stuff from other people that I could never >have
I've researched this topic online for days and it seems like every one has
their own solution or their own idea about how user authentication works in
Cygwin.
What I CAN'T seem to find is a simple description of exactly what happens when
a user tries to log in via SSH. What is the flow of Cygw
instead.
>This
>> > way, without a valid login, you cannot get any information, including
>> > usernames and ACLs.
>> >
>> > How can I stop cygwin setting these ACLs?
>>
>> Did you have a close look to the acc
cluding
> > usernames and ACLs.
> >
> > How can I stop cygwin setting these ACLs?
>
> Did you have a close look to the access rights granted to everyone?
> Otherwise, just don't use ntsec.
>
> Corinna
>
> > [...]
> >
>
> How can I stop cygwin setting these ACLs?
Did you have a close look to the access rights granted to everyone?
Otherwise, just don't use ntsec.
Corinna
> [...]
> Everyone:(special access:)
> READ_CONTROL
>
OK. Here is an example of the way permissions leak out to "Everyone". I
create a new file, with no permissions granted to "other". Cygwin shows this
to have worked OK. Yet in actual fact there is an ACL there giving Everyone
some access rights. I usually choose not to have "Everyone" authorised to
At 07:58 AM 9/15/2003, Chris Rodgers you wrote:
>Hi
>
>I have hunted on the web for a while trying to find a solution, but to no
>avail. If any of you can help me, I'd appreciate it.
>
>I am using Cygwin on Windows 2000 with the NTsec permissions enabled on an
>NTFS volum
Hi
I have hunted on the web for a while trying to find a solution, but to no
avail. If any of you can help me, I'd appreciate it.
I am using Cygwin on Windows 2000 with the NTsec permissions enabled on an
NTFS volume. My problem is that some of the Cygwin tools I use require
certain files
Why isn't ntsec a mount option?
Max Bowsher wrote:
Having ntsec on by default has shown us that the imperfect mapping between
ACLs and file modes can cause a *lot* of problems. Essentially, for ntsec to
be useful, a fair amount of caring for permissions is required. New users
are ofte
Max,
What problems is ntsec causing? I am a relatively new user and I have not
had any problems with it. In fact it is allowing me to host a more secure
ssh server installation. I have been following the list for a couple of
months and I have not seen many problems relating to ntsec. Most of
Having ntsec on by default has shown us that the imperfect mapping between
ACLs and file modes can cause a *lot* of problems. Essentially, for ntsec to
be useful, a fair amount of caring for permissions is required. New users
are often not prepared for this. Hence: what about making ntsc off by
Mark Priest wrote:
> Max,
>
> What problems is ntsec causing? I am a relatively new user and I have not
> had any problems with it. In fact it is allowing me to host a more secure
> ssh server installation. I have been following the list for a couple of
> months and I
Doug VanLeuven wrote:
Christopher Faylor wrote:
On Tue, Aug 05, 2003 at 06:46:05AM -0700, Doug VanLeuven wrote:
Why isn't ntsec a mount option?
The standard reason.
Which is the standard reason?
1. It's that way because nobody has coded it yet.
2. It's that way becaus
Christopher Faylor wrote:
On Tue, Aug 05, 2003 at 06:46:05AM -0700, Doug VanLeuven wrote:
Why isn't ntsec a mount option?
The standard reason.
Which is the standard reason?
1. It's that way because nobody has coded it yet.
2. It's that way because the core team analyzed
Max Bowsher wrote:
Having ntsec on by default has shown us that the imperfect mapping between
ACLs and file modes can cause a *lot* of problems. Essentially, for ntsec to
be useful, a fair amount of caring for permissions is required. New users
are often not prepared for this. Hence: what about
On Tue, Aug 05, 2003 at 06:46:05AM -0700, Doug VanLeuven wrote:
>Why isn't ntsec a mount option?
The standard reason.
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to [EMAIL PROTECTED]
and be permanently bloc
Christopher Faylor wrote:
On Wed, Jul 23, 2003 at 10:54:06AM -0400, Larry Hall wrote:
[EMAIL PROTECTED] wrote:
On 23 Jul, I wrote:
I was going to qualify this with `when ntsec is defined in CYGWIN'
It's not easy to find out if ntsec is turned on, is it? When I wrote
the ab
On Wed, Jul 23, 2003 at 10:54:06AM -0400, Larry Hall wrote:
>[EMAIL PROTECTED] wrote:
>
>>On 23 Jul, I wrote:
>>
>>>I was going to qualify this with `when ntsec is defined in CYGWIN'
>>
>>
>>It's not easy to find out if ntsec is turned on,
[EMAIL PROTECTED] wrote:
On 23 Jul, I wrote:
I was going to qualify this with `when ntsec is defined in CYGWIN'
It's not easy to find out if ntsec is turned on, is it? When I wrote
the above, I was thinking "ntsec turned on" means $CYGWIN includes the
word "ntse
On 23 Jul, I wrote:
> I was going to qualify this with `when ntsec is defined in CYGWIN'
It's not easy to find out if ntsec is turned on, is it? When I wrote
the above, I was thinking "ntsec turned on" means $CYGWIN includes the
word "ntsec".
But I think I
John,
I am using Cygwin and sshd with public key authentication on a Windows XP
Professional machine and I am seeing the same ACL behavior that you are. I
have set the CYGWIN environment variable to "ntsec nontea" "nontsec ntea"
and "nontsec nontea". These settings
000 perms.
We have reformatted these machines and done fresh installs and yet the
corruption happens all over again on every machine using cygwin & ssh.
If there were a way to not use ntsec and use inherited permissions via
nontsec, that would be stellar.
Thanks again,
John
On Tue, 8 Jul 2003,
On Tue, 8 Jul 2003, John wrote:
> CYGWIN="binmode ntsec tty".
>
> When making directories via ssh:
> ssh "mkdir /cygdrive/d/temp/test"
> or when copying files via scp:
> scp file.txt :/cygdrive/d/temp/test
>
> the files are given the "ntsec&
Hello,
We are running openssh 3.5p1 with public key authentication working with
no problems. Currently, we have sshd running with the following:
CYGWIN="binmode ntsec tty".
When making directories via ssh:
ssh "mkdir /cygdrive/d/temp/test"
or when copying files via scp:
scp
Jason,
If you have seen my messages on the Cygwin list, you should have noticed
that the Reply-To field on all of them is set to the Cygwin list. In
fact, the Cygwin list is the preferred method for getting Cygwin help and
information, as opposed to sending e-mail to individual contributors.
This
during remote acess. There has
> been some insight on what the problem seems to be in regards to the
> version of Cygwin. My question is regards to a immediate work-around
> this permissions issue with inetd/xinetd ?
>
> Thanks everyone for taking the time in looking into this issue.
>
Cygwin. My question is
regards to
a immediate work-around this permissions issue with inetd/xinetd ?
Thanks everyone for taking the time in looking into this issue.
Steve
Fwd: Re: NTsec permissions issue over inet]
From: Larry Hall
To: Cygwin
Date: Mon, 02 Jun 2003 23:33:51 -0400
Subject
On Tue, 3 Jun 2003, Banville, Stephen wrote:
> Bruce,
> This is starting to become clear o what is actually going on.
> How do you currently get around this issue ?
>
> Steve
Steve,
Please either quote the message you're replying to, or make sure your
mailer contains threading informatio
Bruce,
This is starting to become clear o what is actually going on. How do
you currently get around this issue ?
Steve
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.h
Original Message
Bruce Dobrin wrote:
YIKES! There it is, and right there in the users guide no less
not only that, but in a section I've actually read a number of
times!. Well, that does explain almost everything that is going on
( though, it seems to have
quot;
convert everything to windows") I'd really appreciate it.. In any case,
Thanks Igor, for the time spent already..
Bruce D.
- Original Message -
From: "Igor Pechtchanski" <[EMAIL PROTECTED]>
To: "Bruce Dobrin" <[EMAIL PROTECTED]>
C
Umm, Bruce, you aren't trying to access network shares from a session you
did with passwordless authentication, are you? Because if you are, it's
not going to work (see
<http://cygwin.com/cygwin-ug-net/ntsec.html#NTSEC-RELEASE1.3.3>).
I've also found that even if you log
- Original Message -
From: "Bruce Dobrin" <[EMAIL PROTECTED]>
To: "Bruce Dobrin" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, June 02, 2003 8:04 PM
Subject: Re: NTsec permissions issue over inet
> I tried executing a the command vi
hen" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, June 02, 2003 12:37 PM
Subject: Re: NTsec permissions issue over inet
> hmmm, still experimenting: thought it might have something to do with
> inetd and mounts, but I also tried rlogin to which is
running
>
Igor Pechtchanski wrote:
Steve,
On Windows, if you use the Windows sharing mechanism (instead of a
proprietary filesystem driver), your shares are SMB shares (which stands
for Server Message Block, IIRC). The 'smbntsec' option is designed for
those kinds of shares.
Methinks the documentation w
27;Bruce Dobrin'" <[EMAIL PROTECTED]>; "Banville, Stephen"
<[EMAIL PROTECTED]>
Sent: Monday, June 02, 2003 5:32 AM
Subject: RE: NTsec permissions issue over inet
> Igor,
> I tried settting smbntsec and it did not work. With older version I
> used to
> just
Igor,
I tried settting smbntsec and it did not work. With older version I
used to
just set ntsec, make the passwd and group files, and everything would just
work
the way I would expect. Something has changed in the way cygwin handles NT
security.
I am running a generic version of windows
to
have extra privileges to be able to switch user context (create an access
token belonging to someone else).
<http://cygwin.com/cygwin-ug-net/ntsec.html#NTSEC-SETUID> should explain
this somewhat.
Igor
On Sun, 1 Jun 2003, Stephen Banville wrote:
> HI Bruce,
>
> Th
brin
Sent: Friday, May 30, 2003 8:20 PM
To: [EMAIL PROTECTED]
Subject: Re: NTsec permissions issue over inet
OK, further testing, I can't get the below rlogin "trick" to work on a
1.3.22 machine, the one it worked on is actually a 1.3.12 machine. so,
with 1.3.12 I can get it to wor
e confused than ever...
- Original Message -
From: "Bruce Dobrin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 30, 2003 4:46 PM
Subject: Re: NTsec permissions issue over inet
> Sorry, On re-reading that, it's not as clear as it could b
CTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, May 30, 2003 4:37 PM
Subject: Re: NTsec permissions issue over inet
> Thanks for responding Larry,
>
> I actually had tried most permutations of (no)ntsec, (no)smbntsec,
(no)ntea,
> etc... and on other m
Thanks for responding Larry,
I actually had tried most permutations of (no)ntsec, (no)smbntsec, (no)ntea,
etc... and on other machines that didn't have weird path or passwd
entries. -- no dice
I think I may have a good hint as to what is going on, but I'll need
someone who knows
Dobrin
- Original Message -
From: "Larry Hall" <[EMAIL PROTECTED]>
To: "Bruce Dobrin" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "Banville, Stephen"
<[EMAIL PROTECTED]>
Sent: Thursday, May 29, 2003 6:54 AM
Subject: Re: NTsec permiss
Message-
From: Larry Hall [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 29, 2003 9:52 AM
To: Banville, Stephen
Cc: '[EMAIL PROTECTED]'
Subject: Re: NTsec permissions issue over inet
Banville, Stephen wrote:
> My system that I have Cygwin running on is a Windows 2000 platform. I h
t: Wednesday, May 28, 2003 4:26 PM
To: Banville, Stephen
Cc: [EMAIL PROTECTED]
Subject: Re: NTsec permissions issue over inet
On Wed, 28 May 2003, Banville, Stephen wrote:
> Hi All,
> I'm not sure if this issue has been detected. I have traversed
> through the MANY probelm
ECTED]
Sent: Wednesday, May 28, 2003 8:05 PM
To: [EMAIL PROTECTED]; Banville, Stephen
Subject: Re: NTsec permissions issue over inet
Stephen,
I was about to ask the same question
If you find a solution, PLEASE Post, as I'm running out of workarounds, I
have had no luck with nosmbntsec/smbnt
Igor Pechtchanski wrote:
For the future, please *attach* the cygcheck output to avoid generating
false positives on message archive search.
Random idea: would it be possible to instruct ezmlm-idx to bounce
messages containing cygcheck output in the body? (Or enough text to
identify cygcheck
1 - 100 of 182 matches
Mail list logo
