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
Container Registry
Model registry
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
The Tor Project
Core
Tor
Commits
43475790
Commit
43475790
authored
16 years ago
by
Karsten Loesing
Browse files
Options
Downloads
Patches
Plain Diff
Changelog entry for implementation of proposal 121.
svn:r16706
parent
94c35150
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ChangeLog
+6
-3
6 additions, 3 deletions
ChangeLog
with
6 additions
and
3 deletions
ChangeLog
+
6
−
3
View file @
43475790
Changes in version 0.2.1.5-alpha - 2008-08-31
o Major features
[IPv6 support]
:
o Major features:
- Convert many internal address representations to optionally hold
IPv6 addresses.
- Generate and accept IPv6 addresses in many protocol elements.
- Make resolver code handle nameservers located at ipv6 addresses.
- Begin implementation of proposal 121 (Client authorization for
hidden services): associate keys, client lists, and authorization
types with hidden services.
hidden services): configure hidden services with client
authorization, publish descriptors for them, and configure
authorization data for hidden services at clients. (The only missing
piece is to actually access hidden services that perform client
authorization.)
- Network status consensus documents and votes now contain for each
router bandwidth information and a summary of that router's exit
policy. This will in the future be used by clients so that they
...
...
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