search for: negoiation

I have a new pcap from beginning to the end with openldap "TLS negoiation failed" https://gwarband.de/openldap/tracefile.dump The sourceports are 45376 and 45377 Tobias Am 2017-03-20 19:59, schrieb Aki Tuomi: > Well, those actually *reduce* the possible algorithms that can be > used, so uncommenting those can make things worse. > > Anyways, your pca...

...m > > The failed attempts are really short, indicating a VERY early problem > with SSL handshake. > > Aki > >> On March 20, 2017 at 9:24 PM info at gwarband.de wrote: >> >> >> I have a new pcap from beginning to the end with openldap "TLS >> negoiation failed" >> >> https://gwarband.de/openldap/tracefile.dump >> >> The sourceports are 45376 and 45377 >> >> Tobias >> >> Am 2017-03-20 19:59, schrieb Aki Tuomi: >>> Well, those actually *reduce* the possible algorithms that can be >...

...AN2.1) and security mode 0x01 (plaintext password) - client sent "session setup andx request" - server sent "session setup andx response" - continued When it's from non-working Windows 2000 server, this is the sequence. Note client closed connection after receiving protocol negoiation results. - client started netbios session, server responded back - client sent "negotiate protocol request" - server sent "negotiate protocol response" with dialect index 5 (>LANMAN2.1) and security mode 0x01 (plaintext password) - client closed connection, sent FIN - client...

...ou provide namei -l /etc/ssl/certs/LetsEncrypt.pem The failed attempts are really short, indicating a VERY early problem with SSL handshake. Aki > On March 20, 2017 at 9:24 PM info at gwarband.de wrote: > > > I have a new pcap from beginning to the end with openldap "TLS > negoiation failed" > > https://gwarband.de/openldap/tracefile.dump > > The sourceports are 45376 and 45377 > > Tobias > > Am 2017-03-20 19:59, schrieb Aki Tuomi: > > Well, those actually *reduce* the possible algorithms that can be > > used, so uncommenting those c...

...are really short, indicating a VERY early problem >> with SSL handshake. >> >> Aki >> >>> On March 20, 2017 at 9:24 PM info at gwarband.de wrote: >>> >>> >>> I have a new pcap from beginning to the end with openldap "TLS >>> negoiation failed" >>> >>> https://gwarband.de/openldap/tracefile.dump >>> >>> The sourceports are 45376 and 45377 >>> >>> Tobias >>> >>> Am 2017-03-20 19:59, schrieb Aki Tuomi: >>>> Well, those actually *reduce* the poss...

[I know this is the 'port' list, but I can't find a better place to post this, and with the garbage going on @slashdot I figured I'd get this out. This belongs on sci.crypt or a general OpenSSH mailing list] First, a quick rehash of stuff everyone here already knows, OpenSSH can use two major forms of authentication: 1. Password 2. RSA keys The RSA method is good because it

I have also tested with 2.2.28 and this version has the same issue. The finding of compatible ciphers is not the problem because I have uncommented the ldap entrys: TLSCipherSuite SECURE128:-ARCFOUR-128:-CAMELLIA-128-CBC:-3DES-CBC:-CAMELLIA-128-GCM TLSProtocolMin 3.1 Maybe you have further ideas. Am 2017-03-20 17:42, schrieb Aki Tuomi: >> On March 20, 2017 at 5:28 PM

Hi all! I have searched through the archives and have not found an answer to this, but it is also possible I wasn't searching for the right thing, so here goes. I am running samba 2.2.7a on a RH 9 box. I am having issues with transfer speeds on my shares. I have the shares mapped to drives on my XP box. When coping files from the XP -> linux, The speed is great. But from linux->XP

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and