Feature #7916

Disable default I2P outproxy

Added by kytv 2014-09-19 11:27:37 . Updated 2014-10-16 08:11:06 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_1.2
Start date:
2014-09-19
Due date:
% Done:

100%

Feature Branch:
kytv:feature/7916-i2p_remove_ssl_outproxy
Type of work:
Code
Blueprint:

Starter:
Affected tool:
I2P
Deliverable for:

Description

History

“Back in the day”, the HTTP and HTTPS outproxies were run by two distinct individuals and required two separate tunnels in I2P. Recently, the java implementation of Tor (Orchid) was ported to I2P in the form of a plugin. At that point, (optional) HTTPS support was added to the default eepsite tunnel, so one could add an SSL outproxy to the eepsite tunnel to access SSL/TLS enabled websites. Sometime after that, another user took over running the outproxy; this user is also allowing outproxy access to HTTPs sites.

Present

A few days ago, the default outproxy (which, as mentioned above, services both HTTP and HTTPS) was added to the default config. Tails, of course, does not want to have an outproxy configured within I2P. Therefore, the chroot_local-hooks hook for I2P needs an update for I2P 0.9.15.

Subtasks

Related issues

Related to Tails - Feature #7936: I2P 0.9.15 Resolved 2014-09-22

History

#1 Updated by kytv 2014-09-19 15:34:11

  • Assignee deleted (kytv)
  • % Done changed from 0 to 50
  • QA Check changed from Dev Needed to Ready for QA
  • Feature Branch set to feature/7916-i2p_remove_ssl_outproxy

#2 Updated by kytv 2014-09-19 15:36:22

  • Feature Branch changed from feature/7916-i2p_remove_ssl_outproxy to kytv:feature/7916-i2p_remove_ssl_outproxy

#3 Updated by kytv 2014-09-22 12:22:29

#4 Updated by anonym 2014-09-25 19:40:29

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

#5 Updated by anonym 2014-10-16 08:11:06

  • Status changed from Fix committed to Resolved