Tag Info

Hot answers tagged

4

Converting chars to hex is not really encryption. Converted back to ASCII characters it's just a regular html document, letting you know who the hackers are: <html><head> <meta content="text/html;charset=utf-8"> <title>./rEdX|3xp1r3CyberArmy</title> <meta name="author" content="rEdX"/> <meta name="keywords" ...


4

BSD Hexdump (package bsdmainutils on Ubuntu): hexdump -C -s SKIP -n COUNT FILENAME


4

This Bash function should work for you: writehex () { while [ $1 ]; do for ((i=0; i<${#1}; i+=2)) do printf "\x${1:i:2}"; done; shift; done } To test it: $ writehex abc00001ff | hexdump -C 00000000 ab c0 00 01 ff |.....| 00000005 $ writehex f6050000 ac7e0500 ...


3

How about md5? domain=example.com color=#`echo -n $domain | md5 | cut -c1-6` The resulting variable $color will be #5ababd


2

With perl: perl -ne '@a=split;for(@a){print chr(hex($_))}' inputfile > outputfile Where the content of inputfile is formatted: 42 43 44 outputfile would then contain BCD. You can prep your input file in vi like so: :%s/ //g :%s/\(.\{2\}\)/\1 /g That will remove all spaces, then insert a space between every character. The example you gave using ...


1

sed should not be "[filtering] out all non-printable characters" - you're not telling it to do so. In fact a simple test on a convenient binary file (the FreeBSD kernel) demonstrates that this is not the case - sed happily passes non-printable characters. Shame on you for publicly accusing poor innocent sed of doing something heinously wrong without ...


1

I believe the most trouble understanding the hex representation of the partition table comes from the endianness problem. Intel PCs are based on the little-endian architecture with an actual reversed byte order for multi-byte number representations. So the LBA sector offset number like 01388b3b is stored as 3b8b 3801 - which is right there in your MBR / ...


1

Depends on the OS, system, and file-system format. Wikipedia is a good resource on the subject: http://en.wikipedia.org/wiki/Master_boot_record Start following the layout. The partition table entries start at 000001BE ... with the 16-byte partition record... skipping the not-so-important bits... the 1st partition is NTFS (000001C3) and starts at ...


1

You can look it up in rfc792 (page 13): Identifier If code = 0, an identifier to aid in matching echos and replies, may be zero. Here is another usefull link: http://www.iana.org/assignments/icmp-parameters/icmp-parameters.xml


1

In future, you can answer this yourself by going to the Cygwin package search page. There is no xd binary in any official Cygwin packages, but since the xd homepage you linked to contains the Win 32 binary, you can just download and use that. Or you could download the source and compile it under Cygwin (untested, but likely to work).


1

Take a look at bvi or hexedit.


1

What about a hex editor, like hexedit ou hexer? You can directly edit the file and type values in hexadecimal with them.



Only top voted, non community-wiki answers of a minimum length are eligible