// COMPLETE THREAD

Re: standard for stegonography?

2 expanded posts ยท every known parent and child

NODE 5317c62fRe: standard for stegonography?
Sergey Sez:
> Have the offset default to the checksum-value of the reciever's public key!  
> The sending program could have the user specify the reciever, look his key
> up in the public-keyring and offset the message accordingly.  While, the 
> recieving program would automatically scan the file starting at the 
> appropriate offset based on the same public key checksum-value.

While Tim May Sez:

> Lots of options for standards. As others have noted, you just don't
> want to have to flag what standard you're using in the message itself
> (in plaintext, else why bother?) as that means the stego use is not
> longer plausibly deniable.


I think these two have a lot to do with each other. Sergeys' suggestion 
would definitely make it a tougher to pick out a starting place to 
search for hidden text. However, the message (if it is ever found in the 
file) points to the intended recipient. This defeats the purpose of 
"stealth pgp", (which would probably be used in this case to strip off 
telltale headers and such). 

If you weren't worried about this type of deniability, though, I don't 
see a problem with it.

mt

Matt Thomlinson                               Say no to the Wiretap Chip!
University of Washington, Seattle, Washington.
Internet: phantom@u.washington.edu      	    phone: (206) 548-9804
PGP 2.2  key available via email or finger phantom@hardy.u.washington.edu
NODE 1da36d7eRe: standard for stegonography?
On Sun, 27 Feb 1994, Matt Thomlinson wrote:
 
> I think these two have a lot to do with each other. Sergeys' suggestion 
> would definitely make it a tougher to pick out a starting place to 
> search for hidden text. However, the message (if it is ever found in the 
> file) points to the intended recipient. This defeats the purpose of 
> "stealth pgp", (which would probably be used in this case to strip off 
> telltale headers and such). 
> 

The hidden message need may be a stripped PGP encrypted file.  It need not
specify who its addressed to!  The intended recipient will be able to 
retrieve the file regardless.  His program should automatically revive 
the file starting from _his_ public-key checksum-value offset (which both 
the sender and the reciever already know, without the need for any 
telltale headers in the file).  Even if the opponent tries all possible 
offsets and filelengths he/she will always get noise, never anything 
pointing to the reciever.

> If you weren't worried about this type of deniability, though, I don't 
> see a problem with it.
> 

It wasn't me!  ;)

> mt
> 
> Matt Thomlinson                               Say no to the Wiretap Chip!
> University of Washington, Seattle, Washington.
> Internet: phantom@u.washington.edu      	    phone: (206) 548-9804
> PGP 2.2  key available via email or finger phantom@hardy.u.washington.edu
> 


Sergey