[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Monday, 17 December 2018 14:59:27 GMT Henry Bremridge wrote: > > Any ideas gratefully received You may need to specify a username and password in the LDAP bind, but you should be able to establish this using standard LDAP tools like ldapsearch https://linux.die.net/man/1/ldapsearch Afraid last place that used this was locked down so I extracted the keys we needed using the web interface of SEM, signed them and shared them with those who needed them (fail on so many levels but they didn't want them on public key servers). I did have a colleague with some experience of the product, happy to put him in touch, but guessing you probably don't have access to the admin interface to figure it out. Horrible product, and nearly all deployments I've saw made PGP worse by hiding details from the users. It has that ultimately failing of so much Enterprise software in that it tries to solve every possible configuration (of PGP email) an Enterprise may request, and in so doing allows them to request configurations that make no sense from a security perspective, but are fiendishly hard to understand, whilst adding a whole bunch of complexity. SEM is why Jonny still can't encrypt (unless he switches to WhatsApp). -- The Mailing List for the Devon & Cornwall LUG https://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq