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
yanmaani
Tor
Commits
f93cd5de
Commit
f93cd5de
authored
3 years ago
by
David Goulet
Browse files
Options
Downloads
Patches
Plain Diff
protover: Add a note on why LinkAuth is not recommended or required
Signed-off-by:
David Goulet
<
dgoulet@torproject.org
>
parent
3d1a4990
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/core/or/protover.c
+7
-0
7 additions, 0 deletions
src/core/or/protover.c
with
7 additions
and
0 deletions
src/core/or/protover.c
+
7
−
0
View file @
f93cd5de
...
...
@@ -462,6 +462,13 @@ protover_get_supported_protocols(void)
* XXX: WARNING!
*/
/*
* NOTE: A keen observer will notice that "LinkAuth" is not recommended nor
* required. This is due to the HAVE_WORKING_TOR_TLS_GET_TLSSECRETS define
* that can either set "1" or "1,3" and so we can't enforce one or the other
* due to this uncertainty on how tor was built.
*/
/** Return the recommended client protocols list that directory authorities
* put in the consensus. */
const
char
*
...
...
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