View Issue Details

IDProjectCategoryView StatusLast Update
0006943Talerdocumentationpublic2021-08-24 14:22
ReporterChristian Grothoff Assigned TottnResolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityurgentSeveritytextReproducibilityN/A
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version0.8Fixed in Version0.8 
Summary0006943: taler merchant manual should inform admins about private keys in database
DescriptionThe Taler merchant backend stores private keys in the database. This should be made explicit in the Taler merchant operator manual, explaining that the database contains sensitive business (and customer) data including key material, and that hence backups of the database should be properly encrypted and/or otherwise secured against illicit access.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2021-07-23 11:24

manager   ~0018006

(Note: this should probably be mentioned in general in the manual, but also again specifically if/when/where we discuss backups.)

ttn

2021-07-31 03:00

reporter   ~0018036

See commit c8676652f40d5aae733052ba95dd17b56ca4c6ce for a start.
If that's okay, next step is to convert the blurb into a frag
and include it in various places.

ttn

2021-07-31 04:36

reporter   ~0018037

I believe we can close this bug now, due to these recent commits:

c8676652f4 2021-07-30 add note re database storing private keys / backups SHOULD be encrypted
1081f8bd20 2021-07-30 fix typo: s/unuathorized/unauthorized/
95ab178523 2021-07-30 move note re database to frags
1fd89a2e23 2021-07-31 include frag re database storing sensitive data
e6c3b7bd3a 2021-07-31 include frag re database storing sensitive data

If there are other places where this note should be included, please re-open.

Issue History

Date ModifiedUsernameFieldChange
2021-07-23 11:24Christian GrothoffNew Issue
2021-07-23 11:24Christian GrothoffStatusnew => assigned
2021-07-23 11:24Christian GrothoffAssigned To => ttn
2021-07-23 11:24Christian GrothoffNote Added: 0018006
2021-07-31 03:00ttnNote Added: 0018036
2021-07-31 04:36ttnStatusassigned => informing
2021-07-31 04:36ttnResolutionopen => fixed
2021-07-31 04:36ttnNote Added: 0018037
2021-07-31 05:53Christian GrothoffProduct Version => git (master)
2021-07-31 05:53Christian GrothoffFixed in Version => 0.8
2021-07-31 05:53Christian GrothoffTarget Version => 0.8
2021-08-24 14:22Christian GrothoffStatusinforming => closed