bugtraq - Re: [Full-Disclosure] Re: [PAPER] Juggling with packets: floating data storage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Wed, 08 Oct 2003 15:58:22 -0400
From: Valdis.Kletnieks@...edu
To: Nicholas Weaver <nweaver@...berkeley.edu>
Cc: bugtraq@...urityfocus.com, secpapers@...urityfocus.com,
	vulnwatch@...nwatch.org, vulndiscuss@...nwatch.org,
	full-disclosure@...sys.com
Subject: Re: [Full-Disclosure] Re: [PAPER] Juggling with packets: floating data storage

On Wed, 08 Oct 2003 12:03:20 PDT, Nicholas Weaver said:

> If my external link is "ONLY" 100 Mb, and the latency/refresh time is
> 1 minute, thats 768 MB of data.
> 
> So who cares?  Why juggle when shelves hold so much more?

Well.. sometimes, you need to store a small amount of data (20-30K of 0day
exploit or encryption key or similar, perhaps?) where people perusing the
bookshelf won't notice it.

I know of somebody who worked out a filesystem that used the "dead space"
between end-of-file and end-of-block to store data.  Who cares?  Somebody who
doesn't want it noticed.....

Content of type "application/pgp-signature" skipped