Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 920
    • Issues 920
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #7070
Closed
Open
Created Apr 11, 2014 by kytv@kytv

Disable inbound connections within I2P (w/ patch)

Originally created by @kytv on #7070 (Redmine)

Please review and merge the following change for consideration for the
upcoming Tails 1.0

git://repo.or.cz/tails/kytv.git bugfix/i2p_incoming

It’s a small but important change, setting I2P to disable inbound
connections. Inbound connections are already blocked with ferm but this
change lets I2P know about it.

Since repo.or.cz is ridiculously slow for me right now, I’m attaching the trivial patch to this ticket.

Thanks :)

Feature Branch: bugfix/i2p_incoming

Attachments

  • 0001-I2P-disble-inbound-connections.patch
Edited May 21, 2020 by kytv
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking