Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After journalist designation is changed, we must rename files that have already been decrypted #282

Closed
redshiftzero opened this issue Mar 26, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@redshiftzero
Copy link
Contributor

Followup to #250, discovered during review of #277

Steps to Reproduce

  1. Submit file as a source
  2. Log into client, download the file. e.g. it will be saved in your client data dir as 2-ducal_hellhound-doc when successfully decrypted
  3. Cycle the journalist designation for that source, e.g. to translucent intrigue
  4. Refresh the client
  5. Source will appear with the new codename
  6. Try to open the file you downloaded: log line like the following will appear:

2019-03-26 07:56:13,591 - securedrop_client.logic:578(on_file_open) INFO: Opening file "/var/folders/gv/2r10zvfj303fyd5_6yn_p0b80000gn/T/tmp.USqujvA3/data/2-translucent_intrigue-doc".

Expected behavior

/var/folders/gv/2r10zvfj303fyd5_6yn_p0b80000gn/T/tmp.USqujvA3/data/2-translucent_intrigue-doc exists on disk and thus can be opened

Actual behavior

Downloaded/decrypted file is still called /var/folders/gv/2r10zvfj303fyd5_6yn_p0b80000gn/T/tmp.USqujvA3/data/2-ducal_hellhound-doc

Comments

When a journalist designation changes, we should also rename files that have been decrypted, i.e. those that no longer end in .gpg

@redshiftzero redshiftzero added the bug Something isn't working label Mar 26, 2019
@eloquence eloquence added this to Near Term Backlog in SecureDrop Team Board Mar 26, 2019
@eloquence eloquence moved this from Near Term Backlog to Nominated for next sprint (4/3-4/17) in SecureDrop Team Board Mar 27, 2019
@eloquence eloquence moved this from Nominated for next sprint (4/3-4/17) to Near Term Backlog in SecureDrop Team Board Mar 29, 2019
@redshiftzero
Copy link
Contributor Author

this feature will be gone on server side as of 1.2.1 so closing (ref freedomofpress/securedrop#4304)

SecureDrop Team Board automation moved this from Near Term - SD Workstation to Done Feb 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Development

No branches or pull requests

1 participant