Question about adding EBCDIC conversion function

[Tom Sellers <nmap () fadedcode net>]

I have a question about adding function to convert EBCDIC encoded
data to ASCII...  Before my primary machine died this last weekend I
was working on a NSE script to extract information from IBM DB2
database instances in a manner similar to what we do now with MS SQL.
Right now I can pull the server version, platform and database instance
name using a IBM DB2 EXCSAT (Exchange server attributes) command.
This is an IBM supported command that, from what I can tell, has no
negative effects.  Wireshark's dissectors are absolutely invaluable when
doing this..those guys are great.

Anyway... its almost done, I should be able to submit it when I get my
machine up and running again.

Part of this script takes EBCDIC encoded hex values from the server
response and returns the human readable ASCII values.  While the
conversion code is not super robust it should be sufficient for the
NSE script I am using it in.

Would there be any value to adding this conversion ability to one of
the existing libraries?  I expect us to see EBCDIC encoded data when
dealing with big iron and certain classes of software, such as DB2.

If you think it is worth while let me know which library you want it
in.   I will expand the code to be more complete and robust.

Also, if anyone has run into EBCDIC encoded responses from services
please let me know.  That will help me gauge demand as well as potentially
giving me a chance to test the conversion code more thoroughly.

Thanks much,

Tom
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/