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
Our current parsing does not handle this. After stripping away the multipart prefix we end up with Message.content_type_parameter = b"protocol=\"application/HTTP-Kerberos-session-encrypted\";boundary=\"Encrypted Boundary\",". When trying to handle this in
we do not anticipate to see something before boundary so we match nothing; this cause a protocol violation when dereferencing boundary which has no value,
If HTTP traffic contains Kerberos encrypted traffic it would have a header like
Our current parsing does not handle this. After stripping away the multipart prefix we end up with
Message.content_type_parameter = b"protocol=\"application/HTTP-Kerberos-session-encrypted\";boundary=\"Encrypted Boundary\","
. When trying to handle this inspicy-http/analyzer/analyzer.spicy
Lines 96 to 104 in 48ce0b7
boundary
so we match nothing; this cause a protocol violation when dereferencingboundary
which has no value,spicy-http/analyzer/analyzer.spicy
Line 103 in 48ce0b7
Zeek's builtin HTTP analyzer does not handle this either and instead reports a weird
The text was updated successfully, but these errors were encountered: