Hi!
I'm trying to create a Cygwin FIFO which can only be read and written by admins:
snip
# as admin
mkfifo system_cmd_fifo
chgrp 544 system_cmd_fifo
chmod a-rwx,g+rw system_cmd_fifo
cat https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:
TL;DR: Weird permissions behavior in a Cygwin installation where
permissions have been changed over time. I can't reproduce it on a
clean install so that's how I'm working around it, but I thought it
might be worth capturing what details I have in case it helps others
or helps
UNTING : FALSE
>FILE_SUPPORTS_SPARSE_VDL : FALSE
>FILE_DAX_VOLUME : FALSE
>FILE_SUPPORTS_GHOSTING: FALSE
> SectorInfoFlags: 0x03
>SSINFO_FLAGS_NO_SEEK_PENALTY : FALSE
>SSINFO_FLAGS_TRIM_ENABLED : FALSE
> By
way, I found a solution:
setfacl -s u::rwx,g::r-x,o::r-x,d:u::rwx,d:g::r-x,d:o::r-x myfolder
After that, permissions work as expected inside "myfolder" and new
subfolders. Even on H:. But I'm not sure to understand why. I would have
expected that a simple chmod on myfolder would ha
On 23/01/2024 22:54, Vincent Rivière via Cygwin wrote:
Hi,
I'm facing a really weird issue with NTFS permissions.
$ umask
0022
$ cd /cygdrive/h/
what is H ?
$ mkdir a
$ ls -ld a
drwxr-xr-x 1 vincent vincent 0 Jan 23 22:35 a
# You can see that permissions are fine.
$ getfacl a
# fi
Hi,
I'm facing a really weird issue with NTFS permissions.
$ umask
0022
$ cd /cygdrive/h/
$ mkdir a
$ ls -ld a
drwxr-xr-x 1 vincent vincent 0 Jan 23 22:35 a
# You can see that permissions are fine.
$ getfacl a
# file: a
# owner: vincent
# group: vincent
user::rwx
group::r-x
other
Greetings, matth...@gmx.li!
Please no top-posting in this list.
> Am Freitag, dem 22.12.2023 um 22:11 + schrieb Lavrentiev, Anton
> (NIH/NLM/NCBI) [C]:
>> > Thanks for any hint
>>
>> https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-files
>>
> How c
Thanks a lot,
How can I set the permissions as promised?
Thanks
Matthias
Am Freitag, dem 22.12.2023 um 22:11 + schrieb Lavrentiev, Anton
(NIH/NLM/NCBI) [C]:
> > Thanks for any hint
>
> https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-files
>
> HTH,
>
> Anton Lav
> Thanks for any hint
https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-files
HTH,
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe in
Hello
I use "mkdir.exe /test" for creating a directory.
If I open the properties in Windows it say "Permissions of /test are in wrong
order"
If I use "cmd /c mkdir /test" all is fine.
I know that the mkdir.exe is the cygwin version and "cmd /c mkdir"
On Sun, Aug 27, 2023 at 2:35 PM Corinna Vinschen via Cygwin
wrote:
>
> On Aug 26 19:44, Martin Wege via Cygwin wrote:
> > On Fri, Aug 25, 2023 at 2:19 PM Corinna Vinschen via Cygwin
> > wrote:
> > >
> > > On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > > > Note that Cygwin does not interpret
On Aug 28 07:35, Cedric Blancher via Cygwin wrote:
> On Sun, 27 Aug 2023 at 14:35, Corinna Vinschen via Cygwin
> wrote:
> > As for FIFOs on NFS, as I wrote, they never worked as desired on NFS.
> > For kicks I tried back until Cygwin 3.3. Given this isn't a regression,
> > it won't be fixed for C
On Sun, 27 Aug 2023 at 14:35, Corinna Vinschen via Cygwin
wrote:
>
> On Aug 26 19:44, Martin Wege via Cygwin wrote:
> > On Fri, Aug 25, 2023 at 2:19 PM Corinna Vinschen via Cygwin
> > wrote:
> > >
> > > On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > > > Note that Cygwin does not interpret th
On Aug 26 19:44, Martin Wege via Cygwin wrote:
> On Fri, Aug 25, 2023 at 2:19 PM Corinna Vinschen via Cygwin
> wrote:
> >
> > On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > > Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO,
> > > instead it comes back as a symlink "myfifo.f
On 2023-08-26 11:44, Martin Wege via Cygwin wrote:
On Fri, Aug 25, 2023 at 2:19 PM Corinna Vinschen via Cygwin
wrote:
On Aug 23 01:05, Roland Mainz via Cygwin wrote:
Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO,
instead it comes back as a symlink "myfifo.fifo -> ':\0:c4:
fsv3/ksh-1.0.4/arch/cygwin.i386-64/bin/mamake
package: make with mamake
package: make output captured in
/cygdrive/z/arbeitdfn/windows_ksh/build_nfsv3/ksh-1.0.4/arch/cygwin.i386-64/lib/package/gen/make.out
mkfifo: cannot set permissions of
'/cygdrive/z/arbeitdfn/windows_ksh/build_nfsv3/ksh-1.0
On Thu, Aug 24, 2023 at 6:45 PM Martin Wege wrote:
>
> On Wed, Aug 23, 2023 at 1:06 AM Roland Mainz via Cygwin
> wrote:
> >
> > On Tue, Aug 22, 2023 at 4:52 PM Lavrentiev, Anton (NIH/NLM/NCBI) [C]
> > via Cygwin wrote:
> > > > FIFOs which don't make *any* sense
> > > > ... FWIW, a remote NFS fil
On Fri, Aug 25, 2023 at 2:19 PM Corinna Vinschen via Cygwin
wrote:
>
> On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO,
> > instead it comes back as a symlink "myfifo.fifo -> ':\0:c4:1000'".
> >
> > AFAIK there are (at least) t
tdfn/windows_ksh/build_nfsv3/ksh-1.0.4/arch/cygwin.i386-64
view
package: update
/cygdrive/z/arbeitdfn/windows_ksh/build_nfsv3/ksh-1.0.4/arch/cygwin.i386-64/lib/probe/C/make/probe
package: update
/cygdrive/z/arbeitdfn/windows_ksh/build_nfsv3/ksh-1.0.4/arch/cygwin.i386-64/bin/mamake
package: make with mam
> You don't seem to understand the problem.
I think I do, and that aligns with your explanation how Cygwin machinery works
to fake the FIFOs.
> If I can recognize a file as FIFO, I can use it as FIFO, regardless if it's a
> native FIFO or a Cygwin FIFO.
That's exactly what I meant!
> Show m
On Aug 25 23:21, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > it is not possible to diffentiate between Cygwin
> > FIFOs and real FIFOs created from the remote side in `ls -l'
> > output.
>
> Why would that be necessary? If it's a FIFO, it can be used as a
> FIFO, regardless where a
On Aug 26 13:26, Cedric Blancher via Cygwin wrote:
> On Fri, 25 Aug 2023 at 14:26, Corinna Vinschen via Cygwin
> wrote:
> >
> > On Aug 25 14:18, Corinna Vinschen via Cygwin wrote:
> > > On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > > > 2. Check whether the filesystem for the fifos path is NF
On Fri, 25 Aug 2023 at 17:15, Roland Mainz via Cygwin wrote:
>
> On Fri, Aug 25, 2023 at 2:18 PM Corinna Vinschen via Cygwin
> wrote:
> >
> > On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > > Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO,
> > > instead it comes back as a
On Fri, 25 Aug 2023 at 14:26, Corinna Vinschen via Cygwin
wrote:
>
> On Aug 25 14:18, Corinna Vinschen via Cygwin wrote:
> > On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > > 2. Check whether the filesystem for the fifos path is NFS
> > > (cgywin.dll's |fs.fs_is_nfs()|), and then just refuse |
> it is not possible to diffentiate between Cygwin
> FIFOs and real FIFOs created from the remote side in `ls -l'
> output.
Why would that be necessary? If it's a FIFO, it can be used as a FIFO,
regardless where and how it was created..
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Problem rep
n [3] as *prototype*, so
|mknod()| will properly work in a portable manner
5. We ask Microsoft to review the private API created in [3], and ask
them to implement it for the Microsoft NFSv3 client too (because we
have a precedent with [4]!)
Optional:
6. Cygwin: Like [1] add "afs_emulate_dev_special_files_as_symlink" to
do
On Aug 25 14:18, Corinna Vinschen via Cygwin wrote:
> On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > 2. Check whether the filesystem for the fifos path is NFS
> > (cgywin.dll's |fs.fs_is_nfs()|), and then just refuse |mkfifo()| with
> > |ENOSYS| (not implemented)
>
> I like the idea.
EPERM,
On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO,
> instead it comes back as a symlink "myfifo.fifo -> ':\0:c4:1000'".
>
> AFAIK there are (at least) these two options to fix the problems:
> 1. Check whether the filesystem for the
On Aug 24 18:24, Martin Wege via Cygwin wrote:
> On Sat, Aug 19, 2023 at 10:15 AM ASSI via Cygwin wrote:
> >
> > Martin Wege via Cygwin writes:
> > > How can I find out whether the current Cygwin terminal has
> > > Administrator rights? I want to safeguard our admin scripts with a
> > > simple tes
On Thu, 24 Aug 2023 at 18:45, Martin Wege via Cygwin wrote:
>
> On Wed, Aug 23, 2023 at 1:06 AM Roland Mainz via Cygwin
> wrote:
> >
> > On Tue, Aug 22, 2023 at 4:52 PM Lavrentiev, Anton (NIH/NLM/NCBI) [C]
> > via Cygwin wrote:
> > > > FIFOs which don't make *any* sense
> > > > ... FWIW, a remot
at the process is a member of the
> Administrators group, the group isn't enabled, so the process isn't
> actually running with administrative permissions. In Windows-speak we would
> say the process isn't "elevated" ("elevated" = "running with admin
On Wed, Aug 23, 2023 at 1:06 AM Roland Mainz via Cygwin
wrote:
>
> On Tue, Aug 22, 2023 at 4:52 PM Lavrentiev, Anton (NIH/NLM/NCBI) [C]
> via Cygwin wrote:
> > > FIFOs which don't make *any* sense
> > > ... FWIW, a remote NFS fileystem.
> >
> > I got an impression that the OP is trying to deploy
On Wed, Aug 23, 2023 at 5:44 PM Jeffrey Altman via Cygwin
wrote:
>
> On 8/22/2023 10:52 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin
> wrote:
> >> FIFOs which don't make *any* sense
> >> ... FWIW, a remote NFS fileystem.
> > I got an impression that the OP is trying to deploy something (may
On Sat, Aug 19, 2023 at 10:15 AM ASSI via Cygwin wrote:
>
> Martin Wege via Cygwin writes:
> > How can I find out whether the current Cygwin terminal has
> > Administrator rights? I want to safeguard our admin scripts with a
> > simple test and bail out with an error if someone wants to do admin
>
er of Administrators):
PS C:\> whoami /groups /fo csv | ConvertFrom-Csv | Where-Object { $_.SID
-eq "S-1-5-32-544" }
That is, while it is true that the process is a member of the
Administrators group, the group isn't enabled, so the process isn't
actually running with administ
> Hello,
>
> How can I find out whether the current Cygwin terminal has
> Administrator rights? I want to safeguard our admin scripts with a
> simple test and bail out with an error if someone wants to do admin
> stuff (say: regtool) without admin privileges.
https://superuser.com/questions/66019
On Wed, 23 Aug 2023 at 17:44, Jeffrey Altman via Cygwin
wrote:
>
> On 8/22/2023 10:52 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin
> wrote:
> >> FIFOs which don't make *any* sense
> >> ... FWIW, a remote NFS fileystem.
> > I got an impression that the OP is trying to deploy something (maybe
> What happens when the user executes two copies of an
> application /*such as PyCharm*/ on two separate machines sharing the same
> home directory? Does the directory entry and inode get reused on startup
> and/or deleted on exit? How does that impact the process instance on the
> other machin
On 8/22/2023 10:52 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin
wrote:
FIFOs which don't make *any* sense
... FWIW, a remote NFS fileystem.
I got an impression that the OP is trying to deploy something (maybe the entire Cygwin)
onto an NFS share. So the named FIFO "file" is also created
On Tue, Aug 22, 2023 at 4:52 PM Lavrentiev, Anton (NIH/NLM/NCBI) [C]
via Cygwin wrote:
> > FIFOs which don't make *any* sense
> > ... FWIW, a remote NFS fileystem.
>
> I got an impression that the OP is trying to deploy something (maybe the
> entire Cygwin) onto an
> NFS share. So the named FIFO
> FIFOs which don't make *any* sense
> ... FWIW, a remote NFS fileystem.
I got an impression that the OP is trying to deploy something (maybe the entire
Cygwin) onto an NFS share. So the named FIFO "file" is also created in there.
It's pointless to assume that the FIFO can be used as a communic
gt; >
> > > /usr/bin/mkfifo -m 600 x.fifo
> > > mkfifo: cannot set permissions of 'x.fifo': Not a directory
> > >
> > > Is there a known workaround? So far named fifos cannot be created somehow.
> >
> > This is fixed for NTFS, but s
t;
> > > > Hello,
> > > >
> > > > We get a weird mkfifo failure in Cygwin on NTFS:
> > > >
> > > > /usr/bin/mkfifo -m 600 x.fifo
> > > > mkfifo: cannot set permissions of 'x.fifo': Not a directory
> > > >
> &
NTFS:
> > >
> > > /usr/bin/mkfifo -m 600 x.fifo
> > > mkfifo: cannot set permissions of 'x.fifo': Not a directory
> > >
> > > Is there a known workaround? So far named fifos cannot be created somehow.
> >
> > This is fixed for NTFS, b
On Sat, Aug 19, 2023 at 2:15 AM ASSI wrote:
Windows really doesn't have a defined notion of what is or is not an
> "administrator". Each particular definition will be insufficient or
> invalid in certain contexts.
>
There is a definition of administrator in Windows: Your account is a
member, eit
Martin Wege via Cygwin writes:
> How can I find out whether the current Cygwin terminal has
> Administrator rights? I want to safeguard our admin scripts with a
> simple test and bail out with an error if someone wants to do admin
> stuff (say: regtool) without admin privileges.
Windows really doe
t;; fi
}
I imagine any other Windows app that needs admin permissions would work.
I use this to change the color of the prompt ($PS1) for the admin user to red.
HTH
Doug
--
Doug Henderson, Calgary, Alberta, Canada - from gmail.com
--
Problem reports: https://cygwin.com/problems.html
FAQ:
gt; >
> > > /usr/bin/mkfifo -m 600 x.fifo
> > > mkfifo: cannot set permissions of 'x.fifo': Not a directory
> > >
> > > Is there a known workaround? So far named fifos cannot be created somehow.
> >
> > This is fixed for NTFS, but s
Mark Geisert via Cygwin wrote:
Backwoods BC via Cygwin wrote:
[...]
I don't know if this is the official method, but it works for me:
# Shell Options
# Elevated privilege windows have $SESSIONNAME set
if [ "$SESSIONNAME" == "" ] ;then
printf -v adminPmt '[\u2022Admin\u2022] '
else
ex
Backwoods BC via Cygwin wrote:
On Thu, Aug 17, 2023 at 7:01 PM Martin Wege via Cygwin
wrote:
How can I find out whether the current Cygwin terminal has
Administrator rights? I want to safeguard our admin scripts with a
simple test and bail out with an error if someone wants to do admin
stuff (s
On Aug 18 06:02, Martin Wege via Cygwin wrote:
> On Mon, Aug 7, 2023 at 4:42 PM Martin Wege wrote:
> >
> > Hello,
> >
> > We get a weird mkfifo failure in Cygwin on NTFS:
> >
> > /usr/bin/mkfifo -m 600 x.fifo
> > mkfifo: cannot set permissions of '
On Mon, Aug 7, 2023 at 4:42 PM Martin Wege wrote:
>
> Hello,
>
> We get a weird mkfifo failure in Cygwin on NTFS:
>
> /usr/bin/mkfifo -m 600 x.fifo
> mkfifo: cannot set permissions of 'x.fifo': Not a directory
>
> Is there a known workaround? So far named fifo
On Thu, Aug 17, 2023 at 7:01 PM Martin Wege via Cygwin
wrote:
> How can I find out whether the current Cygwin terminal has
> Administrator rights? I want to safeguard our admin scripts with a
> simple test and bail out with an error if someone wants to do admin
> stuff (say: regtool) without admin
Hello,
How can I find out whether the current Cygwin terminal has
Administrator rights? I want to safeguard our admin scripts with a
simple test and bail out with an error if someone wants to do admin
stuff (say: regtool) without admin privileges.
Thanks,
Martin
--
Problem reports: https:/
On Wed, Aug 9, 2023 at 11:56 AM Corinna Vinschen
wrote:
>
> On Aug 9 11:12, Martin Wege via Cygwin wrote:
> > On Wed, Aug 9, 2023 at 10:01 AM Corinna Vinschen
> > wrote:
> > >
> > > On Aug 8 21:38, Martin Wege via Cygwin wrote:
> > > > On Tue, Aug 8, 2023 at 10:20 AM Corinna Vinschen
> > > > w
On Aug 9 11:12, Martin Wege via Cygwin wrote:
> On Wed, Aug 9, 2023 at 10:01 AM Corinna Vinschen
> wrote:
> >
> > On Aug 8 21:38, Martin Wege via Cygwin wrote:
> > > On Tue, Aug 8, 2023 at 10:20 AM Corinna Vinschen
> > > wrote:
> > > >
> > > > On Aug 7 23:14, Martin Wege via Cygwin wrote:
> >
eird mkfifo failure in Cygwin on NTFS:
> > > > > > >
> > > > > > > /usr/bin/mkfifo -m 600 x.fifo
> > > > > > > mkfifo: cannot set permissions of 'x.fifo': Not a directory
> > > > > >
> > > > > > This e
gt; > > On Aug 7 12:26, Brian Inglis via Cygwin wrote:
> > > > > On 2023-08-07 08:42, Martin Wege via Cygwin wrote:
> > > > > > We get a weird mkfifo failure in Cygwin on NTFS:
> > > > > >
> > > > > > /usr/bin/mkfifo -m 600 x
n 2023-08-07 08:42, Martin Wege via Cygwin wrote:
> > > > > We get a weird mkfifo failure in Cygwin on NTFS:
> > > > >
> > > > > /usr/bin/mkfifo -m 600 x.fifo
> > > > > mkfifo: cannot set permissions of 'x.fifo': Not a directory
> &g
in Cygwin on NTFS:
> > > >
> > > > /usr/bin/mkfifo -m 600 x.fifo
> > > > mkfifo: cannot set permissions of 'x.fifo': Not a directory
> > >
> > > This error is also reproducible with default fifo permissions 666 or
> > &
On Mon, Aug 7, 2023 at 9:14 PM Corinna Vinschen
wrote:
>
> On Aug 7 12:26, Brian Inglis via Cygwin wrote:
> > On 2023-08-07 08:42, Martin Wege via Cygwin wrote:
> > > We get a weird mkfifo failure in Cygwin on NTFS:
> > >
> > > /usr/bin/mkfifo -m 600 x.fi
On Aug 7 12:26, Brian Inglis via Cygwin wrote:
> On 2023-08-07 08:42, Martin Wege via Cygwin wrote:
> > We get a weird mkfifo failure in Cygwin on NTFS:
> >
> > /usr/bin/mkfifo -m 600 x.fifo
> > mkfifo: cannot set permissions of 'x.fifo': Not a directory
>
On 2023-08-07 08:42, Martin Wege via Cygwin wrote:
We get a weird mkfifo failure in Cygwin on NTFS:
/usr/bin/mkfifo -m 600 x.fifo
mkfifo: cannot set permissions of 'x.fifo': Not a directory
This error is also reproducible with default fifo permissions 666 or anything
else, and app
Hello,
We get a weird mkfifo failure in Cygwin on NTFS:
/usr/bin/mkfifo -m 600 x.fifo
mkfifo: cannot set permissions of 'x.fifo': Not a directory
Is there a known workaround? So far named fifos cannot be created somehow.
Thanks,
Martin
--
Problem reports: https://
On Apr 14 15:49, Eliot Moss via Cygwin wrote:
> At present I have:
>
> $ getfacl id_rsa2
> # file: id_rsa2
> # owner: moss
> # group: moss
> user::rw-
> group::---
> group:SYSTEM:r--#effective:---
> mask::---
> other::---
>
> $ icacls id_rsa2
> id_rsa2 NULL SID:(DENY)(Rc,DC)
> ELI
On Apr 14 15:43, Eliot Moss via Cygwin wrote:
> On 4/14/2023 3:11 PM, Corinna Vinschen via Cygwin wrote:
> > On Apr 13 23:03, Eliot Moss via Cygwin wrote:
> > > Dear cygwin'ers -
> > >
> > > I seem to be caught in a bind with the Cygwin permissions se
On 4/14/2023 3:43 PM, Eliot Moss via Cygwin wrote:
On 4/14/2023 3:11 PM, Corinna Vinschen via Cygwin wrote:
On Apr 13 23:03, Eliot Moss via Cygwin wrote:
Dear cygwin'ers -
I seem to be caught in a bind with the Cygwin permissions setup.
ssh insists that ~/.ssh/config have permissions no
On 4/14/2023 3:11 PM, Corinna Vinschen via Cygwin wrote:
On Apr 13 23:03, Eliot Moss via Cygwin wrote:
Dear cygwin'ers -
I seem to be caught in a bind with the Cygwin permissions setup.
ssh insists that ~/.ssh/config have permissions no less permissive than
rw--- (600).
Huh? N
On Apr 13 23:03, Eliot Moss via Cygwin wrote:
> Dear cygwin'ers -
>
> I seem to be caught in a bind with the Cygwin permissions setup.
>
> ssh insists that ~/.ssh/config have permissions no less permissive than
> rw--- (600).
Huh? No, it doesn't, usually. My f
On 4/13/2023 11:03 PM, Eliot Moss via Cygwin wrote:
Dear cygwin'ers -
I seem to be caught in a bind with the Cygwin permissions setup.
ssh insists that ~/.ssh/config have permissions no less permissive than
rw--- (600).
---> should have read no *more* permissive (sent too late
Dear cygwin'ers -
I seem to be caught in a bind with the Cygwin permissions setup.
ssh insists that ~/.ssh/config have permissions no less permissive than
rw--- (600).
However, my backup program runs as SYSTEM and needs access. I tried to
provide that access by adding an ACL g:SYSTE
I did read that upon installation.
But I read it more as:
"Cygwin is still available to multiple users, depending
on where you install it".
I did not expect it to apply when installing Cygwin into a
private home directory.
And maybe other people read it similar to how I read it.
But its also en
"C:\Users\user1\Downloads\cygwin_test1\"
Then all the directories and files have the read and execute
permissions for the "Everyone" SID.
This means a user2 on the same system can read files inside
"C:\Users\user1\Downloads\cygwin_test1\home\user1\"
It also mean
irectories and files have the read and execute
permissions for the "Everyone" SID.
This means a user2 on the same system can read files inside
"C:\Users\user1\Downloads\cygwin_test1\home\user1\"
It also means that user2 can use stuff in the cygwin install
such as bash, eve
mask(0).]
On Cygwin, however, I have to resort to good old chmod().
> Which is not necessarily related to the permissions on the file. Windows
> socket is an in-memory object, the file is used merely for naming purposes.
Sockets are in-memory objects everywhere. The UNIX socket file is a j
Greetings, Lavrentiev, Anton (NIH/NLM/NCBI) [C]!
>> what your test program was actually doing. But you seem to be assuming that
>> calling fchmod on a socket descriptor should affect the permissions on the
>> socket file (assuming the socket is bound). Is that documented an
On 7/2/2022 3:37 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
what your test program was actually doing. But you seem to be assuming that
calling fchmod on a socket descriptor should affect the permissions on the
socket file (assuming the socket is bound). Is that documented anywhere
> what your test program was actually doing. But you seem to be assuming that
> calling fchmod on a socket descriptor should affect the permissions on the
> socket file (assuming the socket is bound). Is that documented anywhere?
> POSIX
> says that the behavior of fch
ine! Which is why I call fchmod() to fix the permissions up,
and THAT does not work. BTW, should I have called chmod() instead (which
is what the command line chmod does), the permissions would have been
set correctly on the socket file, but fchmod() would have misreported
them again (this time lo
I forgot to mention that my "umask" is the standard 022...
The man page says that for directories with the ACLs, it is ignored.
So in my code bind() wouldn't have created the socket with 0777, and
that's fine! Which is why I call fchmod() to fix the permissions up,
and THAT
On 7/1/2022 11:23 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
That way I'm sure I won't have any surprises with permissions when working in
/cygdrive/g/cygwin. Do you want to try that and see if it makes a difference?
I have no problems with /cygdrive/g/cygwin -- my socket
> That way I'm sure I won't have any surprises with permissions when working in
> /cygdrive/g/cygwin. Do you want to try that and see if it makes a difference?
I have no problems with /cygdrive/g/cygwin -- my socket file gets created there
with proper
permissions and report
new).
So it was something like:
$ mkdir /cygdrive/g/cygwin
At this point the permissions on /cygdrive/g/cygwin are influenced by the ACL on
/cygdrive/g. What I would typically do in this situation is
getfacl ~ | setfacl -f - /cygdrive/g/cygwin
That way I'm sure I won't have any su
en for each $stuffdir I wanted moved
$ cd; tar cf - ./$stuffdir | (cd /cygdrive/g/cygwin; tar xvf -)
So, I have no idea why permissions there ended up all perplexed.
But please note that .socket gets created perfectly fine in that directory,
yet the problem occurs when that's a subdirectory, cr
On 7/1/2022 2:00 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
Lastly, I forgot to list all the involved directories as they look from under
Cygwin with their permissions,
if that's of any help:
$ ls -ld ~ ~/.socket ~/subdir ~/subdir/.socket
drwx--+ 1 ANTON None 0 Jul 1 13:36
On 7/1/2022 2:00 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
getfacl does not work even for the .socket "file" in my home directory for
which ~/sun works perfectly fine with permissions
(and all subdirectories crated with mkdir under it).
Also like I said, ~/sun also works perf
getfacl does not work even for the .socket "file" in my home directory for
which ~/sun works perfectly fine with permissions
(and all subdirectories crated with mkdir under it).
Also like I said, ~/sun also works perfectly fine in /cygdrive/g/cygwin/ but
not if I created a subdirector
ive/g? The failure of getfacl
suggests that Cygwin thinks the drive doesn't support ACLs, in which case it
might just be faking permissions (lying).
Ken
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https:
Hi all,
I am having an issue with socket file permissions...
So here's a mockup of code that shows the problem:
$ cat sun.c
#include
#include
#include
#include
#include
#include
#include
#define SOCKET "./.socket"
int main()
{
struct sockaddr_un addr;
On Fri, Jun 3, 2022 at 6:23 AM Brent Epp wrote:
I would think so too, but that doesn't appear to be happening. If it
> makes a difference, the SID actually starts with S-1-5-21. I have to
> manually take ownership in order to even access the files at all.
>
Explained another way: According to
htt
Brent Epp writes:
> This is essentially what happened (removable disk moved from one
> computer to another).
The server resource kit from M$ used to have a tool called SubInACL that
addresses exactly this situation (among other things). You give it a
set of old/new SID pairs and it will replace t
ble and I can't even take
ownership or change the permissions. I have to either restore them from
a backup or boot to a Linux environment to access them.
Windows displays "Account Unknown" (with a SID) in the ACL when it can't
resolve the SID reference.
There can be a number o
take
> ownership or change the permissions. I have to either restore them from
> a backup or boot to a Linux environment to access them.
>
Windows displays "Account Unknown" (with a SID) in the ACL when it can't
resolve the SID reference.
There can be a number of reasons for this
I'm getting all sorts of permissions issues with cygwin. I
did run the cygwin setup again to reinstall/upgrade.
First, I had restore my cygwin home directory from a backup, since it was
giving me permissions errors on .bash_history, .ssh, etc, but the biggest
headache is with git repos. Firs
Greetings, Brent Epp!
> I recently (finally) installed Windows 10 on my system (clean install).
> All of my files are stored in on a secondary drive/partition, on which
> cygwin is also installed. I expected to be able to just pick up where I
> left off, but I'm getting all sor
I recently (finally) installed Windows 10 on my system (clean install).
All of my files are stored in on a secondary drive/partition, on which
cygwin is also installed. I expected to be able to just pick up where I
left off, but I'm getting all sorts of permissions issues with cygwin.
On 2022-02-10 09:48, Rob Stevens wrote:
Whenever I create files with cygwin (using whatever utilitity or editor)
I get these permissions as reported by icacls:
NULL SID:(DENY)(Rc,S,X,DC)
MALIN\rob:(R,W,D,WDAC,WO)
NT AUTHORITY\SYSTEM:(DENY)(S,X)
BUILTIN\Administrators:(DENY)(S,X
On 10.02.2022 17:48, Rob Stevens wrote:
Whenever I create files with cygwin (using whatever utilitity or editor)
I get these permissions as reported by icacls:
NULL SID:(DENY)(Rc,S,X,DC)
MALIN\rob:(R,W,D,WDAC,WO)
NT AUTHORITY\SYSTEM:(DENY)(S,X)
BUILTIN\Administrators:(DENY)(S,X
Whenever I create files with cygwin (using whatever utilitity or editor)
I get these permissions as reported by icacls:
NULL SID:(DENY)(Rc,S,X,DC)
MALIN\rob:(R,W,D,WDAC,WO)
NT AUTHORITY\SYSTEM:(DENY)(S,X)
BUILTIN\Administrators:(DENY)(S,X)
MALIN\None:(R)
NT AUTHORITY\SYSTEM:(RX,W
956008885-3418522649-1831038044-1853292631-2271478464)(A;ID;FA;;;SY)(A;OICIIOID;GA;;;SY)(A;ID;FA;;;BA)(A;OICIIOID;GA;;;BA)(A;ID;0x1200a9;;;BU)(A;OICIIOID;GXGR;;;BU)(A;OICIIOID;GA;;;CO)
> >
> > -
> > Any thoughts on what might be wrong here?
>
> Again, the pe
1 - 100 of 1441 matches
Mail list logo
