I'm using the approach with Config::IniFiles. A lot of people are "Windows-wise" and able to edit an ini-file, while directed over the phone.

Non-printable characters are represented bei some escapes like \n for a newline or \s for a blank in the right hand value. Even my most ... um ... inexperienced users have learned those escapes.

Since my *nix boxen live within an ADS-environment, I'm looking into something like Bundle::Net::LDAP for (mis-)using the existing ADS/LDAP as a general authentification/configuration-tool. I've no practical experience with that approach yet.

BTW, it's one of the goals evaluating a LDAP-based solution to restrict the ability for configuration to some users -- i.e. teamleaders -- who have also the rights to reset password, assign printers and such.