similar to: EVP_PKEY_get1_EC_KEY:expecting a ec key

Displaying 20 results from an estimated 400 matches similar to: "EVP_PKEY_get1_EC_KEY:expecting a ec key"

2015 Dec 08
2
EVP_PKEY_get1_EC_KEY:expecting a ec key
Hi Teemu, > Could you post your doveconf -n output? # 2.2.20.rc1 (ed41702f14c2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.10.rc1 # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.9 auth_mechanisms = plain login log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_location =
2016 Apr 13
2
Warning: Global setting won't change the setting inside an earlier filter
Hi, I'm using the Dovecot Prebuilt Binary: deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main I configured multiple SSL certificates with client TLS SNI (see http://wiki2.dovecot.org/SSL/DovecotConfiguration). Since my last update I get some warnings: doveconf: Warning: /etc/dovecot/conf.d/10-ssl.conf line 12: Global setting ssl_cert won't change the setting inside an
2015 Jun 13
2
Testin new installation
On Sat, 13 Jun 2015 21:57:06 +0200, you wrote: >On Sat, Jun 13, 2015 at 03:41:26PM -0400, Steve Matzura wrote: >> >> > > Trying ::1... # this is certainly suspect >> >> > > Escape character is '^['. >> >> > > Connection closed by foreign host. > >This means the daemon is listening but errors out before able to process.
2015 Jun 14
4
Testin new installation
The public cert part is good, but the private one begins with "Begin private key", not "RSA key." On Sun, 14 Jun 2015 15:54:23 +0200, you wrote: >Am 13.06.2015 um 22:11 schrieb Steve Matzura: >> On Sat, 13 Jun 2015 21:57:06 +0200, you wrote: >> >>> On Sat, Jun 13, 2015 at 03:41:26PM -0400, Steve Matzura wrote: >>>>>>>> Trying
2015 Jun 14
0
Testin new installation
Am 13.06.2015 um 22:11 schrieb Steve Matzura: > On Sat, 13 Jun 2015 21:57:06 +0200, you wrote: > >> On Sat, Jun 13, 2015 at 03:41:26PM -0400, Steve Matzura wrote: >>>>>>> Trying ::1... # this is certainly suspect >>>>>>> Escape character is '^['. >>>>>>> Connection closed by foreign host. >> >> This
2015 Jun 14
0
Testin new installation
I think I saw mention of "notepad" previously. If this is the case there may be some "dos" formatting that is messing things up. On Jun 14, 2015, at 12:10 PM, Steve Matzura wrote: > The public cert part is good, but the private one begins with "Begin > private key", not "RSA key." > > On Sun, 14 Jun 2015 15:54:23 +0200, you wrote: >
2015 Jun 13
2
Testin new installation
On Sat, 13 Jun 2015 20:41:01 +0200, you wrote: >Am Samstag, den 13.06.2015, 13:40 -0400 schrieb Steve Matzura: >> On Sat, 13 Jun 2015 14:16:30 +0200, you wrote: >> >> > Am Samstag, den 13.06.2015, 08:00 -0400 schrieb Steve Matzura: >> > > >> > > All of the above specified settings are correct. Yet, when I >> > > telnet >> >
2002 Apr 25
3
ext3 with 2.4.18, back to 2.2.20 ?
Hi, I installed a 2.4.18 kernel, with ext3 support and make a tune2fs -j /dev/sdxxx with all partitions, now I want to run a 2.2.20 kernel, I want to know if I can use the patch for 2.2.20 series (0.0.7a) without problems with my new ext3 partitions, or I must mount it as ext2 from 2.2.20, greetings and reply to admin@cideweb.com, I'm not subscribed to the list.
2001 Nov 13
4
EXT3 with 2.2.20 - Is it stable enough for a production server th at is used 24X7?
Hello All, I have a production server that is running 2.2.20. This server *has* to be up 24X7 - what I'm wondering is: 1) Is ext3 on 2.2.20 rock stable? Or, would you recommend that I just stay with ext2? 2) I have looked far and wide for a the ext3 patch for 2.2.20 - where can I find it? 3) Were are the e2fsprogs that are appropriate to run with the 2.2.X kernel series? Thanks,
2015 Dec 07
7
v2.2.20 released
http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login:
2015 Dec 07
7
v2.2.20 released
http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login:
2015 Dec 03
8
v2.2.20 release candidate released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz.sig v2.2.20 probably will be released tomorrow or maybe during weekend. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login: Added
2015 Dec 03
8
v2.2.20 release candidate released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz.sig v2.2.20 probably will be released tomorrow or maybe during weekend. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login: Added
2015 Dec 02
1
[patch] Fix for bug in TLS/SSL for LMTP with chained certificates
Hi, In case of tl;dr: I fixed a bug in TLS support for LMTP which caused chained certificates not to work, and another one which caused certificate read errors to be ignored; the patches are attached to this email. While testing LMTP with TLS and certificate verification by Postfix I discovered that certificate chains are not exchanged properly when using LMTP, even though everything works fine
2005 Mar 23
4
Samba-LDAP TLS problems with inofficial Debian OpenLDAP 2.2 packages
Dear Torsten, dear samba list reader Three days ago I switched our domain from a NT 4 domaincontroller to Samba-OpenLDAP, controlled by a Debian Sarge system. I installed the following inofficial Debian OpenLDAP 2.2 packages (I know these are not supported, but TLS with OpenSSL is essential to us...): Package: slapd Version: 2.2.20-1.hrz.1 Package: libldap2.2 Version: 2.2.20-1.hrz.1
2015 Dec 08
3
v2.2.20 released
On Tuesday 08 of December 2015, Gerhard Wiesinger wrote: > On 07.12.2015 20:13, Timo Sirainen wrote: > > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz > > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig > > > > This could be (one of) the last v2.2.x release. We're starting v2.3 > > development soon. > > Great! > > What's on
2016 Apr 21
2
UTF-8 encoded folders on filesystem
Hi, > mail_location = ...:UTF-8 UTF-8 or UTF8? See http://dovecot.org/list/dovecot-cvs/2011-September/019148.html Documentation doesn't mention this setting... http://wiki.dovecot.org/MailLocation Regards Oliver
2001 Nov 06
1
ext3 0.0.7a OK for linux 2.2.20?
Hello, Now that kernel 2.2.20 is out with security fixes, I'd be interested in using it with ext3. The latest patch for 2.2.19, 0.0.7a, applies with some offset (both with and without kdb), and even compiles (without kdb), but I scarcely know what I am doing so haven't tried it yet. Could people in the know enlighten me on that point? I guess there is little chance for another ext3
2002 May 03
1
ingress in 2.2.20
Hello , I am trying to install an ingress qdisc on a slackware 7 , 2.2.20 box . I have installed iproute2-2.4.7-now-ss010824.tar.gz . I `ve built all the QOS stuff in my kernel . Playing with cbq sfq etc works ok . However when i try to setup ingress i get the infamous RNETLINK message tc qdisc add dev eth0 handle ffff: ingress RTNETLINK answers: No such file or directory Something weird ,
2015 Dec 29
2
LMTP crashes on Debian with dovecot backports from rename-it.nl
Hello dovecot-users, we're running Debian 7.9 with dovecot from Stephan Bosch's repository: deb http://xi.rename-it.nl/debian/ oldstable-auto/dovecot-2.2 main Starting with dovecot 2.2.20-1 build 28, we suddenly discovered that some mails (to be locally delivered) "got stuck". dovecot's log revealed messages like the following one: Dec 29 09:56:50 mailhost dovecot: