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

Fixes for gensalt handling with libxcrypt. #144

Closed
wants to merge 2 commits into from

Conversation

besser82
Copy link
Collaborator

The libxcrypt library in version >= 4 offers support for safely generating entropy itself. Besides that, the <crypt.h> header of the library already defines CRYPT_GENSALT_OUTPUT_SIZE.

@besser82 besser82 force-pushed the topic/besser82/libxcrypt_fixes branch 2 times, most recently from 128c516 to afb46d3 Compare February 26, 2020 19:48
@besser82 besser82 force-pushed the topic/besser82/libxcrypt_fixes branch from afb46d3 to 476e711 Compare February 27, 2020 10:33
@jreidinger
Copy link
Member

@besser82 thanks for your patch. I took us some time to check it as it is critical part and cryptography is always a bit scary. Also code is not so clear if we use libxcrypt or libowcrypt. So I check this and also pr to ruby-bindings. I found that we no longer use those builtins from core, so I will create pull request that will drop it and also its dependency, so faster building. Thanks for pointing us to this code.
In yast2-ruby-bindings situation is different and it is used in yast2-users. As target for master is opensuse TW and Leap 42.3, I will try if we can have this code without those ugly ifndefs to keep it simply enough. And luckily in ruby-bindings we already have rspec tests for those crypt builtins.

@jreidinger jreidinger mentioned this pull request Sep 24, 2020
@jreidinger
Copy link
Member

so replaced by #149

@jreidinger jreidinger closed this Sep 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants