> sasl-regexp > uidNumber=([^,]*)\\+gidNumber=([^,]*),cn=peercred,cn=external,cn=auth > ldap:///ou=People,dc=example,dc=net??sub?(&(uidNumber=$1)(gidNumber=$2)) > > The problem? From the logs: > > gidNumber=0+uidNumber=0,cn=peercred,cn=external,[email protected]
This combines my hate for applications that provide inadequate tools for parsing tagged data (regexps are wonderful for many things, but this isn't one of them) with my hate for X.400. Thank you. However: > They reversed the order. They frigging reversed the order! Breaking > every documented technique for handling unix socket peer credentials. I'm confused, why would you expect the order of tagged elements in a list to remain constant?
