// COMPLETE THREAD

Re: do NOT escrow communications keys (Re: What's really in PGP 5.5?)

2 expanded posts ยท every known parent and child

NODE 28a8c5a2Re: do NOT escrow communications keys (Re: What's really in PGP 5.5?)
-----BEGIN PGP SIGNED MESSAGE-----

Adam Back wrote:
>About the only example of email in transit being considered storage
>was a USENET article years ago by someone who considered it a kewl
>hack that he had some games or something else which was in breach of
>policy in his account and rumor went around that the admin was having
>a purge.  He tarred, gzipped & uuencoded the lot and emailed it to
>himself down a _long_ ! fowarding path.  It came back to him around 3
>days later after the purge.  That's the kind of thing I mean when I
>say you don't consider email storage.

Sometimes you can use this trick to get around storage limitations at
your ISP.  Often mail in the spool file doesn't get added up for the
disk quota.  When you hit your limit, just e-mail yourself a bunch of
megabyte messages.  Sysadmins tend not to like this.

Monty Cantsin
Editor in Chief
Smile Magazine
http://www.neoism.org/squares/smile_index.html
http://www.neoism.org/squares/cantsin_10.html


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQEVAwUBND5t8JaWtjSmRH/5AQFf9wf/TQMiQH4wJXO3Xx/borwAobWIlKQCGmVQ
BnflPYg5pDvHOc+vppprb/f5HLZ78p1WaOY9l7vc+aJ97NC346UQAzS8kGyr6WP7
YmHmWRx576CV8EsLWjMZFYB6fZXvvMQd6VGUPC9IKC9Zum2BV1GCUSxGIHFpwNDp
ElfqFFlFdVqfh30XEi2e/XK7UKh6bzYMHgfHTEjv+FqV1grXpGlwDHQfWvPMv4s8
ZEO8XM7Sh6DOXEMnrZkKJ0dl9cW8FjphEeYbkePV9oPVuCqC8HF6gzFfGLtWMK6E
nj7iuv1QoQPagk4nwogHRUjhuuFg0aDcHieDR7T1HivFReB5fZIHYQ==
=HCXe
-----END PGP SIGNATURE-----
NODE 2c3d9d51Re: do NOT escrow communications keys (Re: What's really in PGP 5.5?)
Monty wrote:
> Adam Back wrote:
> >[emailing stuff to yourself]
> 
> Sometimes you can use this trick to get around storage limitations at
> your ISP.  Often mail in the spool file doesn't get added up for the
> disk quota.  When you hit your limit, just e-mail yourself a bunch of
> megabyte messages.  Sysadmins tend not to like this.

Yep, I've done both of these.

Mail spool didn't count on quota, so I wrote some scripts to store and
retrieve messages from /usr/mail/aba.  Didn't actually use them, but I
enjoyed writing them :-)

Also we had a temporary scratch 1 Gig partition on one machine.  Your
stuff was defined to live for 1 week after last access.  So I put

	find /scratch -name \* -exec touch {} \; &

in my .login.  So the stuff was always up to date and lived for ever :-)

The hack caught on, and soon everyone was doing this, and I got a
polite note from admin of the system in question telling me (they
determined I was the ring leader somehow) to pass the word around that
this was not ok, and reprisals in terms of deletion of touched files
would occur to those doing it.

Phun stuff.  (Oddly that and other experimentation ensured I was not
the admins favourite student.)

Adam
-- 
Now officially an EAR violation...
Have *you* exported RSA today? --> http://www.dcs.ex.ac.uk/~aba/rsa/

print pack"C*",split/\D+/,`echo "16iII*o\U@{$/=$z;[(pop,pop,unpack"H*",<>
)]}\EsMsKsN0[lN*1lK[d2%Sa2/d0<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<J]dsJxp"|dc`