Re: [tor-bugs] #27446 [Core Tor/Tor]: HS creation via SETCONF changed from v2 to v3

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#27446: HS creation via SETCONF changed from v2 to v3
--------------------------+------------------------------------
 Reporter:  atagar        |          Owner:  (none)
     Type:  defect        |         Status:  needs_information
 Priority:  Medium        |      Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  tor-hs        |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------
Changes (by dgoulet):

 * cc: dgoulet (removed)
 * keywords:   => tor-hs
 * status:  new => needs_information


Comment:

 Yes we recently made it that the default version is now 3 so one has to
 explicitly put `HiddenServiceVersion 2` starting on 0.3.5 (not yet
 released).

 To answer your question now, yes it breaks backward compatibility for
 *new* services. Old services, tor will detect the version by looking at
 the key material and if it sees an RSA key in the appropriate file, then
 your service will be a v2.

 The idea is indeed long term to phase out v2. Hope this answers your
 question?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27446#comment:2>
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