- To: lists@xxxxxxxxxx
- Subject: Re: [SLUG] decodeing base64 ?
- From: Peter Chubb <peterc@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 6 Apr 2006 11:01:17 +1000
- Cc: slug@xxxxxxxxxxx
- Comments: Hyperbole mail buttons accepted, v04.18.
>>>>> "Voytek" == Voytek Eymont <lists@xxxxxxxxxx> writes:
Voytek> On Thu, April 6, 2006 10:28 am, Peter Chubb wrote:
>>>>>>> "Voytek" == Voytek Eymont <voytek@xxxxxxxxxx> writes:
>> Most mime-compliant mailers have base64 coding/decoding built in.
Voytek> is there a command here to detach it, I tried sending it to a
Voytek> file, but, the whole file transferred
Edit the file afterwards; delete all but the base64 encoded part.
>> uudecode expects a begin 644 filename
>>
>> line at the start of the file.
>>
>> You could try:
>>
>>
>> { echo 'begin-base64 644 x.wav'; cat file; echo ====; } | uudecode
Voytek> get 'iilegal line'
Voytek> [root@rhel mail]# { echo 'begin-base64 644 x.wav'; cat test;
Voytek> echo ====; } | uudecode uudecode: stdin: illegal line
Everything between the begin and end needs to be base64-encoded. You
probably sent it the entire file.
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au ERTOS within National ICT Australia