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

Advice of security point of view for doveadm and doveconf and sh usage #85

Open
osevan opened this issue Feb 22, 2025 · 2 comments
Open

Comments

@osevan
Copy link

osevan commented Feb 22, 2025

Last day I investigated php-fpm and especially postfixadmin strace file with some cool information behind the doors.

Postfixadmin needs for login inside database for password 3 additionally binarys - in my point of view too many -, because for php container hardening we MUST add these binarys as dependency inside high security container and these are security risks especially sh binary.

Can you figure out how to hash and dehash directly inside php universe itself without invoke sh, doveadm and doveconf?

I mean here exactly pure php solution clean one, without any additionaly binarys involved in this hashing and dehashing phase.

Thanks and

Best regards.

@DavidGoodwin
Copy link
Member

The dependency has been (almost) removed in the master branch of postfixadmin - https://github.com/postfixadmin/postfixadmin/blob/9620056277d09cf7a0e833f60dadc361208d4121/DOCUMENTS/HASHING.md

You don't have to use doveadm for your password hashing.

@osevan
Copy link
Author

osevan commented Feb 22, 2025

Thank you very much for info.
So php_crypt doesn't support argon2i natively I see.

Maybe in future.

Good luck

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

No branches or pull requests

2 participants