Minor control-spec.txt corrections.

Re: SETCONF:

Tor responds with a "250 configuration values set" reply on success. If some of the listed keywords can't be found, Tor replies with a

According to git blame that hasn't been the case since... 2008? 2007?

      case SETOPT_OK:
        config_free_lines(lines);
        send_control_done(conn);
        return 0;

Sent from the client to the server. The syntax is as for GETCONF: "GETINFO" 1*(SP keyword) CRLF one or more NL-terminated strings. The server replies with an INFOVALUE message, or a 551 or 552 error.

"one or nor NL-terminated strings" is confusing. Did a newline and a word get cutoff somewhere, or am I just being dense?

changed milestone to %Tor: 0.3.2.x-final

added component::core tor/tor doc easy milestone::Tor: 0.3.2.x-final owner::nickm points::0.1 priority::very low resolution::fixed severity::normal status::closed tor-control tor-spec type::defect version::tor unspecified labels

Replying to yawning:

Re: SETCONF:

Tor responds with a "250 configuration values set" reply on success. If some of the listed keywords can't be found, Tor replies with a

According to git blame that hasn't been the case since... 2008? 2007?

Do you mean that the text is different? Current tor responds with '250 OK'.

Sent from the client to the server. The syntax is as for GETCONF: "GETINFO" 1*(SP keyword) CRLF one or more NL-terminated strings. The server replies with an INFOVALUE message, or a 551 or 552 error.

"one or nor NL-terminated strings" is confusing. Did a newline and a word get cutoff somewhere, or am I just being dense?

INFOVALUE also isn't defined or used anywhere else. Both of those issues date back to 2005.

Replying to special:

Replying to yawning:

Re: SETCONF:

Tor responds with a "250 configuration values set" reply on success. If some of the listed keywords can't be found, Tor replies with a

According to git blame that hasn't been the case since... 2008? 2007?

Do you mean that the text is different? Current tor responds with '250 OK'.

Indeed. It stood out as the only thing not documented to return 250 OK.

Sent from the client to the server. The syntax is as for GETCONF: "GETINFO" 1*(SP keyword) CRLF one or more NL-terminated strings. The server replies with an INFOVALUE message, or a 551 or 552 error.

"one or nor NL-terminated strings" is confusing. Did a newline and a word get cutoff somewhere, or am I just being dense?

INFOVALUE also isn't defined or used anywhere else. Both of those issues date back to 2005.

Yup. Should figure out what it should say.

Trac:
Milestone: N/A to Tor: 0.2.7.x-final

Trac:
Status: new to assigned

Marking triaged-out items from first round of 0.2.7 triage.

Trac:
Keywords: N/A deleted, 027-triaged-1-out added

Make all non-needs_review, non-needs_revision, 027-triaged-1-out items belong to 0.2.???

Trac:
Milestone: Tor: 0.2.7.x-final to Tor: 0.2.???

Trac:
Sponsor: N/A to N/A
Cc: N/A to gk
Severity: N/A to Normal

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Milestone: Tor: 0.3.??? to Tor: unspecified
Keywords: N/A deleted, tor-03-unspecified-201612 added

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: N/A deleted, 027-triaged-in added

Trac:
Keywords: 027-triaged-in deleted, N/A added

Trac:
Keywords: 027-triaged-1-out deleted, N/A added

Unify controller keyword to "tor-control".

Trac:
Keywords: N/A deleted, controller added

Unify "controller" keyword to "tor-control".

Trac:
Keywords: controller deleted, tor-control added

Cleanup remaining "tor-controller" that already have "tor-control"

Trac:
Keywords: tor-controller deleted, N/A added

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

Trac:
Status: assigned to new

Trac:
Status: new to accepted
Keywords: N/A deleted, doc, easy added
Points: N/A to 0.1
Owner: N/A to nickm
Reviewer: N/A to N/A
Milestone: Tor: unspecified to Tor: 0.3.2.x-final

d92fc8b17b207c fixes this.

The INFOVALUE thing was left over from control-spec-v0.txt

Trac:
Resolution: N/A to fixed
Status: accepted to closed

closed

changed time estimate to 48m

moved to tpo/core/tor#15333 (closed)