Hi. Correct me if I'm wrong but POSIX appears to define
https://pubs.opengroup.org/onlinepubs/7908799/xsh/ucontext.h.html
as, among other things, containing the field:
sigset_tuc_sigmask the set of signals that are blocked when this
context is active
and it also spe
On Apr 3 11:27, Petr Skočík wrote:
> Hi. Correct me if I'm wrong but POSIX appears to define
>
> https://pubs.opengroup.org/onlinepubs/7908799/xsh/ucontext.h.html
>
> as, among other things, containing the field:
>
> sigset_tuc_sigmask the set of signals that are blocked when this
>
On 05.03.2019 17:23, LRN wrote:
> On 05.03.2019 17:07, E. Madison Bray wrote:
>>
>> If they're clean, worthwhile patches then I absolutely think you
>> should get them integrated upstream if at all possible--that's almost
>> always preferable.
>
> Okay, i'll see what i can do.
>
Made some progre
On Apr 3 14:15, Corinna Vinschen wrote:
> On Apr 3 11:27, Petr Skočík wrote:
> > Hi. Correct me if I'm wrong but POSIX appears to define
> >
> > https://pubs.opengroup.org/onlinepubs/7908799/xsh/ucontext.h.html
> >
> > as, among other things, containing the field:
> >
> > sigset_tuc_sigmas
> On Apr 3 14:15, Corinna Vinschen wrote:
> > On Apr 3 11:27, Petr Skočík wrote:
> > > Hi. Correct me if I'm wrong but POSIX appears to define
> > >
> > > https://pubs.opengroup.org/onlinepubs/7908799/xsh/ucontext.h.html
> > >
> > > as, among other things, containing the field:
> > >
> > > sigset
Greetings, All!
This can be considered "working by design", but it really imposes some serious
restrictions on interoperability with Cygwin, that I think can be avoided.
...
After some further testing, this seems to be affecting IP-based UNC paths
only.
The essence is this:
$ dir "\\192.168.1.
On Apr 3 16:39, Petr Skočík wrote:
> > On Apr 3 14:15, Corinna Vinschen wrote:
> > > On Apr 3 11:27, Petr Skočík wrote:
> > > > Hi. Correct me if I'm wrong but POSIX appears to define
> > > >
> > > > https://pubs.opengroup.org/onlinepubs/7908799/xsh/ucontext.h.html
> > > >
> > > > as, among othe
On Apr 3 19:20, Andrey Repin wrote:
> Greetings, All!
>
> This can be considered "working by design", but it really imposes some serious
> restrictions on interoperability with Cygwin, that I think can be avoided.
>
> ...
>
> After some further testing, this seems to be affecting IP-based UNC p
Andrey Repin writes:
> This can be considered "working by design", but it really imposes some serious
> restrictions on interoperability with Cygwin, that I think can be avoided.
But cygpath never sees the quotes, so whatever is done to the path that
it gets is actually the work of your shell. In
Not completely the shell.
From a Windows command prompt:
c:\Apps\cygwin64\bin\cygpath.exe -u
\\123.456.789.321\wwwroot\ccenter\bin\online.sh
//123.456.789.321/wwwroot/ccenter/bin/online.sh
c:\Apps\cygwin64\bin\cygpath.exe -u
"\\123.456.789.321\wwwroot\ccenter\bin\online.sh"
/cygdrive/c/123.45
On 2019-04-03 12:20 pm, Andrey Repin wrote:
Greetings, All!
This can be considered "working by design", but it really imposes some
serious
restrictions on interoperability with Cygwin, that I think can be
avoided.
...
After some further testing, this seems to be affecting IP-based UNC
path
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
12 matches
Mail list logo