Opened 14 years ago

#226 closed defect (Implemented)

Torcp tries to change ORPort even in 0.1.0.15

Reported by: arma Owned by: edmanm
Priority: Low Milestone:
Component: Tor - Tor Control Panel Version: 0.1.0.15
Severity: Keywords:
Cc: arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

It looks like TorCP 0.0.4 (from the bundle) will let you try to change your ORPort, but it will fail,
because we only added that feature in 0.1.1.6-alpha. Perhaps TorCP should make use of what Tor version
you have, and tell you that you need to upgrade to the experimental package if you want to become a
Tor server?

I suppose the documentation should say that too.

[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]

Child Tickets

Change History (4)

comment:1 Changed 14 years ago by edmanm

Vidalia 0.0.2 checks to make sure the Tor it's talking to can speak V1 of
the control protocol. I assume that if a Tor can speak V1, then it can deal
when I ask it to change its ORPort. This, of course isn't true in every
instance (e.g., pre-0.1.1.13 will just crash), but it should generally be
true for recent and future Tors, yes?

comment:2 Changed 13 years ago by arma

Correct.

You could even be smarter and notice if the Tor version is buggy
("getinfo version") and let the user know he should upgrade.

Of course, if vidalia and tor are mostly shipped as a bundle, then
an old vidalia won't magically be able to learn that the tor it shipped
with has some new versions.

But Vidalia could notice the warn messages from Tor about running an
un-recommended version and display these in some higher priority way.

comment:3 Changed 13 years ago by edmanm

Vidalia notices warn messages and logs them in yellow. Err messages get logged in red, so
hopefully people will notice them.

I'm going to go ahead and close this, in hopes of moving TorCP's slow death along a bit.

comment:4 Changed 13 years ago by edmanm

flyspray2trac: bug closed.

Note: See TracTickets for help on using tickets.