[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #8095 [Stegotorus]: Configurable threshold on the overhead of a payload



#8095: Configurable threshold on the overhead of a payload
-----------------------------+--------------------
     Reporter:  vmon         |      Owner:  zwol
         Type:  enhancement  |     Status:  closed
     Priority:  minor        |  Milestone:
    Component:  Stegotorus   |    Version:
   Resolution:  fixed        |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+--------------------
Changes (by vmon):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Current behavoir is that user can enter option "noise-to-signal" which is
 an integer. The option will be processed by the chopper. The chopper will
 simply passes the value to the steg modules, in this way it asks the steg
 module not to transfer "noise-to-signal" times garbage over data. It is in
 steg module descretion to obay the ratio and also do it intelligently.

 Currently, nosteg module flatly ignore the value as it is called nosteg
 for a reason.

 The http and http_apache modules will pass the ratio to the
 payload_server, the payload server will not choose a payload such that
 size/(requested size) < noise-to-signal. Now, that the payload has the
 extra capacity for the noise, it is in file steg module discretion to use
 this redundancy to stegographized intelligently. Currently no file steg
 module is doing that and only use the beginning of the payload, but it is
 not fundamentally hard to improve the steg algorithm, but that can be
 another ticket.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8095#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs