similar to: Fwd: handshake problem

Hi, ldapsearch with an ldaps-URL stopped working recently, probably with the update from openssl 1.0.0 to openssl 1.0.1. On a server with up-to-date packages (openssl-1.0.1e-16.el6_5.x86_64, openldap-clients-2.4.23-32.el6_4.1.x86_64) I get the following errors when issuing an ldapsearch (some parts anonymized): [bad]# ldapsearch -H "ldaps://ldap.domain.org:6636/" -D <binddn>

Similar to --no-sr, it can be handy for testing a client implementation to have a server that can easily be forced into older behaviors, without having to recompile a one-off hack into a server or dig up an older server binary that lacked a newer feature. To see the patch in action, try things like: $ ./nbdkit -U - -fv --mask-handshake=0 null \ --run 'qemu-nbd --list -k $unixsocket'

Another new issue has cropped up with my rc1 -> rc31 upgrade: This morning, right around the typical morning email surge, Dovecot stopped accepting new IMAP connections. I didn't get a chance to do much troubleshooting and a restart of Dovecot fixed it. The only thing I've been able to find in the logs is a bunch of entries like this one: Apr 10 09:11:36 cliff dovecot: imap-login:

Hello I have that kind of messages in dovecot.log anyone has those troubles ? the machine is Debian etch 64 bits dovecot 1.2.5 has been compiled on the machine it run NIS client to a YPLDAPD server thank you Oct 02 12:15:27 auth(default): Error: do_ypcall: clnt_call: RPC: Timed out Oct 02 12:15:33 pop3-login: Error: Timeout waiting for handshake from auth server. my pid=16755, input bytes=0

Hello, Upgraded from 1.2.x to 2.0.5, converted configuration as described in http://wiki2.dovecot.org/Upgrading/2.0 and now I'm unable to log in to imap server. Dovecot error.log shows: Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13338, input bytes=0 Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my

Dear OpenSSH team, First of all thanks a lot for your good work on developing such a usable peace of software. Nice job. As you may know, we have some issues using OpenSSH in Iran. Recently the government did some packet filtering on some protocols, including SSH. We don't know what exactly they've done but it appears to be some routing rule that prevents SSH protocol to initiate a

I doubt whether there is any fixed algorithm given while generating certificates. I used RSA 1024 bit. On Wed, Nov 19, 2014 at 11:42 AM, Ajitha Robert <ajitharobert01@gmail.com> wrote: > > Hi all, > > I am facing an error while connecting libvirt remotely using tls.. I have created CA, client and server certificates with RSA 1024 bit using Openssl. I am using debian linux

After building and install dovecot I then made my own self signed SSL certs and placed them carefully into the correct places : Thus : # grep -v "^#" dovecot-openssl.cnf | grep -v "^$" [ req ] default_bits = 1024 encrypt_key = yes distinguished_name = req_dn x509_extensions = cert_type prompt = no [ req_dn ] C=CA ST=Ontario L=Toronto O=Blastwave OU=IMAP server

Hi all, I am facing an error while connecting libvirt remotely using tls.. I have created CA, client and server certificates with RSA 1024 bit using Openssl. I am using debian linux flavor in both client and server. *Original Error:* (When trying to connect remote libvirt) virsh -c xen+tls://destinationipaddr/system error: failed to connect to the hypervisor error: authentication failed: TLS

Dear all, I am trying to setup Dovecot with GSSAPI support. For testing purposes gssapi is the only method allowed for login. As I cannot login to my mailbox, I'vo got two questions about the following log entries: dovecot: Info: auth-worker(default): passwd-file /dovecot/store/db/test-userdb: Read 3 users dovecot: Info: auth(default): new auth connection: pid=3915 dovecot: Info:

Hi, I tracked down a tricky bug in dovecot that can cause the imap-login and pop3-login processes to crash on handshake failures. This can be tested by disabling SSLv3 in the dovecot config (ssl_protocols = !SSLv2 !SSLv3) and trying to connect with openssl and forced sslv3 (openssl s_client -ssl3 -connect localhost:995). This would cause a crash. What was going on is this: In

This is strange... Do you have SSL aktive on both systems? Run nrpr localy without parameters (this should return some nrpe stats) and check ldd for libssl. Am 01.05.2015 07:32 schrieb "Tim Dunphy" <bluethundr at gmail.com>: > Hi Eric, > > Thanks for your reply. I do have nrpe running under xinetd on the host I'm > trying to monitor. > > And running the

Hi list, I recently tried to backup mailboxes from an older server machine to a new one in order to move the service to the new machine. Both machines are in the same LAN, I used this command: dsync -R -u username backup ssh -i .ssh/id_rsa username at 192.168.1.11 /opt/local/bin/dsync and I get this error: dsync-local(dz): Error: Invalid server handshake: dsync-server 2 dsync-remote(dz):

On R 3.2.5, 3.3.2 and devel for Windows, R CMD check --as-cran gives me: Found the following (possibly) invalid URLs: URL: https://www.stat.auckland.ac.nz/~paul/Reports/DisplayList/dl-record.html From: man/capturePlot.Rd Status: Error Message: libcurl error code 35 error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure This is reported both by the

The issue: ruby-1.8.7 (compiled from src, not rpm) can''t connect to mysql-5.1.58: "Mysql::Error: #08S01Bad handshake" Environment: Linux Fedora Core 12 (or 14, does not matter) remote database server (different host) mysql-5.1.58 Ruby 1.8.7: wget ftp://ftp.ruby-lang.org/pub/ruby/1.8/ruby-1.8.7-p352.tar.gz tar -xzvf ruby-1.8.7-p352.tar.gz cd ruby-1.8.7-p352 ./configure

We had something similar, and as far as I recall the problem turned out to be that we had not set the config file to allow remote connections. This would probably be better put on the Rosuda mailing list: http://mailman.rz.uni-augsburg.de/mailman/listinfo/stats-rosuda-devel Hope this helps, Matt Wiener -----Original Message----- From: r-help-bounces at stat.math.ethz.ch [mailto:r-help-bounces

Hi Does the deamon run under xinetd? Then you have to configure the only_from in */etc/**xinetd.d**/**nrpe* to. Regards Eric Am 01.05.2015 06:46 schrieb "Tim Dunphy" <bluethundr at gmail.com>: > Hello, > > I am trying to monitor a host in the Amazon EC2 cloud. > > Yet when I try to check NRPE from the monitoring host I am getting an SSL > handshake error:

Hi everybody, I'm using dovecot-2.2.11 on NetBSD. After a kernel upgrade, while using the same dovecot binaries (they were working perfectly until today), I'm experiencing this error (more log at the end of my email): BUG: Authentication client sent unknown handshake command: REQUEST?227672066?18807?2?c717631d60216b2e9ec57a2fa69674b8?session_pid=16343?... I tried to build a newer

Hi All, I am using "asterisk-11.12.0" version and I am trying to setup secure call (TLS + SRTP) between two extensions and while making a call, I got following error *CLI> == Using SIP RTP CoS mark 5 -- Executing [6004 at from-office:1] Dial("SIP/6003-00000000", "SIP/6004,20") in new stack == Using SIP RTP CoS mark 5 -- Called SIP/6004 SSL certificate