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

[Tor Bug Tracker & Wiki]

#27446: HS creation via SETCONF changed from v2 to v3
--------------------------+------------------------------------
 Reporter:  atagar        |          Owner:  (none)
     Type:  defect        |         Status:  new
 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:
--------------------------+------------------------------------

Comment (by dgoulet):

 Replying to [comment:3 atagar]:
 > * [**Tor**] Could you please clarify the above error response? Since
 we're breaking backward compatibility we should be very clear in the
 response what is going on. In particular when users provide v2 HS
 arguments we should provide a response such as...
 >
 >   ''"Version 2 hidden services are deprecated, and this method now
 creates v3 hidden services by default which is incompatible with the X
 argument. Please see Y for our documentation on v3 hidden services, and
 include 'HiddenServiceVersion 2' if you would like to explicitly create a
 version 2 hidden service anyway."''

 So this is a "fun" one ... The reported error is really a "generic" one
 because there are so many ways you can fail configuration that we log the
 error and then provide that generic failure message at in the end.

 In other words, we would need a major refactoring to be able to tell the
 user if the error was related to a v2 option used with v3 for instance.
 Which is probably why there is this "see logs for details"...

 I'm not sure how we can fix that so users on the control port at least get
 something meaningful?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27446#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online