mirror of
https://github.com/nmap/nmap.git
synced 2025-12-06 12:41:29 +00:00
UTF-8–aware escaping in XML todo.
This commit is contained in:
@@ -66,6 +66,16 @@ o NSE digest auth should use the more robust parsing from
|
|||||||
http.parse_www_authenticate as described at
|
http.parse_www_authenticate as described at
|
||||||
http://seclists.org/nmap-dev/2012/q3/868
|
http://seclists.org/nmap-dev/2012/q3/868
|
||||||
|
|
||||||
|
o Treat the input to the escape function in xml.cc as UTF-8, not just
|
||||||
|
ASCII. Good UTF-8 should survive into the output; i.e., "\xe2\x98\xbb"
|
||||||
|
should become "\xe2\x98\xbb" in the output, not "☻".
|
||||||
|
If the input happens not to be UTF-8, (like the file name in
|
||||||
|
http://seclists.org/nmap-dev/2013/q1/180), I suppose we can
|
||||||
|
individually encode each byte of each invalid sequence: "\xba\xda\xbf"
|
||||||
|
becomes "ºÚ¿". Can probably do this with simple
|
||||||
|
byte->rune and rune->byte functions as in
|
||||||
|
http://plan9.bell-labs.com/sys/doc/utf.html.
|
||||||
|
|
||||||
o We should probably redo the Nmap header (e.g. on http://nmap.org) to
|
o We should probably redo the Nmap header (e.g. on http://nmap.org) to
|
||||||
make it more attractive. Or, at a minimum we should update the
|
make it more attractive. Or, at a minimum we should update the
|
||||||
screenshots and think about which links we really need (some of those
|
screenshots and think about which links we really need (some of those
|
||||||
|
|||||||
Reference in New Issue
Block a user