similar to: gplpv cert

I have installed the 210 gplpv (debug), when I try to update them with current gplpv I get a BSOD even so when I try to uninstall them. Now I have made a bootentry that specifies NOGPLPV, what gives me a bootable system after such a crash, I found (uninstalling the leftover driver packages after getting bsod during uninstall of the main package) that uninstalling the net driver leads to bsod. Now

for testing a new ssl cert. it works ok for browsers, but > openssl s_client -crlf -connect ms1.trailsandtribulations.net:443 => verify error:num=19:self signed certificate in certificate chain is this ssl cert - as it's constructed - is ok for mail clients? (realize needs to be on mail port etc - right now talking about the cert itself.) have had problems with thunderbird, and

On Fri, June 17, 2016 11:06, Walter H. wrote: > On 17.06.2016 16:46, James B. Byrne wrote: >> On Thu, June 16, 2016 13:53, Walter H. wrote: >>> On 15.06.2016 16:17, Warren Young wrote: >>>> but it also affects the other public CAs: you can???t get a >>>> publicly-trusted cert for a machine without a publicly-recognized >>>> and -visible

Greetings all, I have verified a bug that has long been attributed to lack of knowledge on the part of the user. Dovecot rejects StartSSL client certificates due to reject StartSSL root CA when doing client verification even though the appropriately constructed ca-bundle.pem has been created and applied vi ssl_ca = </etc/dovecot/ca-bundle.pem. openssl verify -CAfile ca-bundle.pem

Hi there! What am I doing wrong? I created a ssh-certificate id_user_rsa-cert.pub with this dump: id_user_rsa-cert.pub: root at host # ssh-keygen -Lf id_user_rsa-cert.pub ??????? Type: ssh-rsa-cert-v01 at openssh.com user certificate ??????? Public key: RSA-CERT SHA256:kPitwgxblaUH4viBoFoozSPq9Pblubbedk ??????? Signing CA: ED25519 SHA256:8p2foobarQo3Tfcblubb5+I5cboeckvpnktiHdUs ??????? Key ID:

On 2015/2/16 16:28, Jochen Bern wrote: > On 02/16/2015 04:23 PM, Reindl Harald wrote: >>> "The CA file should contain the certificate(s) followed by the >>> matching CRL(s). Note that the CRLs are required to exist. For a >>> multi-level CA place the certificates in this order: >>> >>> Issuing CA cert >>> Issuing CA CRL

Sure, and thanks for trying to help! These are the two correct answers when SNI is included. The certificates are fully chained. Both certificates carry the same subject mail.cs.sbg.ac.at but differ in Subject Alternative Name (SAN). X509v3 Subject Alternative Name:? ? DNS:mail.cs.sbg.ac.at, DNS:smtp.cs.sbg.ac.at, DNS:imap.cs.sbg.ac.at, DNS:pop.cs.sbg.ac.at X509v3 Subject Alternative Name:? ?

Hi, I'm trying to get apache, sendmail , and dovecot to use SSL certs signed by my own CA. I've got the apache certs working fine. However, dovecot ( I haven't even tried sendmail yet) doesn't seem to accept any of the certificates that I create for it. There is a script that comes with dovecot that creates self-signed certificates for you but, I need certificates signed by my own

Hi Daminan! Hmmm... thought about a little... when i use -vvv with ssh-keygen -Qf i see "debug1:..." So i think, debug is compiled in. ssh-keygen --help gives me ssh-keygen -k -f krl_file [-u] [-s ca_public] [-z version_number] file ... so... option -z is not the serial of the certificate, it is the version-number of the KRL-File... My openssh-Verision from Debian is

El lun, 28-08-2017 a las 20:23 +0000, Speagle, Andy escribió: > > > > > > > Hi Folks, > > > > > > > > > > > > > > I’m having a problem getting a the SSL cert file > > > > > > > formatted > > > > > > > just like icecast wants… I’m running 2.4.2 … and it > > > > > > >

El lun, 28-08-2017 a las 21:37 +0000, Speagle, Andy escribió: > > > > > > > > > Hi Folks, > > > > > > > > > > > > > > > > > > I’m having a problem getting a the SSL cert file > > > > > > > > > formatted > > > > > > > > > just like icecast wants… I’m running 2.4.2

I''m running a two headed puppetmaster and have disabled crl''s. Let''s call them the primary and the secondary. The primary and secondary both use the primary as their master. The secondary only is used when the primary isn''t responding (I wrap the puppetd call in cron with a short shell script) I''m managing these ca files on the masters, pushing

El lun, 28-08-2017 a las 21:56 +0000, Speagle, Andy escribió: > > > > > > > > > > > Hi Folks, > > > > > > > > > > > > > > > > > > > > > > I’m having a problem getting a the SSL cert file > > > > > > > > > > > formatted just like icecast wants… I’m running > >

https://bugzilla.redhat.com/show_bug.cgi?id=466681 just to be sure that some one in xvm-team notices that before any bits from xvm-gate are putback ;) Florian

Can you provide some details on what those openssl commands returned? Aki On 20.07.2018 12:14, Martin Johannes Dauser wrote: > Hi, > > I recognised some funny behaviour on my server. IMAP clients which > won't send an Server Name Indication (SNI) sometimes get the wrong > certificate. I would expect that those clients always get the default > certificate (of my new

I am building a mail server on Centos 6.3 and working with OpenSSL to create a self-signed certificate for mail use. Along the line of learning the 'best' options to use for OpenSSL and dealing with the default SSL virtual host for Apache, I discovered that the localhost cert created (I believe) during firstboot has the X509v3 extensions set as a CA cert (eg basicConstraint CA:TRUE).

"Speagle, Andy" <andy.speagle at wichita.edu>Hi Andy, El lun, 28-08-2017 a las 13:46 +0000, Speagle, Andy escribió: > > El vie, 25-08-2017 a las 16:49 +0000, Speagle, Andy escribió: > > > Hi Folks, > > > > > > I’m having a problem getting a the SSL cert file formatted just > > > like > > > icecast wants… I’m running 2.4.2 … and it

Hi Andy, El lun, 28-08-2017 a las 19:05 +0000, Speagle, Andy escribió: > > > > > Hi Folks, > > > > > > > > > > I’m having a problem getting a the SSL cert file formatted > > > > > just > > > > > like icecast wants… I’m running 2.4.2 … and it doesn’t seem > > > > > to > > > > > want to use my

Hey list, I was having a similar SSL/openLDAP problem to this last week. I had a chance to look at this again today and it still appears to not be working. I called godaddy and had the last cert cancelled and reissued as I had mis-typed the name of the CN on the last one. I am trying to setup a Godaddy turbo SSL certificate with an openLDAP 2.4 server under FreeBSD 8.1. The clients are mainly

> > > > > > > > Hi Folks, > > > > > > > > > > > > > > > > I’m having a problem getting a the SSL cert file formatted > > > > > > > > just like icecast wants… I’m running 2.4.2 … and it > > > > > > > > doesn’t seem to want to use my combined key + cert chain > > > >