David Goldberg writes:
> Thanks but unfortunately even after don't that I still get the complaint
> that they're is a self signed certificate in the chain. We do indeed run
> our own CA but it seems like that should not really be a problem.
Wait, are you saying you do run a private CA, but the LDA
On 2019-08-02 15:58, Eric Blake wrote:
> On 8/2/19 4:53 PM, Ken Brown wrote:
>
Putting this all together, Eric's explanation is indeed correct. All
processes created by xwin-xdg-menu via fork/exec inherit the property of
ignoring SIGPIPE.
I don't know if this is a bug, bu
One downside of having to do non-work email on my phone while at work is
that I didn't realize my reply to Quanah was direct, not to the list.
Sorry about that. Trying again:
I did the following to try to answer
$ ldd /usr/bin/ldapsearch.exe # 2.4.42
ntdll.dll => /cygdrive/c/WINDOWS/SYS
On 8/2/19 4:53 PM, Ken Brown wrote:
>>> Putting this all together, Eric's explanation is indeed correct. All
>>> processes created by xwin-xdg-menu via fork/exec inherit the property of
>>> ignoring SIGPIPE.
>>>
>>> I don't know if this is a bug, but it certainly leads to surprising
>>> behavior.
On 8/2/2019 5:26 PM, Brian Inglis wrote:
> On 2019-08-02 08:34, Ken Brown wrote:
>> On 8/1/2019 10:32 PM, Ken Brown wrote:
>>> On 8/1/2019 5:17 PM, Ken Brown wrote:
On 8/1/2019 12:04 PM, Corinna Vinschen wrote:
> On Aug 1 10:38, Eric Blake wrote:
>> Could it be a case of xwin-xdg-menu
On 2019-08-02 08:34, Ken Brown wrote:
> On 8/1/2019 10:32 PM, Ken Brown wrote:
>> On 8/1/2019 5:17 PM, Ken Brown wrote:
>>> On 8/1/2019 12:04 PM, Corinna Vinschen wrote:
On Aug 1 10:38, Eric Blake wrote:
> Could it be a case of xwin-xdg-menu calling signal(SIGPIPE, SIG_IGN) or
> simil
Code Example:
#include
#include
#include
#include
#include
#include int main()
{
// https://github.com/msys2/MSYS2-packages/issues/1711
char buf[50];
char * str = gcvt(3.141592653589793238462643383279502884197169399375, 49, buf);
printf("buffer: %s", str);// https://github.com/msys2/MSYS2-pac
Thanks but unfortunately even after don't that I still get the complaint
that they're is a self signed certificate in the chain. We do indeed run
our own CA but it seems like that should not really be a problem.
On Fri, Aug 2, 2019, 15:13 Achim Gratz wrote:
> David Goldberg writes:
> > I updated
David Goldberg writes:
> I updated openldap from 2.4.42-1 to 2.4.48-1 this morning and now
> ldapsearch will not connect, complaining that the server provided
> certificate is self signed. I have set up /etc/pki with my company's
> certificate chain and that allows 2.4.42-1 (and earlier) and other
KAVALAGIOS Panagiotis (EEAS-EXT) writes:
> I have also switched the order of the mentioned options to no avail.
Hmm. I tried that again today and it worked correctly regardless of the
order of options. Funky… :-(
> I am including the "setup.log.full" with --verbose option for further
> investi
--On Friday, August 02, 2019 12:45 PM -0400 David Goldberg
wrote:
I updated openldap from 2.4.42-1 to 2.4.48-1 this morning and now
ldapsearch will not connect, complaining that the server provided
certificate is self signed. I have set up /etc/pki with my company's
certificate chain and that
Hi – I have one password protected WinRAR Zip file, unfortunately I forget the
password.
Please help me out.
Look forward for your earliest response...
Best Regards
Sandeep Mehta
+91 9971792377
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.co
I updated openldap from 2.4.42-1 to 2.4.48-1 this morning and now
ldapsearch will not connect, complaining that the server provided
certificate is self signed. I have set up /etc/pki with my company's
certificate chain and that allows 2.4.42-1 (and earlier) and other
applications to properly authen
On Aug 2 14:34, Ken Brown wrote:
> On 8/1/2019 10:32 PM, Ken Brown wrote:
> > On 8/1/2019 5:17 PM, Ken Brown wrote:
> >> On 8/1/2019 12:04 PM, Corinna Vinschen wrote:
> >>> On Aug 1 10:38, Eric Blake wrote:
> Could it be a case of xwin-xdg-menu calling signal(SIGPIPE, SIG_IGN) or
> simi
On 8/1/2019 10:32 PM, Ken Brown wrote:
> On 8/1/2019 5:17 PM, Ken Brown wrote:
>> On 8/1/2019 12:04 PM, Corinna Vinschen wrote:
>>> On Aug 1 10:38, Eric Blake wrote:
Could it be a case of xwin-xdg-menu calling signal(SIGPIPE, SIG_IGN) or
similar, and accidentally letting grep inherit the
15 matches
Mail list logo
