While it's easy to think of cool uses, I *really* do not want to discuss support for arbitrary environment variables. To my mind, it brings up too many issues wrt security and performance, and thus it scares me off. Pardon my obtuseness, but given that we already support one type of variant link, how does generalizing the mechanism compromise security or performance? I might be opposed because of the complexity but I don't see the other issues. _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo.cgi/openafs-devel
- Re: [OpenAFS-devel] DRAFT: New sysname standard Ted McCabe
- Re: [OpenAFS-devel] DRAFT: New sysname standard Derek Atkins
- Re: [OpenAFS-devel] DRAFT: New sysname standard Garance A Drosihn
- Re: [OpenAFS-devel] DRAFT: New sysname standard Nathan Neulinger
- Re: [OpenAFS-devel] DRAFT: New sysname standard Todd M. Lewis
- Re: [OpenAFS-devel] DRAFT: New sysname standard eichin-oa
- Re: [OpenAFS-devel] DRAFT: New sysname standard Garance A Drosihn
- Re: [OpenAFS-devel] DRAFT: New sysname standard Jim Rees
- RE: [OpenAFS-devel] DRAFT: New sysname standard Neulinger, Nathan
- Re: [OpenAFS-devel] DRAFT: New sysname standard Jim Rees
- Re: [OpenAFS-devel] DRAFT: New sysname standard Jim Rees
- RE: [OpenAFS-devel] DRAFT: New sysname standard Neulinger, Nathan
- RE: [OpenAFS-devel] DRAFT: New sysname standard Ted McCabe
- Re: [OpenAFS-devel] DRAFT: New sysname standard Jim Rees
- Re: [OpenAFS-devel] DRAFT: New sysname standard Derek Atkins
- Re: [OpenAFS-devel] DRAFT: New sysname standard Ted McCabe
- Re: [OpenAFS-devel] DRAFT: New sysname standard Garance A Drosihn
- RE: [OpenAFS-devel] DRAFT: New sysname standard Garance A Drosihn
- RE: [OpenAFS-devel] DRAFT: New sysname standard Garance A Drosihn
- Re: [OpenAFS-devel] DRAFT: New sysname standard Jim Rees
