On Tue, Nov 15, 2022 at 10:38 AM Mark Li <[email protected]> wrote: > I think you are missing "it". > The point of my email was to offer: > 1) working Postgres code for password hashing for Guac > 2) describe that Java tostring() function returns uppercase hex and the > analogous Postgres encode() function returns lowercase hex which needs to > converted to uppercase > 3) the documentation says, "If you are not using MySQL, or you are using a > version of MySQL that lacks the SHA2 function, you will need to calculate > the SHA-256 value manually (by using the sha256sum command, for example)." > The phrase "you will need", at least, to me indicates that "maybe" is not > an option to calculate the sha256 digest. > The statement might be clearer as: " If you are not using MySQL or you are > using a version of MySQL, that lacks the SHA2 function, you will need to > calculate the SHA-256 value manually (by using the sha256sum command, for > example)." > > Either way, Guacamole remains a great product.. >
Thanks. If you'd like to contribute to the documentation like Nick described, please open a pull request with your changes. The GitHub repository used to produce the documentation we include with each release is here: https://github.com/apache/guacamole-manual See our contribution guidelines: https://github.com/apache/guacamole-manual/blob/master/CONTRIBUTING Be advised that there is no guarantee that PostgreSQL will support the digest() function shown in your example - that's part of an optional module called "pgcrypto". If a PostgreSQL snippet demonstrating password assignment is to be included in the docs, it will need to take this into account. - Mike
