[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7559 [Flashproxy]: Registration via indirect URL request
#7559: Registration via indirect URL request
------------------------+---------------------------------------------------
Reporter: dcf | Owner: aallai
Type: project | Status: needs_revision
Priority: normal | Milestone:
Component: Flashproxy | Version:
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by dcf):
Replying to [comment:7 dcf]:
> I decided that I want to architect the local facilitator programs
differently, so this ticket is pending until I do that. This is how I
expect it to break down:
I've made the above changes involving `flashproxy-reg-daemon` and
`flashproxy-reg` in master. `flashproxy-reg-email` now doesn't touch the
private key and delegates registrations to `flashproxy-reg`. This updated
master is now running on the public facilitator.
Please pull from my branch at
https://gitweb.torproject.org/user/dcf/flashproxy.git/shortlog/refs/heads/url_reg,
which has merged the above changes from master. Adapt your changes to
`facilitator.cgi` to work with the new system, namely, call
`fac.put_reg_base64` which delegates to `flashproxy-reg`. You will
probably have to convert the base64 alphabet before doing so. The public
key in `flashproxy-reg-url` should now be the same as that in `flashproxy-
reg-email`.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7559#comment:8>
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