Hello everyone,

I hope I have the correct mailing list for my question. Initially I asked this 
question at: 
http://stackoverflow.com/questions/24999580/can-postfix-verify-client-certificate-fingerprint-when-supporting-starttls

According to the Postfix TLS Readme there are 3 ways to configure the 
server-side to support access control:
* permit_tls_clientcerts
* permit_tls_all_clientcerts
* check_ccert_access type:table

But these three options are only configurable for the configuration property:
* smtpd_client_restrictions

This property will trigger the verification at the time the connection is 
established with the client. This is useful when you support SSL (SMTPS or 
SSMTP), but not when you are using StartTLS. A client connecting to SMTPS will 
first start the TLS negotiation and authenticate with the client certificate. 
When using StartTLS, the client is already connected (may even already have 
stated "EHLO stackoverflow.com") and then starts the TLS negotiation.

I actually created a policy daemon and used the "check_ccert_access type:table" 
for "smtpd_client_restrictions". That way I was able to confirm that postfix 
was at CONNECT state, and no client certificate information was available.

The only alternative I have, is to use my policy daemon, and verify the 
authentication at the first "MAIL FROM" (MAIL STATE). At this point I am 
rejecting the sender address, based on the authentication. But I would like to 
reject the client right after the TLS negotiation.

Is this possible? Otherwise, can I request this as a feature? (How? Where?)

So instead of:
openssl s_client -connect localhost:25 -starttls smtp -cert cert.crt -key 
key.pem -ign_eof
----
250 DSN

I would like:
openssl s_client -connect localhost:25 -starttls smtp -cert cert.crt -key 
key.pem -ign_eof
----
535 5.7.8 Error: authentication failed: authentication failure

Regards Atze Zitman
[email protected]

Reply via email to