--pipe using tls to exim compiled with gnutls not working
Open
Nobody has claimed this yet.
bug
- Dominant language
- Perl
- Stars
- 1.3k
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Description
This is an old report (2014) which was just brought back to my attention by hschlittermann. It appears to be specific to Exim compiled with gnutls, which I don't think was ever tested. "The same Exim, but compiled with OpenSSL works."
swaks --tls --pipe 'exim -bh <ip>'
LOG: TLS error on connection from (SERVERNAME) [SERVERIP] (gnutls_handshake): A TLS packet with unexpected length was received.
<- 220 TLS go ahead
*** TLS startup failed (connect(): error:00000000:lib(0):func(0):reason(0))
*** STARTTLS attempted but failed
pkg-config --modversion gnutls ---> 2.12.20
pkg-config --modversion openssl ---> 1.0.1e
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing swaks --tls --pipe 'exim -bh <ip>' against Exim compiled with GnuTLS, then compare the same setup compiled with OpenSSL. Trace the --pipe TLS handshake path and verify that the GnuTLS case completes STARTTLS without the unexpected-length error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100