Re: About TLS variables
Then the information variables can be pass to post-login script? Aki Tuomi () 在 2021年3月4日星期四 下午02:58:44 [GMT+8] 寫道: This information is not passed currently to auth process, so no, it's not currently possible. Aki > On 04/03/2021 08:34 Henry wrote: > > > Hello, > > I found the Variable %c only has TLS, Can it be using "TLSv1, > TLSv1.1,TLSv1.2,TLSv1.3" instead of only TLS like as dovecot logging, this is > really a most meaningful , thanks > > > > Variable%c > Long namesecured > Description“TLS” with established SSL/TLS connections, “TLS handshaking”, or > “TLS [handshaking]: error text” if disconnecting due to TLS error. “secured” > with localhost connections. Otherwise empty. > > > > > >
Re: About TLS variables
This information is not passed currently to auth process, so no, it's not currently possible. Aki > On 04/03/2021 08:34 Henry wrote: > > > Hello, > > I found the Variable %c only has TLS, Can it be using "TLSv1, > TLSv1.1,TLSv1.2,TLSv1.3" instead of only TLS like as dovecot logging, this is > really a most meaningful , thanks > > > > Variable%c > Long namesecured > Description“TLS” with established SSL/TLS connections, “TLS handshaking”, or > “TLS [handshaking]: error text” if disconnecting due to TLS error. “secured” > with localhost connections. Otherwise empty. > > > > > >
About TLS variables
Hello, I found the Variable %c only has TLS, Can it be using "TLSv1, TLSv1.1, TLSv1.2, TLSv1.3" instead of only TLS like as dovecot logging, this is really a most meaningful , thanks Variable %cLong name securedDescription “TLS” with established SSL/TLS connections, “TLS handshaking”, or “TLS [handshaking]: error text” if disconnecting due to TLS error. “secured” with localhost connections. Otherwise empty.