You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed an inconsistency among the smtp, imap, pop3 and ftp modules: If explicit tls is selected, the smtp, imap and pop3 modules will not set .data.PROTO.status to "success" if the explicit TLS handshake fails. But the ftp module will happily do so. You have to filter for key_material or server_finished in the tls handshake log to get the actually successful connections. Just something odd I noticed, and wanted to let you know in case you want to keep it consistent (which I would suggest). This is with version 0.1.1, which I realize is quite old by now, but I am in the middle of something and can't update right now, sorry.
Thanks!
The text was updated successfully, but these errors were encountered:
There are other inconsistencies as well: For example, the ftp module uses application-error for TLS related failures that other modules put into unknown-error.
Hi @lambdafu, thanks for reporting this! For the status flag, it seems we fixed the issue earlier in #314. I know it has been quite a while since this was brought up, but could you verify if the current version sets status to a non-success value as expected?
For error type, I have a fix ready but we might need to discuss if we want to continue to use unknown or unifies everything to use a specific error type for TLS. I'll get back on this soon.
I noticed an inconsistency among the smtp, imap, pop3 and ftp modules: If explicit tls is selected, the smtp, imap and pop3 modules will not set .data.PROTO.status to "success" if the explicit TLS handshake fails. But the ftp module will happily do so. You have to filter for key_material or server_finished in the tls handshake log to get the actually successful connections. Just something odd I noticed, and wanted to let you know in case you want to keep it consistent (which I would suggest). This is with version 0.1.1, which I realize is quite old by now, but I am in the middle of something and can't update right now, sorry.
Thanks!
The text was updated successfully, but these errors were encountered: