similar to: All DomU failing SSLv3 handshake (curl, apt-get, wget, etc.) but OK on Dom0

Displaying 20 results from an estimated 11000 matches similar to: "All DomU failing SSLv3 handshake (curl, apt-get, wget, etc.) but OK on Dom0"

2016 Nov 07
1
R CMD check --as-cran: sslv3 alert handshake failure
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
2014 Nov 02
1
sslv3 alert handshake failure error
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
2010 Sep 16
1
'sslv3 alert handshake failure' when using puppet load-balanced through Apache
I''ve setup a puppet load-balanced solution based on these instructions: http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Scalability I have 4 puppetmaster instances running on my puppet server and an Apache instance running on that server listening on port 8140 and round-robining the requests from puppet clients. This works fine for all my existing client machines. The problem
2020 Jan 17
1
[PATCH nbdkit] Add cainfo and capath options to curl plugin
This change adds cainfo and capath options to the curl plugin. They refer directly to CURLOPT_CAINFO and CURLOPT_CAPATH, as documented in libcurl. Signed-off-by: Wiktor Gołgowski <wiktor.golgowski@linux.intel.com> --- plugins/curl/curl.c | 16 ++++++++++++++++ plugins/curl/nbdkit-curl-plugin.pod | 9 +++++++++ 2 files changed, 25 insertions(+) diff --git
2010 Sep 29
5
err: Could not request certificate: sslv3 alert handshake failure error
Hi, I''ve setup the puppetmaster to start 5 processes each listening on a different port, with an Apache server in front. This works fine for existing clients, however when I try to add a new client (ie. a newly installed machine with no previous puppet configuration) I get this error: err: Could not request certificate: sslv3 alert handshake failure error Any ideas what''s
2020 Mar 30
2
doveadm backup from gmail with imapc
I am trying to backup a gmail account (not the one I am writing from) to dovecot, using doveadm-backup and imapc, but am having ssl connection problems. ted at expectation:~# doveadm backup -D -R -u ted imapc: dsync(ted): Info: imapc(imap.gmail.com:993): Connected to 74.125.71.108:993 (local 10.7.1.179:53852) dsync(ted): Warning: imapc(imap.gmail.com:993): Server disconnected unexpectedly:
2014 Oct 18
0
curl: (35) Cannot communicate securely with peer:
Hello I am stumped. I am trying to us the kraxel qemu repository, it appears the repository moved to secure server since then I have not been able to configure this properly. https://www.kraxel.org/repos/jenkins/ I receive the following error when I try to use the repository curl: (35) Cannot communicate securely with peer: no common encryption algorithm(s). I have discovered this problem on
2011 Sep 27
2
Matrix and list indices
Hi guys, I am trying to replace all elements of earth that are equal to zero with their corresponding elements in mars. I can do the replace with a bunch of for-loops, but I don't think this is the R way of doing things. my_list <- list( earth=array(c(0,0,45,0,0,45,0,45),dim=c(2,2,2)), mars=array(c(8:1),dim=c(2,2,2))) my_list for (i in c(1:2)) { for (j in c(1:2)) {
2020 Jul 20
1
Re: [PATCH nbdkit v2] curl: Implement header and cookie scripts.
On 7/15/20 3:53 PM, Richard W.M. Jones wrote: > This rather complex feature solves a problem for certain web services > that require a cookie or token for access, especially one which must > be periodically renewed. > > For motivation for this feature see the included documentation, and > item (1)(b) here: > >
2016 Nov 10
2
service doveadm : ssl problems
Hello, I'm using dovecot 2.2.13 on Debian stable. My users are authenticated through PAM, and stored in an LDAP backend I'm trying to set-up replication with ssl, following (mainly) this : http://wiki2.dovecot.org/Replication 1) I only diverted from the instructed setup by not setting "doveadm_port = 12345", as it would give me errors of the like: > Fatal:
2015 Mar 15
0
Dovecot 2.1.7 still accepting SSLv3 though disabled?
Thomas Preissler: > ssl_protocols = !SSLv3 !SSLv2 that disable SSLv3 > When I enable verbose_ssl I get this: > 2015-03-15 08:27:39 imap-login: Warning: SSL: where=0x2001, > ret=1: SSLv3 flush data [$CLIENTIP] > ... > Is this right? Is SSLv3 used on this connection? The logging is right, but SSLv3 isn't used. Today it's not uncommon that application /log/
2015 Mar 15
2
Dovecot 2.1.7 still accepting SSLv3 though disabled?
Hello, I came across a strange problem with my Dovecot 2.1.7 installation (updated Debian Wheezy) in regards to SSL/TLS connections. My configuration is as follows: $ dovecot -n | grep ssl service imap-login { ssl = yes ... } ssl_cert = <...... ssl_cipher_list =
2020 Jul 15
2
[PATCH nbdkit v2] curl: Implement header and cookie scripts.
Evolution of this patch series: https://www.redhat.com/archives/libguestfs/2020-July/thread.html#00073 Instead of auth-script, this implements header-script and cookie-script. It can be used for similar purposes but the implementation is somewhat saner. Rich.
2015 Apr 26
2
[patch] TLS Handshake failures can crash imap-login
On 04/26/2015 04:07 PM, Florian Pritz wrote: > Since there are three people involved I kindly ask you to be more > specific as to who should provide which (exact) information. > > Given you ask for it right after quoting my link all I can tell you is > that I provide all the information you ask for (openssl version, crash > message) in the link you quoted. Sorry if I was not
2015 Apr 24
3
[patch] TLS Handshake failures can crash imap-login
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
2015 Apr 27
1
[patch] TLS Handshake failures can crash imap-login
On 04/26/2015 10:51 PM, Hanno B?ck wrote: > On Sun, 26 Apr 2015 21:51:25 +0300 > Teemu Huovila <teemu.huovila at dovecot.fi> wrote: > >> Seems the issue might require a version of libopenssl, that does not >> have support for sslv3 compiled in. I have been made aware, that we >> have a fix for Dovecot in the works. > > No that's not true. I have
2014 Nov 04
2
Samba 4 - disabling SSLv3 to mitigate POODLE effects
Hi all, Am trying to find a way to disable SSLv3 protocol in smb.conf on Samba4. I am using the following: tls enabled = yes tls keyfile = tls/myKey.pem tls certfile = tls/myCert.pem tls cafile = With a self-signed cert. But when I remote connect from another host using: openssl s_client -showcerts -connect samba4-dc:636 -ssl3 I get a successful
2011 Oct 07
1
iplots
Hi guys, I am trying to plot a scatterplot with lines instead of with points using function iplot in library iplots. The best I can come up with is x =(1:100) y = rnorm(100) iplot(x,y,ptDiam=0) ilines(x,y) Do you guys know of any paramter to set the "type" in iplot or iplot.opt? Thanks, Fernando ?lvarez
2015 Apr 25
0
[patch] TLS Handshake failures can crash imap-login
On 24/04/2015 22:17, Hanno B?ck wrote: Hello, > 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
2016 Jun 14
5
Besoin d’aide pour upssched
Bonjour je n?arrive pas ? configurer convenablement NUT pour qu?il m?adresse des SMS en cas de coupure de courant. C?est important pour moi car dans ma maison les coupures sont tr?s fr?quentes. Voici ma configuration : ****************************************************************** 1/ dans /etc/nut/upsmon.conf MONITOR eaton at localhost 1 admin motdepasse master MINSUPPLIES 1 SHUTDOWNCMD