Opened 6 years ago

Closed 5 years ago

#16277 closed task (fixed)

Finish setting up the Sandstorm instance

Reported by: isis Owned by: isis
Priority: Medium Milestone:
Component: Internal Services/Service - sandstorm Version:
Severity: Keywords:
Cc: isis, weasel, nickm, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

For now, since our Sandstorm installation rather heavily relies on Debian Jessie features, and our VM hosting provider has some problem with their virtualisation infrastructure, weasel and I have agreed that it's not possible to move the Sandstorm instance at http://para.noid.cat to a TPO-controlled server.

However, and despite my putting a GIANT, ALL-CAPS WARNING THAT MY SERVER HAS ZERO TRANSPORT LAYER ENCRYPTION AND THE SANDSTORM INSTANCE SHOULDN'T BE USED FOR ACTUAL, SENSITIVE TOR PROJECT DOCUMENTS AND RESOURCES YET in my email announcing our Sandstorm instance, some people have already started doing exactly that. Ergo, this thing needs TLS now (or needed it yesterday!).

Because we can't easily relocate to a TPO-controlled server immediately, weasel and I have agreed that likely the most sensible thing to do would be to:

  1. Point the storm.torproject.org and other required DNS entries at my server.
  2. Purchase TLS certificates for *.storm.torproject.org and storm.torproject.org.

Child Tickets

TicketStatusOwnerSummaryComponent
#16278closedObtain TLS certificates for the Sandstorm instanceArchived/operations
#16279closedSetup DNS entries for storm.torproject.orgInternal Services/Tor Sysadmin Team

Change History (2)

comment:1 Changed 6 years ago by isis

Component: - Select a componentService - sandstorm

comment:2 Changed 5 years ago by isis

Resolution: fixed
Status: newclosed

Completed in June 2015, but forgot to close this ticket.

Note: See TracTickets for help on using tickets.