Fix: Silence SOCKET_DLLLOADER log flood and tighten device-port logging
SOCKET_DLLLOADER (210) is the shellcode / memory-DLL loader asking the server for the full DLL payload before it can load the client. The MFC master console serves it via SendServerDll; the Go web device port has no payload to hand out, so every memory-DLL client startup/reconnect fell into the default dispatch branch and logged "Unhandled command 210", flooding the log. Add a protocol constant and drop the command silently. While auditing the device-port logging surface: - Downgrade wrapTLS's per-connection hex-dump lines and the screen-spy "[timing]" cold-start line from Info to Debug (they fire once per TCP connection / screen view and are diagnostics, not operational events). - Distinguish a sub-connection hijack attempt from a plain orphan: when a screen/terminal sub-conn claims a MasterID from a source IP other than the device's login conn, log a dedicated Warn instead of mislabeling it as "orphan ... unknown device". Co-Authored-By: deepseek-v4-pro
This commit is contained in:
1 parent
614b03994c
commit
a447452521
4 files changed
+29
-10
No files matched your search
@@ -105,9 +105,9 @@ func (s *Server) wrapTLS(conn net.Conn) net.Conn {
|
||||
|
||||
bc := &bufferedConn{Conn: conn, r: br}
|
||||
if isTLSClientHello(hdr) {
|
||||
s.logger.Info("wrapTLS: TLS peer %s first6=%x", conn.RemoteAddr(), hdr)
|
||||
s.logger.Debug("wrapTLS: TLS peer %s first6=%x", conn.RemoteAddr(), hdr)
|
||||
return tls.Server(bc, s.tlsCfg)
|
||||
}
|
||||
s.logger.Info("wrapTLS: plaintext peer %s first6=%x", conn.RemoteAddr(), hdr)
|
||||
s.logger.Debug("wrapTLS: plaintext peer %s first6=%x", conn.RemoteAddr(), hdr)
|
||||
return bc
|
||||
}
|
||||
Reference in new issue
Block a user