4 ms·
...What are you trying to achieve? I mean, really, think about it. If you're just looking for their info against an AC'able backend, LDAP or a generic sql bac
by salawat 3y ago
...What are you trying to achieve?
I mean, really, think about it.
If you're just looking for their info against an AC'able backend, LDAP or a generic sql backend with the right tables.
The entire point of finger was to get the hardware to give you an idea of who/where the person was in the network.
Things like servers were not meant to only be used by orgs, they were meant to be used by people too.
- shortrounddev2 3y agoI'm LARPing
- OhMeadhbh 3y agoThat's a good point. But LDAP is usually administered by an organization. Most individuals don't have permission to edit their leaf records in the orgs I know that do LDAP. So... yeah... depends on what you're trying to achieve. If you want something org-focused and regular, LDAP is good. But if I wanted to publish my own info, maybe putting LDAP-ish records in a dotfile that some server serves out by mDNS would be a decent idea. Corporate guys who freak out over mDNS could just prevent it from traversing corporate owned switches. Everyone else would be on their own to figure out if individuals are leaking too much info.