similar to: R CMD check --as-cran: sslv3 alert handshake failure

Displaying 20 results from an estimated 300 matches similar to: "R CMD check --as-cran: sslv3 alert handshake failure"

2015 Jul 04
0
Support for transparency in metafile export & support for export to Powerpoint
Dear all, Further to my previous message I now made a one-line convencience function to export your currently active graphics window/plot to either Word or Powerpoint in Office-native vector-based DrawingML format using either export2ppt(file="plot.pptx") or export2doc(file="plot.docx") : see
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
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
2011 Feb 04
2
All DomU failing SSLv3 handshake (curl, apt-get, wget, etc.) but OK on Dom0
Hi, First of all I''ve googled this subject a lot (several hours) but right now I''m simply stuck. All my 4 DomU fails SSL handshake: > niklas@stats:~$ curl -vI https://graph.facebook.com > * About to connect() to graph.facebook.com port 443 (#0) > * Trying 69.63.181.58... connected > * Connected to graph.facebook.com (69.63.181.58) port 443 (#0) > * successfully
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
2004 Jul 19
1
Failed to issue the StartTLS instruction: Connect error
Hi, I have two LDAP Servers with similar configurations. The main difference is that one runs Linux Fedora 1 and the other Linux Fedora 2. The Fedora 2 server runs correctly whilst the Fedora 1 LdAP doesn't with the error: Failed to issue the StartTLS instruction: Connect error. Following is an example of error message on Fedora 1. [root@otr etc]# net getlocalsid [2004/07/18 21:20:09, 0]
2005 May 11
3
smbldap_open_connection(623)
Hi, Did this issue get resolved? Can someone tell me how it was resolved and what needs to be done? I am running into the same issue. Thanks, Prakash
2018 Dec 11
3
"no shared cypher", no matter what I try
hello, and some update short version: the error is still there, but I have some more data to share, thanks in advance for further advice first, I am using Mutt 1.10.1 (2018-07-13) as mail client, so it is not an obsolete version. second... at the moment I can send email through postfix on the same server, with the same certificates (almost: I still have to fix some stuff, but is NOT related to
2004 Jun 18
1
configuring samba-LDAP-PDC using IDEALX tools
I am using smbldap-tool from IDEALX on my Fedora Core 1 samba 3.0.5 PDC. I have been following their guide step by step and I am getting the following error message as I try to get SID. I have looked in google group, but I couldn't exactly find anybody who had the same problem as I do. Please help me if you can! [root@pdc smbldap-tools]# net getlocalsid [2004/06/17 10:53:57, 0]
2014 Aug 12
0
Asterisk 11.11 with TCP/TLS SRTP and Grandstream gxp1450 not working
Hey there i'm trying to get an Asterisk 11.11 with encryption working with my Grandstream phones. But i stuck. To avoid NAT problems i'm using IPv6 Just with TCP/TLS it's working fine. Only the SRTP funktion is not working. Asterisk tells me WARNING[6938]: chan_sip.c:3906 __sip_xmit: sip_xmit of 0x7fa10800f5a0 (len 681) to [2a02:1205::...]:37635 returned -2: Success and also SSL
2004 Aug 26
2
smbldap_open_connection(623)
I am running Redhat Linux 9, openldap 2.2.15, Bdb - 4.2.52, openssl - 0.9.7d, smbldap-tools-0.8.5 and samba - 3.0.6. When I try to migrate my users from NT 4 domain to Samba, using the net vampire command, I get the following error: [2004/08/25 14:58:59, 0]Lib/smbldap.c:smbldap_open_connection(623) Failed to issue the StartTLS instruction: Connect error Broken pipe Am I missing
2012 Nov 24
1
Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3
What are the reasons for the above error (apart from clocks out of sync - they aren''t, and different versions of Ruby - they aren''t). -Nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/1ZljqG71MSgJ. To post to this group,
2010 Jan 15
0
CVE-2009-4355 / openssl memory leak in SSLv3 (DoS)
Yesterday most major linux distributions pushed an update to their servers with a patched version of openssl conerning CVE-2009-4355. However, I have unitl now been unable to find anything on the subject (no SA or anything on VuXML) as to how this bug affects FreeBSD and if there's a patch on its way to the upstream ports-tree. Is there anyone who has some information on the subject? --
2015 Jun 03
1
sslv3 alert unexpected message
hello, my webrtc calls ends after ~60seconds with "res_rtp_asterisk.c: DTLS failure occurred on RTP instance '0xb6c02a94' due to reason 'sslv3 alert unexpected message', terminating". any ideas where can be problem? or howto debug this problem? asterisk13.4.0-rc1 + sipml5 latest (chrome,firefox) -- --------------------------------------- Marek Cervenka
2014 Oct 15
0
SSLv3 vunerability and Nautilus
CentOS-6.5 Apache httpd-2.2.15 We have a webdav folder accessible only by https. In conformance with the advisory we removed SSLv3 from the SSLProtocol directive of the Apache server on that webdav host, so that it now looks like this: SSLProtocol +TLSv1 Now I cannot connect to the webdav service from my gnome desktop. When I open the webdav folder I get a window with the following error
2015 Jan 26
0
Apache and SSLv3
> I'm configuring apache with https and I've a question about sslv3 > deactivation. > > Running "openssl ciphers -v" I get a list of cypher suite of openssl like: > > ECDH-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH/RSA Au=ECDH Enc=AESGCM(128) > Mac=AEAD > ......... > SSLProtocol all -SSLv2 -SSLv3 SSLHonorCipherOrder on SSLCompression
2015 Mar 12
0
Java SSLv3 status on CentOS-6.6
On Wed, March 11, 2015 13:46, Grant McChesney wrote: > On Wed, Mar 11, 2015 at 10:03 AM, James B. Byrne > <byrnejb at harte-lyne.ca> > wrote: > >> Can anyone inform me as to whether or not Java on CentOS-6.6 still >> has SSLv3 enabled? And if it does then how is it disabled? >> >> > James: > > Check the java.security file for your JRE. I'm
2015 Apr 17
2
Disable SSLv3 in sendmail in CentOS 5
RedHat released sendmail-8.13.8-10.el5_11.src.rpm which includes sendmail-8.13.8-ssl-opts.patch which adds support for disabling SSLv3 and SSLv2 in sendmail.cf But as far as I can see there is no support in sendmail.mc - I can't see how to compile sendmail.mc to get the required line ServerSSLOptions in sendmail.cf Does anyone know how to do this ? -- Andrew Daviel, TRIUMF, Canada
2015 Apr 17
0
Disable SSLv3 in sendmail in CentOS 5
On Thu, 16 Apr 2015, Andrew Daviel wrote: > RedHat released sendmail-8.13.8-10.el5_11.src.rpm which includes > sendmail-8.13.8-ssl-opts.patch which adds support for disabling > SSLv3 and SSLv2 in sendmail.cf > > But as far as I can see there is no support in sendmail.mc - I can't > see how to compile sendmail.mc to get the required line > ServerSSLOptions in
2014 Oct 15
0
Koji/CBS infra and sslv3/Poodle important notification
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As most of you already know, there is an important SSLv3 vulnerability (CVE-2014-3566 - see https://access.redhat.com/articles/1232123) , known as Poodle. While it's easy to disable SSLv3 in the allowed Protocols at the server level (for example SSLProtocol All -SSLv2 -SSLv3 for apache), some clients are still defaulting to SSLv3, and Koji