Greetings, Bill Stewart!
> On Mon, Mar 11, 2019 at 3:38 PM Achim Gratz wrote:
>> Try it with a group that has several hundred members. Then try with
>> several hundreds of such groups. Then try it again over a DSL line or
>> some VPN routing you across the globe that has a roundtrip measured
On Mon, Mar 11, 2019 at 3:38 PM Achim Gratz wrote:
> Try it with a group that has several hundred members. Then try with
> several hundreds of such groups. Then try it again over a DSL line or
> some VPN routing you across the globe that has a roundtrip measured in
> tenths of seconds.
Bill Stewart writes:
> FWIW, not sure if you're using the IADsNameTranslate interface (
> https://docs.microsoft.com/en-us/windows/desktop/api/iads/nn-iads-iadsnametranslate).
[…]
> Init depends on a available AD server (GC in this example), of course, but
> seems pretty fast in my tests.
Try it
On Thu, Feb 28, 2019 at 2:39 AM Corinna Vinschen wrote:
> > Since windows seems to adhere to the rule:
> > "Case preserving", but "case ignoring", what does it
> > mean to make sure all user and group names are
> > case-correct?
>
> This all started here:
>
On 2/28/2019 1:39 AM, Corinna Vinschen wrote:
This is all more or less moot as soon as OpenSSH 8.0 comes out, which
will contain patches to handle user and group names case-insensitive,
finally.
Please forgive my ignorance of cygwin's internals, but why does
cygwin1.dll need to do anything on
On Feb 27 19:11, L A Walsh wrote:
> On 2/27/2019 12:50 PM, Corinna Vinschen wrote:
> > The fix was this one:
> > https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=18c203fb6eb
> > Corinna
> >
> >
>
> My question would be related to the comment with the fix:
>
> "made sure all
On 2/27/2019 12:50 PM, Corinna Vinschen wrote:
> The fix was this one:
> https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=18c203fb6eb
> Corinna
>
>
My question would be related to the comment with the fix:
"made sure all user and group names are case-correct"
Since windows
On 2/27/2019 12:50 PM, Corinna Vinschen wrote:
Apparently same problem as reported in
https://cygwin.com/ml/cygwin/2019-02/msg00301.html
The fix was this one:
https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=18c203fb6eb
Thanks. Yeah, our AD has 152 groups.
--
Problem reports:
On Feb 27 12:44, Jerry Baker via cygwin wrote:
> On 2/27/2019 12:23 PM, Jerry Baker via cygwin wrote:
> > I am also happy to report that cygwin1-20190226.dll fixes the issue.
>
> For the curious, the fix happened between cygwin1-20190219.dll and
> cygwin1-20190223.dll.
>
> Maybe the changes in
On 2/27/2019 12:23 PM, Jerry Baker via cygwin wrote:
I am also happy to report that cygwin1-20190226.dll fixes the issue.
For the curious, the fix happened between cygwin1-20190219.dll and
cygwin1-20190223.dll.
Maybe the changes in sec_auth.cc. They look suspicious.
--
Problem reports:
On 2/27/19 2:19 PM, Jerry Baker via cygwin wrote:
> On 2/26/2019 10:55 PM, Brian Inglis wrote:
>> As Cygwin is a rolling release system, if you are not running current
>> releases,
>> some CVE security issues may remain unpatched, and your system may not be
>> compliant to your corporate security
On 2/27/2019 12:19 PM, Jerry Baker via cygwin wrote:
I narrowed it down to my network. If I unplug the Ethernet cable the
problem disappears. If I plug it in, the problem returns. I can
reproduce it 100% for an hour straight, going back and forth.
I am also happy to report that
On 2/26/2019 10:55 PM, Brian Inglis wrote:
As Cygwin is a rolling release system, if you are not running current releases,
some CVE security issues may remain unpatched, and your system may not be
compliant to your corporate security policies (you may want to check with your
IT security and/or
On Wed, Feb 27, 2019 at 4:45 AM Steven Penny wrote:
>
> On Tue, 26 Feb 2019 19:21:15, "Jerry Baker via cygwin" wrote:
> > Well I guess it's a good thing there's only one possible state of
> > Windows 7 x64 which allows us to determine that there's no possibility
> > of a bug simply by running a
On 2019-02-26 16:00, Jerry Baker via cygwin wrote:
> On 2/26/2019 2:48 PM, Doug Henderson wrote:
>> Good. This tells us something important. Right after the path listing,
>> cygcheck list "Output from C:\cygwin64\bin\id.exe". The id exe is a
>> cygwin exe which uses cygwin1.dll, cygintl-8.dll, and
On Tue, 26 Feb 2019 18:01:27, Jerry Baker via cygwin" wrote:
> Trying to think of what could make 2.11.x work and 3.0.1 fail on the i7
> system. The only difference I can think of is that the i7 system is a
> member of a domain.
(first I would suggest a good night's sleep :-)
If you really
> On Feb 26, 2019, at 8:55 PM, Jerry Baker wrote:
>
> I don't work for free,
This is open source. Given that the people here do, that's not a very good
argument.
> especially for hostile people with over inflated egos and crippling social
> disorders.
Don't feed it by arguing.
> The onus is
On Tue, 26 Feb 2019 19:21:15, "Jerry Baker via cygwin" wrote:
Well I guess it's a good thing there's only one possible state of
Windows 7 x64 which allows us to determine that there's no possibility
of a bug simply by running a single instance in one VM. We're going to
turn the world of unit
On 2/26/2019 7:12 PM, Doug Henderson wrote:
There is one more place you could have a problem. It does not seem
likely, but maybe you have a bad download cache area.
When you run setup, on the fourth panel, where it asks for the Local
Package Directory, you could try deleting that directory. (It
On 2/26/2019 7:05 PM, Steven Penny wrote:
On Tue, 26 Feb 2019 18:55:56, "Jerry Baker via cygwin" wrote:
Not really. I don't work for free, especially for hostile people with
over inflated egos and crippling social disorders.
https://yourlogicalfallacyis.com/ad-hominem
The onus is on whoever
On Tue, 26 Feb 2019 at 19:01, Jerry Baker via cygwin <> wrote:
>
> On 2/26/2019 5:50 PM, Jerry Baker via cygwin wrote:
> > Glad to. Please let me know what evidence will suffice to prove that.
> >
> > If it is my system our organization is going to have bigger issues.
> > There are about 3,700
On Tue, 26 Feb 2019 18:55:56, "Jerry Baker via cygwin" wrote:
Not really. I don't work for free, especially for hostile people with
over inflated egos and crippling social disorders.
https://yourlogicalfallacyis.com/ad-hominem
The onus is on whoever is interested in having cygwin work in this
On 2/26/2019 6:43 PM, Steven Penny wrote:
i would like to make that last point vividly clear: its on you to do that
testing. ive already given a clear refutation of your original point, so
the
ball is now squarely in your court.
Not really. I don't work for free, especially for hostile
On Tue, 26 Feb 2019 17:50:10, "Jerry Baker via cygwin" wrote:
Glad to. Please let me know what evidence will suffice to prove that.
pretty simple
1. get the Windows 7 x64 from here
https://softlay.net/operating-system/windows-7-download.html
2. get virtualbox from here
https://virtualbox.org
On 2/26/2019 5:50 PM, Jerry Baker via cygwin wrote:
Glad to. Please let me know what evidence will suffice to prove that.
If it is my system our organization is going to have bigger issues.
There are about 3,700 workstations with this machine image just in this
building.
Problem machine is
On 2/26/2019 5:17 PM, Steven Penny wrote:
you know i just finished reading this entire thread and its kind of
depressing.
7 replies from 5 people, and not one person explicitly answered the
implicit,
most important, and frankly only question worth answering:
Can anyone else reproduce this
On Tue, 26 Feb 2019 15:00:03, "Jerry Baker via cygwin" wrote:
It's just cygwin1.dll for sure. I can replace that with 2.x version and
everything works fine.
I don't recognize most of the BLODAs and not running any of them that I
know of. Are there any software packages known to interfere with
On 2/26/2019 2:48 PM, Doug Henderson wrote:
Good. This tells us something important. Right after the path listing,
cygcheck list "Output from C:\cygwin64\bin\id.exe". The id exe is a
cygwin exe which uses cygwin1.dll, cygintl-8.dll, and cygiconv-2.dll.
That narrow the problem. These three DLLs
On Tue, 26 Feb 2019 at 15:10, Jerry Baker via cygwin <> wrote:
>
> On 2/26/2019 1:56 PM, Doug Henderson wrote:
> > Two things.
> > 1. You can execute cygcheck by navigating to C:\cygwin or C:\cygwin64
> > in Explorer and opening a command or powershell window from explorer's
> > shift-context
On 2/26/2019 2:10 PM, Jerry Baker wrote:
Thanks for the tips. I made a completely fresh install in a new
directory and attempted all three suggestions. Here are the results:
1. That command gets part way through and then hangs with the blinking
cursor after listing the directories in the path
On 2/26/2019 1:56 PM, Doug Henderson wrote:
Two things.
1. You can execute cygcheck by navigating to C:\cygwin or C:\cygwin64
in Explorer and opening a command or powershell window from explorer's
shift-context menu. There, run the following command:
.\cygcheck.exe -csr >
On Tue, 26 Feb 2019 at 13:00, Jerry Baker via cygwin <> wrote:
>
> On 2/26/2019 11:32 AM, Jerry Baker via cygwin wrote:
> > Yes, but by wiping out the whole tree and installing 64-bit. You filled
> > me with doubt, so I browsed around with a hex editor looking at quite a
> > few random executables
> On Feb 26, 2019, at 2:00 PM, Jerry Baker wrote:
>
> I just installed from scratch in a new directory. Same issue. Nothing runs.
If cygcheck doesn't run, then it would appear there's (at least) something
non-cygwin-related
going on. cygcheck isn't a cygwin program, i.e. it doesn't link to or
On 2/26/2019 11:32 AM, Jerry Baker via cygwin wrote:
Yes, but by wiping out the whole tree and installing 64-bit. You filled
me with doubt, so I browsed around with a hex editor looking at quite a
few random executables and dll files in cygwin\bin and all of them I
checked are 64-bit.
I just
On 2/26/2019 11:19 AM, Ken Brown wrote:
Here's a wild guess, based on the fact that your Cygwin installation is in
C:\cygwin rather than C:\cygwin64. Do you have a 32-bit Cygwin installation
that you updated using setup-x86_x64.exe instead of setup-x86.exe?
Yes, but by wiping out the whole
On 2/26/2019 1:59 PM, Jerry Baker via cygwin wrote:
> On 2/26/2019 10:44 AM, Vince Rice wrote:
>> What is also described on the page are the reporting guidelines. Please read
>> them again, paying special
>> attention to the bolded part.
Here's a wild guess, based on the fact that your Cygwin
On 2/26/2019 10:44 AM, Vince Rice wrote:
What is also described on the page are the reporting guidelines. Please read
them again, paying special
attention to the bolded part.
That command has the same problem under 3.0.0.1-1 as all the others.
Under 2.11.2-1 it is as follows:
-
Cygwin
> On Feb 26, 2019, at 12:37 PM, Jerry Baker wrote:
>
> That's why you're reading about it "on the appropriate list," as described on
> that page. It's a take it or leave it thing. I report it, and the cygwin
> community can do whatever they like with it - ignore it, investigate it,
> shoot the
On Tue, Feb 26, 2019 at 12:38 PM Jerry Baker via cygwin
wrote:
>
> That's why you're reading about it "on the appropriate list," as
> described on that page. It's a take it or leave it thing. I report it,
> and the cygwin community can do whatever they like with it - ignore it,
> investigate it,
On 2/26/2019 10:30 AM, Houder wrote:
Jerry, short answer:
--
Problem reports: http://cygwin.com/problems.html
^^^
^^^
^^^
> On 2/26/2019 7:38 AM, Jerry Baker via cygwin wrote:
> > I have a large installation of cygwin on Windows 7 x64 for the last
> > decade that has been working without issue. When I use setup-x86_64.exe
> > (2.895) to upgrade the cygwin 2.11.2-1 package to cygwin 3.0.1-1, all of
> > my cygwin
I have narrowed it down to cygwin1.dll. If I install cygwin 3.0.1-1 and
overwrite cygwin1.dll with the 2.11.2-1 version, everything works.
Likewise, if I install cygwin 2.11.2-1 and overwrite cygwin1.dll with
the 3.0.1-1 version everything stops working.
Additional information about the
I have a large installation of cygwin on Windows 7 x64 for the last
decade that has been working without issue. When I use setup-x86_64.exe
(2.895) to upgrade the cygwin 2.11.2-1 package to cygwin 3.0.1-1, all of
my cygwin applications stop working. Simply executing a command (such as
'bash'
43 matches
Mail list logo
