Displaying 20 results from an estimated 21 matches for "vtol".
Did you mean:
vol
2018 Aug 06
2
2.3.2.1 - relay to lmtps from other lan host
Hi,
looked into the [ dovecot wiki ] but a search for [ lmtps ] came up
empty and thus hoping to get some assistance here.
I am trying to relay with [ msmtp ] via [ lmtps ] from a lan host other
than [ dovecot ] is running on.
[ dovecot config ]
> service lmtp {
> ? unix_listener lmtp {
> ??? #mode = 0666
> ? }
[ ss -wxl | grep lmtp ]
> u_strLISTEN 0????? 100???
2018 Jul 30
0
2.3.2.1 - EC keys suppport?
> On 29 July 2018 at 23:39 ????? <vtol at gmx.net> wrote:
>
>
>
> >> facing [ no shared cipher ] error with EC private keys.
> > the client connecting to your instance has to support ecdsa
> >
> >
>
> It does - Thunderbird 60.0b10 (64-bit)
>
> [ security.ssl3.ecdhe_ecdsa_aes_256_gc...
2018 Jul 30
2
2.3.2.1 - EC keys suppport?
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 30 July 2018 at 21:00 ѽ҉ᶬḳ℠ <
<a href="mailto:vtol@gmx.net">vtol@gmx.net</a>> wrote:
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<blockquote type="cite">
<div>
I did some local testing and...
2018 Jul 30
0
2.3.2.1 - EC keys suppport?
> On 30 July 2018 at 20:01 ????? <vtol at gmx.net> wrote:
>
>
>
> >>>> facing [ no shared cipher ] error with EC private keys.
> >>> the client connecting to your instance has to support ecdsa
> >>>
> >>>
> >> It does - Thunderbird 60.0b10 (64-bit)
> >>...
2018 Aug 06
2
AW: 2.3.2.1 - relay to lmtps from other lan host
You have lmtp as unix socket configured but want to access from remote via tcp socket? I think you need inet_listener instead of unix_ listener
----- Originale Nachricht -----
Von: "?????" <vtol at gmx.net>
Gesendet: 06.08.18 - 20:14
An: dovecot <dovecot at dovecot.org>
Betreff: 2.3.2.1 - relay to lmtps from other lan host
> Hi,
>
> looked into the [ dovecot wiki ] but a search for [ lmtps ] came up
> empty and thus hoping to get some assistance here.
>
> I am...
2018 Jul 30
3
2.3.2.1 - EC keys suppport?
> On 30 July 2018 at 20:37 ????? <vtol at gmx.net> wrote:
>
>
>
> >>>>>>> facing [ no shared cipher ] error with EC private keys.
> >>>>>> the client connecting to your instance has to support ecdsa
> >>>>>>
> >>>>>>
> >>>&g...
2018 Jul 29
4
2.3.2.1 - EC keys suppport?
>> facing [ no shared cipher ] error with EC private keys.
> the client connecting to your instance has to support ecdsa
>
>
It does - Thunderbird 60.0b10 (64-bit)
[ security.ssl3.ecdhe_ecdsa_aes_256_gcm_sha384;true ]
It seems there is a difference between the private key (rsa vs. ecc ->
SSL_CTX?) used for the certificate signing request and the signed
certificate.
The csr
2018 Jul 30
2
2.3.2.1 - EC keys suppport?
>>>> facing [ no shared cipher ] error with EC private keys.
>>> the client connecting to your instance has to support ecdsa
>>>
>>>
>> It does - Thunderbird 60.0b10 (64-bit)
>>
>> [ security.ssl3.ecdhe_ecdsa_aes_256_gcm_sha384;true ]
>>
>> It seems there is a difference between the private key (rsa vs. ecc ->
>>
2018 Jul 30
2
2.3.2.1 - EC keys suppport?
>>>>>> facing [ no shared cipher ] error with EC private keys.
>>>>> the client connecting to your instance has to support ecdsa
>>>>>
>>>>>
>>>> It does - Thunderbird 60.0b10 (64-bit)
>>>>
>>>> [ security.ssl3.ecdhe_ecdsa_aes_256_gcm_sha384;true ]
>>>>
>>>> It seems there is
2018 Jul 29
2
2.3.2.1 - EC keys suppport?
Hi,
facing [ no shared cipher ] error with EC private keys. This happens
when the private key is generated with [ openssl ecparam -name
brainpoolP512t1 -genkey ] with OpenSSL 1.1.0hh on the same machine
Dovecot is running on.
Tried some variations of [ ssl_cipher_list ] but to no avail - the [ no
shared cipher ] error persists.
Once the key is generated with [ openssl genpkey -algorithm RSA ]
2018 Jul 30
0
2.3.2.1 - EC keys suppport?
>>
>>> I did some local testing and it seems that you are using a curve
>>> that is not acceptable for openssl as a server key.
>>> I tested with openssl s_server -cert ec-cert.pem -key ec-key.pem
>>> -port 5555
>>> using cert generated with brainpool. Everything works if I use
>>> prime256v1 or secp521r1. This is a limitation in OpenSSL
2018 Jul 30
0
2.3.2.1 - ssl_alt_key revealed with dovecot -n
Seems like a minor cosmetic bug with [ dovecot -n ]
ssl_alt_key = </etc/pki/private/some.key.pem
ssl_key =? # hidden, use -P to show it
2018 Jul 31
0
2.3.2.1 - EC keys suppport?
> Perhaps for whose interested - IETF RFC 7027 specifies for TLS use:
>
> [ brainpoolP256r1 | brainpoolP384r1 | brainpoolP512r1 ]
>
> And thus t1 would not work anyway. However, having tested r1 the result
> was just the same.
>
> A tcpdump during the openssl test [ s_server | s_client ] then revealed
> (TLSv1.2 Record Layer: Handshake Protocol: Client Hello) :
>
>
2018 Jul 31
0
2.3.2.1 - EC keys suppport?
>
>>> Perhaps for whose interested - IETF RFC 7027 specifies for TLS use:
>>>
>>> [ brainpoolP256r1 | brainpoolP384r1 | brainpoolP512r1 ]
>>>
>>> And thus t1 would not work anyway. However, having tested r1 the result
>>> was just the same.
>>>
>>> A tcpdump during the openssl test [ s_server | s_client ] then revealed
2018 Jul 31
0
2.3.2.1 - EC keys suppport?
> Yeah, it needs to be recompiled to fix.
>
Sure, no worries.? Thanks for the quick turnaround on the patch.
Downstream is notified and pending migration into their package.
Meanwhile ssl_alt_key/certs does the trick. I am grateful that such
option is even provisioned or else I would a be in rather bad spot with
the CA. Other apps are rather ignorant on that matter.
2018 Aug 06
0
AW: 2.3.2.1 - relay to lmtps from other lan host
Right, now I got then
> service lmtp {
> ? unix_listener lmtp {
> ??? #mode = 0666
> ? }
>
> ? inet_listener lmtp {
> ???? address = 172.24.109.6
> ??? port = 24
> ? }
> }
and [ msmtp ] is connecting indeed. Does TLS/STARTTLS need to be added
to [ inet_listener lmtp ] in order to facilitate [ lmptps ]? If so what
is the syntax?
Right now this error comes up:
>
2004 Dec 03
0
ZAPHFC, Asterisk does not load with signalling = bri_net_ptmp
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
I am trying to get zaphfc running in nt mode with asterisk.
2018 Jul 30
2
2.3.2.1 - EC keys suppport?
>>>> I did some local testing and it seems that you are using a curve
>>>> that is not acceptable for openssl as a server key.
>>>> I tested with openssl s_server -cert ec-cert.pem -key ec-key.pem
>>>> -port 5555
>>>> using cert generated with brainpool. Everything works if I use
>>>> prime256v1 or secp521r1. This is a
2018 Jul 30
2
dovecot 2.3.x, ECC and wildcard certificates, any issues
That is one of the reasons I do not bother since long with public CAs
but rather deploy my own, including own OSCP responder.
Which has of course has some drawbacks like redundancy, resilience,
bandwidth provision, geographical spread, implementing CA security
standards and CA trust in clients. Latter though could be easily
overcome if browser and email clients were to support DNSSEC/DANE
2018 Jul 30
0
2.3.2.1 - EC keys suppport?
> I did some local testing and it seems that you are using a curve that is not acceptable for openssl as a server key.
>
> I tested with openssl s_server -cert ec-cert.pem -key ec-key.pem -port 5555
>
> using cert generated with brainpool. Everything works if I use prime256v1 or secp521r1. This is a limitation in OpenSSL and not something we can really do anything about.
>
>