#10006: Build an obfs-flash PT bundle
-------------------------------------+-------------------
Reporter: dcf | Owner: dcf
Type: task | Status: new
Priority: normal | Milestone:
Component: Pluggable transport | Version:
Resolution: | Keywords:
Actual Points: | Parent ID: #7167
Points: |
-------------------------------------+-------------------
Comment (by infinity0):
Replying to [comment:22 dcf]:
> Replying to [comment:20 dcf]:
> > It seems like we're on the right track. Are you able to test embedding
a manifest in flashproxy-client and obfsproxy? That's the next thing I'd
try. Then you have to test it some way that doesn't involve running it
from the command line (like building a wrapper that sets environment
variables and runs obfs-flash-client).
>
> I tried doing the same `uac_info` thing for flashproxy-client.exe and
obfsproxy.exe, and there was no change. I thought that maybe "Start Tor
Browser.exe", vidalia.exe, and tor.exe might also need to have manifests,
but I didn't know how to do that. I tried going into their properties, and
put them in "Windows 7" compatibility mode, but nothing changed.
>
It's cool, we don't need to use UACs or any of that bullshit. We just need
to have tor.exe start the PT with the `CREATE_BREAKAWAY_FROM_JOB`
(`0x01000000`) flag. I do this in `subproc.py`, and the underlying reason
is the same, explained in detail
[http://blogs.msdn.com/b/cjacks/archive/2009/07/10/how-to-work-around-
program-compatibility-assistant-pca-jobobjects-interfering-with-your-
jobobjects.aspx here].
You could try the trick you did above with tor-hacked.exe. (Perhaps also
add `CREATE_NEW_PROCESS_GROUP` (`0x00000200`) for good karma, but I don't
think it's necessary.)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10006#comment:26>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online