Feature #9221

Set up private Git repo for sharing test suite secrets

Added by anonym 2015-04-10 12:20:04 . Updated 2015-04-18 08:26:05 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Tails_1.4
Start date:
2015-04-10
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

I guess we should use gcrypt, or perhaps that’s overkill.

Subtasks

Related issues

Blocks Tails - Feature #9222: Document how to use shared test suite secrets for release testing Resolved 2015-04-10

History

#1 Updated by anonym 2015-04-10 12:25:44

  • blocked by Feature #9222: Document how to use shared test suite secrets for release testing added

#2 Updated by anonym 2015-04-10 12:25:53

  • blocks deleted (Feature #9222: Document how to use shared test suite secrets for release testing)

#3 Updated by anonym 2015-04-10 12:26:01

  • blocks Feature #9222: Document how to use shared test suite secrets for release testing added

#4 Updated by intrigeri 2015-04-14 13:01:46

  • Assignee changed from intrigeri to anonym
  • QA Check set to Info Needed

Who exactly should have access to that repo?

#5 Updated by anonym 2015-04-15 12:21:23

  • Assignee changed from anonym to intrigeri
  • QA Check changed from Info Needed to Dev Needed

#7 Updated by intrigeri 2015-04-18 08:26:05

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100
  • QA Check deleted (Dev Needed)
git clone tails@git.tails.boum.org:test-suite-shared-secrets

Anyone who needs to give read-only access on that repo to e.g. their test suite VM, please let me know and send me a SSH pubkey for their test suite VM: no need to copy your beloved personal SSH key pair to vaguely trusted systems.