commit - f087c68a99951d12ba91c5f6e1e0e548c5a5d912
commit + 5410d96748bbc93fa9479ddaad0fffc51d816f92
blob - b4a498d456575f5880043a812f1074e2ee7593d7
blob + 02c8bee1387bf679c1fb789e3016ee7f9bcb1e73
--- doc/sample-ngircd.conf.tmpl
+++ doc/sample-ngircd.conf.tmpl
@@ -165,6 +165,9 @@
 	# "PONG" reply.
 	;RequireAuthPing = no
 
+	# Silently drop all incomming CTCP requests.
+	;ScrubCTCP = no
+
 	# SSL Server Key Certificate
 	;SSLCertFile = :ETCDIR:/ssl/server-cert.pem
 
blob - e8efab1f0bf75072d23a410d3f97e4f30a4a9c50
blob + 09fd164dd9fa70381dedf4aa85448cd12eeeec4d
--- man/ngircd.conf.5.tmpl
+++ man/ngircd.conf.5.tmpl
@@ -274,6 +274,16 @@ Default: no.
 \fBRequireAuthPing\fR (boolean)
 Let ngIRCd send an "authentication PING" when a new client connects, and
 register this client only after receiving the corresponding "PONG" reply.
+Default: no.
+.TP
+\fBScrubCTCP\fR (boolean)
+If set to true, ngIRCd will silently drop all CTCP requests sent to it from
+both clients and servers. It will also not forward CTCP requests to any
+other servers. CTCP requests can be used to query user clients about which
+software they are using and which versions said softare is. CTCP can also be
+used to reveal clients IP numbers. ACTION CTCP requests are not blocked,
+this means that /me commands will not be dropped, but please note that
+blocking CTCP will disable file sharing between users!
 Default: no.
 .TP
 \fBSSLCertFile\fR (string)