Nit: {2,2} is the same as {2}

unpack can do your hexifying quite nicely, so you end up with:

while (...) {
   my $raw_length = length($rows[0]);  # Formerly named $ea
   my $encoded = unpack('H*', $rows[0]);
   ...do something with these vars...
}
[download]

You could also use MIME::Base64, which results in a smaller output.

[id://ikegami], I tried using MIME::Base64 to decode the stirng, and I got the string:

�M��m5�M8����}����^��`4�M6ӏ;�ߝ6�]4�m5�M��M��M:�
�ӭ5�m5�m6�
[download]


From the string:

303D02010004087333357537316162A02E0204870BAF350201000201003020300E060A
+2B060102010202010A050500300E060A2B0601020102020110050500
[download]


Ideally, I want it to look like something like this:

000 : 30 3D 02 01 00 04 08 73 33 35 75 37 31 61 62 A0   0=.....s35u71a
+b.
010 : 2E 02 04 87 0B AF 35 02 01 00 02 01 00 30 20 30   ......5......0
+ 0
020 : 0E 06 0A 2B 06 01 02 01 02 02 01 0A 05 05 00 30   ...+..........
+.0
030 : 0E 06 0A 2B 06 01 02 01 02 02 01 10 05 05 00      ...+..........
+.
[download]



These are all from the same packet, the problem is that I can't pass the preformated test from OpenAanval, so I have to dig through the raw DB.


amt.

perlcheat

oops! you're trying to decode! Switch unpack for pack. It's odd to decode before putting it into an email. Is binary data even allowed in emails?

while (...) {
   my $encoded = pack('H*', $rows[0]);
   my $raw_length = length($rows[0]);  # Formerly named $ea
   ...do something with these vars...
}
[download]