docker-openldap VS pass-import

I'm entirely unfamiliar with overlays. I don't believe I've configured any on my OpenLDAP server, as it is just a default docker image I've populated with some OUs and users.

I'm trying to integrate LDAP into my small homelab but I'm extreme noobie in it. So far I've tried: 1. OpenLDAP - not so resource heavy but I found it difficult go get working correctly with NextCloud, Keycloak and Jellyfin. Maybe someone could recommend an easy to follow guide? 2. LLDAP - honestly it's almost prefect. Nice clean UI, great guides how to setup with everything I need, but it's a read-only LDAP, so I cannot create or manage users with Keycloak or NC, that's about the only downside and probably bugs me more than it should. 3. 389ds - has everything I need (and probably some more), super easy to setup with this guide but the elephant in the room is that it uses 700MiB of RAM (whereas LLDAP uses only 7-8MiB). That's a big difference which really makes me question whether I want to use this particular solution.

I have been struggling for a week to get sudo to work with my LDAP setup. I am using this docker setup. I have added these attributes to my server.

Hi, I've used the osixia github repository to spin up a docker container act as a LDAP Slave and I've successfully used the custom configuration and spin up the container. When i checked the logs of the container i saw the following as the output when it tries to sync with the Master.

It is quite straightforward to stand up an LDAP server listening in plaintext. My favorite mechanism is using the openldap container, although there are other options.

I'm trying to setup a LDAP server using the Osixia Docker container through docker-compose. I want it to contain lists of PosixAccount and PosixGroups, and use them to grant access to some external applications which also have a simpleSecurityObject entry in the directory (e.g. Grafana, which I already integrated with another LDAP server).

I've been trying to setup an openldap server from https://github.com/osixia/docker-openldap

I've grown quite tired of how painful it is to manage my LDAP server with multi-master replication. Currently I'm running osixia/openldap, with a wheelybird/ldap-user-manager frontend to manage users, all hosted on my Kubernetes cluster. Eventually, I'm looking to migrate to nitnelave/lldap

> I always tell these people to just sign up for a password manager and they always resist and say no. I must be missing something obvious.

Maybe they don't want to be relying on a random third-party for all their passwords?

Rather than getting them to sign up for a password manager, what about getting them to install a password manager? I use https://www.passwordstore.org/ - it encrypts your passwords with GPG, and shares the storage via a Git repository for synchronisation between different machines.

That way you can delegate the password handling to another program, e.g. a password manager like pass(1) (https://www.passwordstore.org/) or some interactive graphical prompt.

I want to move to something compatible with https://www.passwordstore.org/ - an open standard for keeping your passwords in a folder encrypted with OpenPGP.

The problem is that I'm nervous to give an unknown Android app and browser plugin total control of my passwords and access to my github account when I don't have time to review it's code properly. I have a bit more trust ing the command line tools, but I'd like to be sure that more people are looking at the code before I trust my life to it.

> Create a system or pattern based on url or brand and mentally hash it into a password.

Doesn't sound very secure. Also when you realize that you anyway have to trust cryptography, I believe it starts making a lot of sense to have an actual cryptographic key and encrypt it with one good random password you learn by heart.

I use pass https://www.passwordstore.org/, which encrypts my passwords with my GPG key, which comes from my Yubikey, which I unlock with a password. That means that I only need to remember one password, and it feels a lot more secure than your pattern based on url or brand.

i use pass and keep my database on a local git repo. it encrypts your passwords with gpg and is a really simple command line program

If you want portability and simplicity, there's a project called simply pass that uses standard *nix utilities (and git, I believe) to manage passwords from CLI.

0. Pass is just text files encrypted with gpg. I needed just one password on one work computer, where I had my gpg key, but not all my passwords. Decrypted the file and that was it.

1. There are plugins and web clients: https://www.passwordstore.org/#extensions

I've been incredibly happy with https://www.passwordstore.org/ for years. The data store is a file hierarchy, with the files themselves encrypted with GPG. Sync is via git. TOTP support with a plugin.