On Wed, Aug 19, 2015 at 8:43 PM, Alec Muffett wrote:
>
> Hi, I'm Alec, and I am co-author of the Onion RFC draft with Jacob Appelbaum.
>
> Reports of the bogging-down have been greatly exaggerated, and I wish people
> would stop repeating them.
>
> The status of the Onion RFC draft is viewable at
Alec Muffett writes:
> Pardon me replying to two at once...
Thanks for all the helpful clarifications, Alec.
--
Seth Schoen
Senior Staff Technologist https://www.eff.org/
Electronic Frontier Foundation https://www.eff.org/join
815 Eddy Street, San Franci
Flipchan writes:
> Im wondering , have anyone got letsencrypt to work with a .onion site? Or is
> it jus clearnet
For the reasons described elsewhere in this thread, it's definitely
just clearnet for the foreseeable future.
--
Seth Schoen
Senior Staff Technologist https
Im wondering , have anyone got letsencrypt to work with a .onion site? Or is it
jus clearnet
Alec Muffett skrev: (19 augusti 2015 20:43:53 CEST)
>Pardon me replying to two at once...
>
>
>> On Aug 19, 2015, at 18:34, Seth David Schoen wrote:
>>
>> [...]
>> Right now, the industry allows .onion
Pardon me replying to two at once...
> On Aug 19, 2015, at 18:34, Seth David Schoen wrote:
>
> [...]
> Right now, the industry allows .onion certs temporarily, but only EV
> certs, not DV certs (the kind that Let's Encrypt is going to issue),
> and the approval to issue them under the current c
elrippo writes:
> Hy,
> i don't think letsencrypt will work on a HS because letsencrypt checks [1] if
> the domain you type in, is registered.
> So for example on a clearnet IP which has a registered domain at mydomain.com
> called myserver.tld, letsencrypt makes a DNS check for this clearnet IP
Fabio Pietrosanti (naif) - lists writes:
> Hello,
>
> does anyone had looked into the upcoming Letsencrypt if it would also
> works fine with Tor Hidden Services and/or if there's some
> complexity/issues to be managed?
>
> As it would/could be interesting if Tor itself would support directly
>
Hy,
i don't think letsencrypt will work on a HS because letsencrypt checks [1] if
the domain you type in, is registered.
So for example on a clearnet IP which has a registered domain at mydomain.com
called myserver.tld, letsencrypt makes a DNS check for this clearnet IP and
gets the awnser, that
