Bug #10906

Enigmail is configured to use a cleartext hkp:// keyserver

Added by intrigeri 2016-01-12 12:50:32 . Updated 2016-06-08 01:30:51 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_2.4
Start date:
2016-01-12
Due date:
% Done:

100%

Feature Branch:
feature/6154-secure-autoconfig-in-icedove
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Email Client
Deliverable for:
268

Description

I didn’t test it in Tails itself, but config/chroot_local-patches/torbirdy-adjust-defaults.diff patches the upstream code to set the keyserver to hkp://pool.sks-keyservers.net apparently. Why don’t we use our default hkps:// keyserver?

Subtasks

Related issues

Blocked by Tails - Feature #6154: Secure the Icedove autoconfig wizard Resolved 2013-10-16

History

#1 Updated by Anonymous 2016-02-24 11:23:04

  • Target version changed from Tails_2.2 to Tails_2.3

#2 Updated by anonym 2016-03-10 12:58:00

  • Assignee changed from kytv to anonym

#3 Updated by anonym 2016-03-18 17:37:35

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 40
  • Feature Branch set to feature/6154-secure-autoconfig-in-icedove

Seems like an oversight. Fixed (i.e. switched to hkps) in the feature branch.

#4 Updated by anonym 2016-04-20 10:57:06

  • Target version changed from Tails_2.3 to Tails_2.4

#5 Updated by intrigeri 2016-05-10 04:38:26

  • blocked by Feature #6154: Secure the Icedove autoconfig wizard added

#6 Updated by anonym 2016-05-24 20:18:34

  • Assignee changed from anonym to intrigeri
  • % Done changed from 40 to 50
  • QA Check set to Ready for QA

#7 Updated by intrigeri 2016-05-24 23:09:40

Didn’t work for me, so I’ve fixed the keyserver URL in commit:a7c499a.

#8 Updated by intrigeri 2016-05-24 23:37:41

  • Status changed from In Progress to Fix committed
  • Assignee deleted (intrigeri)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

#9 Updated by anonym 2016-06-08 01:30:51

  • Status changed from Fix committed to Resolved