Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Tor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
sergi
Tor
Commits
e72f5842
Commit
e72f5842
authored
21 years ago
by
Roger Dingledine
Browse files
Options
Downloads
Patches
Plain Diff
add a list of backward-incompatible things we need to do
svn:r1650
parent
0e94b9ff
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/TODO
+12
-0
12 additions, 0 deletions
doc/TODO
with
12 additions
and
0 deletions
doc/TODO
+
12
−
0
View file @
e72f5842
...
...
@@ -11,6 +11,18 @@ ARMA - arma claims
D Deferred
X Abandoned
Flag-day changes: (things which are backward incompatible)
. remove link key from directories, from connection_t.
(just get it from the tls cert)
. make onion keys include oaep padding, so you can tell
if you decrypted it correctly
. add bandwidthrate and bandwidthburst to server descriptor
- directories need to say who signed them.
- what other pieces of the descriptors need to change?
maybe add a section for who's connected to a given router?
add a flexible section for reputation info?
Bugs:
o we call signal(), but we should be calling sigaction()
o send socks rejects when things go bad ?
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment