-
Notifications
You must be signed in to change notification settings - Fork 42
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
Cryptoerror logs #1090
Cryptoerror logs #1090
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks okay to me. Approved. But,I will wait for another look from @redshiftzero before merging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one comment, otherwise lgtm!
os.path.basename(filepath), os.path.dirname(filepath)) | ||
) | ||
type(db_object), db_object.uuid, session, original_filename=original_filename) | ||
logger.info(f'File decrypted to {filepath}') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think here in the decrypt method, on success we should provide the enclosing directory (i.e. log that the file can be found in os.path.dirname(filepath)
), since the file at filepath
will not exist if the user is looking for it - what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
da1f07b
to
9449bcc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
restamping
Description
Clean up noisy logs around decryption errors: #1083 (comment)
Before
Info level
Debug level
After
Info level
Debug level
Test Plan
Follow test plan here: #1059 (comment)
Checklist
If these changes modify code paths involving cryptography, the opening of files in VMs or network (via the RPC service) traffic, Qubes testing in the staging environment is required. For fine tuning of the graphical user interface, testing in any environment in Qubes is required. Please check as applicable:
If these changes add or remove files other than client code, the AppArmor profile may need to be updated. Please check as applicable:
If these changes modify the database schema, you should include a database migration. Please check as applicable:
master
and confirmed that the migration applies cleanlymaster
and would like the reviewer to do so