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
Stop using "checksumming" instead of "encrypting" in the docs #76168
Conversation
All encryption systems have a formal inverse function to decrypt A hash is a one way function without inverse by definition
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 for your contribution, I reviewed it and discovered that below the hashing examples in this documentation section, there are also examples of encryption with vault
/unvault
at the bottom. So it sounds like there's both encryption and hashing present. Note that the title also mentions "checksumming" — I believe that this part is what refers to hashing in the examples. Would you agree with this judgement?
You are right that now there is content about vault storage and that is encrypted storage. This content have been added in commit 90518d8 on September 1th 2021 and I haven't read it in https://docs.ansible.com/ansible/latest/user_guide/playbooks_filters.html#encrypting-and-checksumming-strings-and-passwords. Preparing this pull request I noticed the vault part but thought that it would be another section. So this title was wrong all this time but could be correct thanks to this recent addition. |
I agree that cryptographically strong hash code could be a good checksum. But Checksums and hashes have different uses and requirements. See introductions from wikipedia: |
@webknjaz what do you think of the updated heading now? |
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.
LGTM
…e#76168) * Hashing is not encrypting All encryption systems have a formal inverse function to decrypt A hash is a one way function without inverse by definition * Update docs/docsite/rst/user_guide/playbooks_filters.rst Co-authored-by: Sandra McCann <samccann@redhat.com>
* Stop using "checksumming" instead of "encrypting" in the docs (#76168) * Hashing is not encrypting All encryption systems have a formal inverse function to decrypt A hash is a one way function without inverse by definition * Update docs/docsite/rst/user_guide/playbooks_filters.rst Co-authored-by: Sandra McCann <samccann@redhat.com> * ansible-core 2.12 dropped support for galaxy.yaml. (#76179) * apt - remove obsolete documentation (#76243) The lock_timeout feature was recently added to the apt module making this section in the documentation no longer necessary * Documentation for other types in collection `requirements.yml` (#75872) * Docs: Link to valid data types for role parameters (#76276) * Fixed typo in keyword_desc.yml (#76280) The description of 'max_fail_percentage' had a typo. * Restore documentation on M() and R() (#76284) * Undo most of bf99442, add note on where R() does not work. Co-authored-by: Brian Scholer <1260690+briantist@users.noreply.github.com> Co-authored-by: Vicente Jimenez Aguilar <googuy@gmail.com> Co-authored-by: Sandra McCann <samccann@redhat.com> Co-authored-by: Felix Fontein <felix@fontein.de> Co-authored-by: Sam Doran <sdoran@redhat.com> Co-authored-by: Daniel Goldman <merkavabuilder@gmail.com> Co-authored-by: nkoechling <nkoechling@users.noreply.github.com>
All encryption systems have a formal inverse function to decrypt
A hash is a one way function without inverse by definition
SUMMARY
Change title in template filter documentation that says encrypting when hashing is described
ISSUE TYPE
COMPONENT NAME
Template hashing and checksum filters