https://github.com/lldap/lldap logo
petrosmm - hello, ldapsearch -x -y password.tx...
# troubleshooting
n
Hello! LLDAP stores passwords as a zero-knowledge proof, so they're neither importable nor exportable
p
if i added an attribute using cli, would that attribute be editable from the web interface or only via DB?
n
The web interface is almost there for custom attributes
For now, lldap-cli is the recommended way
p
🙂 i know you're not going to do it for probably already talked about reasons but i think having an env option to expose encrypted password as an attribute... LLDAP is popular choice because all other LDAPS are so ardous to setup/debug/configure, it's killer and people want something intuitive simple/beautiful
thank you for your service!
n
It's both a security choice (don't want to expose the password for other services to leak), and a purely practical choice: we depend on a specific version of a specific implementation of the OPAQUE algorithm, that is simply not supported in other services
So even if we exposed it, it would be useless
p
ahhh okay that makes sense
yes then that means for example freeradius wouldnt be able to decrpyt it if it doesnt have OPAQUE
ok well, custom attributes in web will have to do
and thank you for getting back, love this thing!
n
I'm glad you do!