similar to: Adding CA/Root SSL / TLS Certificate, HTTPS

On Thursday 29 August 2019 16:47:11 Alexander Dalloz wrote: > rpm -Vv nss [root at stan2 ~]# rpm -Vv nss ......... /etc/pki/nss-legacy ......... c /etc/pki/nss-legacy/nss-rhel7.config ......... /etc/pki/nssdb ......... c /etc/pki/nssdb/cert8.db ......... c /etc/pki/nssdb/cert9.db ......... c /etc/pki/nssdb/key3.db ......... c /etc/pki/nssdb/key4.db ......... c

Am 2019-08-29 18:26, schrieb Gary Stainburn: > On Thursday 29 August 2019 16:47:11 Alexander Dalloz wrote: >> rpm -Vv nss > > [root at stan2 ~]# rpm -Vv nss > ......... /etc/pki/nss-legacy > ......... c /etc/pki/nss-legacy/nss-rhel7.config > ......... /etc/pki/nssdb > ......... c /etc/pki/nssdb/cert8.db > ......... c /etc/pki/nssdb/cert9.db > ......... c

Hi Rich, I'm not sure how far this helps as it mostly says 'No space left on device', but here's the output of the command you asked me to run: ➜ tmp /usr/bin/supermin --build -v -v -v --copy-kernel -f ext2 --host-cpu x86_64 /usr/lib64/guestfs/supermin.d -o /tmp/appliance.d supermin: version: 5.1.9 supermin: rpm: detected RPM version 4.11 supermin: package handler: fedora/rpm

Hi, I'm trying to manually create a rhel7 image using the qemu-img and virt-install commands. I'm re-testing a procedure I previously wrote with the new grub commands that a customer suggested we add in. This procedure is available at: http://file.bne.redhat.com/dnavale/docs/review/RH-guides/AG-020715/#sect-create-images As in the procedure, I'm able to run all steps successfully

Dovecot v2.2.18 OS: FreeBSD 10.1/amd64 Dovecot in proxy mode ignores the root certificate store and can't verify the backend's SSL certificate. I've pointed ssl_client_ca_file to my root certificate store, but I suspect ssl_client_ca_file is only used in imapc context. It seems to be ignored in proxy context. doveconf -n ssl_client_ca_file: ssl_client_ca_file =

The Asterisk Development Team has announced the release of Certified Asterisk 13.1-cert8. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/certified-asterisk The release of Certified Asterisk 13.1-cert8 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following are the

The Asterisk Development Team has announced security releases for Certified Asterisk 1.8.28 and 11.6 and Asterisk 1.8, 11, 12, and 13. The available security releases are released as versions 1.8.28-cert3, 11.6-cert8, 1.8.32.1, 11.14.1, 12.7.1, and 13.0.1. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/releases The release of these

The Asterisk Development Team has announced security releases for Certified Asterisk 1.8.28 and 11.6 and Asterisk 1.8, 11, 12, and 13. The available security releases are released as versions 1.8.28-cert3, 11.6-cert8, 1.8.32.1, 11.14.1, 12.7.1, and 13.0.1. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/releases The release of these

Am 2019-08-29 17:36, schrieb Gary Stainburn: > On Thursday 29 August 2019 16:20:00 Alexander Dalloz wrote: >> Hi, >> >> yum uses libcurl behind the scenes and thus NSS and not OpenSSL. >> >> Do you get something indicative when running: >> >> URLGRABBER_DEBUG=1 yum --disablerepo=\* --enablerepo=webtatic >> check-update >> >>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 27 Jul 2015, Piotr Rotter wrote: > I tryed to eneble TLS connection from postfix to dovecot lmtp. Unfortunely I > have problem with certificate, postfix shows, post the output of doveconf -n > > 2015-07-27T12:51:15.025333+02:00 k30 postfix/lmtp[4572]: Untrusted TLS > connection established to

The Asterisk Development Team has announced security releases for Certified Asterisk 13.13 and Asterisk 13, 14 and 15. The available security releases are released as versions 13.13-cert8, 13.18.3, 14.7.3 and 15.1.3. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/releases The release of these versions resolves the following security

> -----Original Message----- > From: m.roth at 5-cent.us [mailto:m.roth at 5-cent.us] > Sent: Friday, July 22, 2016 4:15 PM > To: CentOS mailing list > Subject: Re: [CentOS] CentOS 6.7->6.8, ssh-add issue, followup, more info > > m.roth at 5-cent.us wrote: > > Folks, > > > > I am perplexed. I updated my workstation at work Wed before I left, > >

Hello, I tryed to eneble TLS connection from postfix to dovecot lmtp. Unfortunely I have problem with certificate, postfix shows, 2015-07-27T12:51:15.025333+02:00 k30 postfix/lmtp[4572]: Untrusted TLS connection established to 192.168.67.30[192.168.67.30]:24: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) I checked certs by openssl s_client: #openssl s_client -connect

I'm having difficulty with the doveadm who command on a multi-instance setup of dovecot. When I run the who command on the non-standard instance with the -m flag (to see their mail location), this happens: [root at wardentest3 dovecot]# doveadm -i mailtest user -m warden doveadm(root): Error: user warden: Initialization failed: Namespace 'INBOX.': Ambiguous mail location setting,

We are using now dovecot 2.0.21 with open-ldap, but this situations has already taken a quite long time. When user changes the password, we have to reload dovecot every time, otherwise the change is ignored and dovecot sees only the old password. Any ideas where the problem might exist? Conf: # 2.0.21: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-308.24.1.el5 i686 CentOS release 5.9 (Final)

Hi I have renew my geotrust certificate using sha2, and I have problem with Dovecot 2.0.9 and redhat 6.7. The same certificate is working in Apache. The error is dovecot: imap-login: Fatal: Can't load ssl_cert: There is no valid PEM certificate. and the configuration file is ssl_cert=</etc/pki/dovecot/certs/2015/new.2015.pem ssl_key =</etc/pki/dovecot/private/new.2015.key ssl_ca =

Hello All, I'm having issues joining some Ubuntu servers to an Active Directory domain with trusts. All my machines are running samba and winbind. I have a two domains, we'll call them CORPORATE and CUSTOMER. CUSTOMER has a one way trust with CORPORATE, such that any resources CUSTOMER can access, CORPORATE can as well, but not vice-versa. On all of my CORPORATE machines, users are

The Asterisk Development Team has announced security releases for Certified Asterisk 13.13 and Asterisk 13, 14 and 15. The available security releases are released as versions 13.13-cert8, 13.18.3, 14.7.3 and 15.1.3. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/releases The release of these versions resolves the following security

We have a freeradius server using LDAP authentication against openldap. We have had freeradius-3.0.4-6 on CentOS 7 successfully communicating with openldap-servers-2.3.43 on CentOS 5. We need some features in freeradius-3.0.12. When I build that on CentOS 6, it initially works, but then develops TLS errors. We can search and authenticate against the LDAP server with Apache, and with

On RHEL 6.2 + dovecot 2.1.5 with the stats and fts (squat) plugins enabled and each user having their own uid on the system I get the following error in the logs when the indexer-worker process indexes some messages: Apr 25 09:56:19 wardentest3 dovecot: imap-login: Login: user=warden, method=PLAIN, rip=137.238.60.164, lip=137.238.2.240, lport=1993, mpid=19464, encryption=TLS Apr 25 09:56:26