Displaying 6 results from an estimated 6 matches for "privkey1".
Did you mean:
privkey
2018 Dec 11
3
"no shared cypher", no matter what I try
...eturns "no peer certificate
available", and when
I connect with mutt to dovecot I still get the "no shared cipher"
error. These are the permissions
on the certificate files:
ls -l /etc/letsencrypt/archive/<MYSERVER>/fullchain1.pem
/etc/letsencrypt/archive/<MYSERVER>/privkey1.pem
-r--------. 1 root root 3546 Dec 7 11:59
/etc/letsencrypt/archive/<MYSERVER>/fullchain1.pem
-r--------. 1 root root 1704 Dec 7 11:59
/etc/letsencrypt/archive/<MYSERVER>/privkey1.pem
output of openssl, dovecot -n, its current SSL settings and excerpt of
the log file are all below....
2018 Dec 11
0
"no shared cypher", no matter what I try
...gt; available", and when
> I connect with mutt to dovecot I still get the "no shared cipher"
> error. These are the permissions
> on the certificate files:
>
> ls -l /etc/letsencrypt/archive/<MYSERVER>/fullchain1.pem
> /etc/letsencrypt/archive/<MYSERVER>/privkey1.pem
> -r--------. 1 root root 3546 Dec 7 11:59
> /etc/letsencrypt/archive/<MYSERVER>/fullchain1.pem
> -r--------. 1 root root 1704 Dec 7 11:59
> /etc/letsencrypt/archive/<MYSERVER>/privkey1.pem
>
> output of openssl, dovecot -n, its current SSL settings and excerpt o...
2018 Dec 11
2
"no shared cypher", no matter what I try
...> > I connect with mutt to dovecot I still get the "no shared cipher"
> > error. These are the permissions
> > on the certificate files:
> >
> > ls -l /etc/letsencrypt/archive/<MYSERVER>/fullchain1.pem
> > /etc/letsencrypt/archive/<MYSERVER>/privkey1.pem
> > -r--------. 1 root root 3546 Dec 7 11:59
> > /etc/letsencrypt/archive/<MYSERVER>/fullchain1.pem
> > -r--------. 1 root root 1704 Dec 7 11:59
> > /etc/letsencrypt/archive/<MYSERVER>/privkey1.pem
> >
> > output of openssl, dovecot -n, its curr...
2018 Dec 08
6
"no shared cypher", no matter what I try
Greetings,
I have had to reinstall my email server on another Linux (centos 7.6)
VPS, with a newer version of dovecot, other software and a brand new
letsencrypt certificate just for email withpostfix and dovecot (that
certificate works fine with postfix). Output of dovecot --version and
dovecot -n on the new server is below.
Now, messages ARE delivered in the right IMAP mailboxes, but when I
try
2019 Feb 05
2
Unable to join to a SAMBA4 domain
Hi folks
I'm using samba 4.8.3 in CentOS client and samba 4.9.3 from Van Belle repos
on server
I cannot join to the domain as
net ads join -k -d 1
libnet_Join:
libnet_JoinCtx: struct libnet_JoinCtx
in: struct libnet_JoinCtx
dc_name : NULL
machine_name : 'TINY-FISHWIFE'
domain_name : *
2019 Feb 05
5
Unable to join to a SAMBA4 domain
...full_audit:success = mkdir rmdir read pread write pwrite rename
unlink
full_audit:facility = local5
full_audit:priority = notice
# TLS settings
tls enabled = yes
tls certfile = tls/ldap.example.com/fullchain1.pem
tls keyfile = tls/ldap.example.com/privkey1.pem
tls cafile =
#log auth
log level = 1 auth_audit:3 auth_json_audit:3
[netlogon]
path = /var/lib/samba/sysvol/example.com/scripts
read only = No
[sysvol]
path = /var/lib/samba/sysvol
read only = No
Thanks in advance!
--
--
Sergio Belkin...