Re: history of system
On Tue, Apr 26, 2005 at 01:54:48PM -0400, Bill Marcum wrote:
> On Tue, Apr 26, 2005 at 09:18:36AM +0100, michael wrote:
> > On Tue, 2005-04-26 at 00:34 -0500, a.list.address@gmail.com wrote:
> > > On 4/25/05, michael <linux@networkingnewsletter.org.uk> wrote:
> > > >
> > > > cHBwICgyLjQuMy0yMDA0MTIzMSszKSB1bnN0YWJsZTsgdXJnZW5jeT1tZWRpdW0KCiAgKiBSZW1v
> > > > dmVkIHBhdGNoIDA1N19wcHBvZS1pbnRlcmZhY2UtY2hhbmdlIHdoaWNoIHdhcyByZWZ1c2VkIGJ5
> > > > IHRoZQogICAgdXBzdHJlYW0gbWFpbnRhaW5lci4gTm93IHVzZXJzIG11c3QgYXJyYW5nZSBmb3Ig
> > > > dGhlIGV0aGVybmV0CiAgICBpbnRlcmZhY2UgdXNlZCBmb3IgUFBQb0UgdG8gYmUgdXAuCiAgKiBU
> > > > aGUgUFBQb0EgcGx1Z2luIGRvZXMgbm90IHJlcXVpcmUgYW55bW9yZSB0aGUgbGliYXRtMSBwYWNr
> > > > YWdlIHRvIGJlCiAgICBpbnN0YWxsZWQuCgogLS0gTWFyY28gZCdJdHJpIDxtZEBsaW51eC5pdD4g
> > > > IFN1biwgMjAgRmViIDIwMDUgMjA6MzQ6MDAgKzAxMDAK
> > > >
> > > > &
> > >
> > > Well, as you can see by the header, it's base64-encoded.
> >
> > But uudecode couldn't decode it...
> >
> uudecode only decodes uuencoded messages.
Actually, uudecode is able to decode it. It needs a little tweaking,
however. Just wrap the encoded block in two lines as follows
begin-base64 640 filename.out
cHBwICgyLjQuMy0yMDA0MTIzMSszKSB1bnN0YWJsZTsgdXJnZW5jeT1tZWRpdW0KCiAgKiBSZW1v
(...)
IFN1biwgMjAgRmViIDIwMDUgMjA6MzQ6MDAgKzAxMDAK
====
Then, after running "uudecode filename.in", you'll find the plain text
content in filename.out.
Not that I'm saying this is the way to go (WRT your original problem),
but just in case you should ever find yourself needing to decode such
stuff... :)
Almut
Reply to: