You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See freedomofpress/securedrop-export#69 and #1226 where we introduced semgrep, custom rules, and some safety functions for file system operations in utils.py. This code is useful across projects so we should create a new library called securedrop-path or securedrop-safety or something that works for functions such as:
safe_mkdir
safe_extract
safe_decrypt
This will also help standardize the way we create and cleanup files (which can be confusing, see #1228).
The text was updated successfully, but these errors were encountered:
sssoleileraaa
changed the title
Make a securedrop-path library for all our safety functions that we use across projects, e.g. export, client
Python library for SecureDrop Workstation filesystem operations
Apr 28, 2021
@creviera has offered to take a first stab at a spike to implement such a library, with the goal to prepare a draft PR for broader input as part of the 5/5-5/19 sprint.
I didn't get as far as opening a draft PR because of the security issue that came up during the sprint, but I have something started:
I propose we name the new module securedrop-pathlib. Once we agree on that, I can create a new repo and work with infra to set this up. Until then I'm working on fixing up tests, moving code around, and getting things to just work here: https://github.com/creviera/securedrop-pathlib. You can install securedrop-pathlib in the client virtualenv on this test branch by following these steps:
Description
See freedomofpress/securedrop-export#69 and #1226 where we introduced semgrep, custom rules, and some safety functions for file system operations in
utils.py
. This code is useful across projects so we should create a new library calledsecuredrop-path
orsecuredrop-safety
or something that works for functions such as:This will also help standardize the way we create and cleanup files (which can be confusing, see #1228).
The text was updated successfully, but these errors were encountered: