On Thu, Nov 06, 2003 at 09:19:23PM -0500, Derek Atkins was heard to remark: > Let me think about this and get back to you. At a first > approximation, the "user" should have some "user authentication
Yeah, OK, I know the concepts, I've seen them done in the kernel, I'll give it some thought. Might even rough in a few bits & peices. Not sure why I asked. Oh, here's why I asked: the big conceptual leap is that security presumes that there's a gnucash server, since I don't know of any way of enforcing security with a library (at least not in Unix). Now, there are some cheesey SQL hacks one could do to enforce security ... should I provision for those? If there's really a gnucash server, this raises that ugly question again of what's the client-server protocol. For which I used to have a clear answer, but now its dimmed a bit ... --linas -- pub 1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <[EMAIL PROTECTED]> PGP Key fingerprint = 8305 2521 6000 0B5E 8984 3F54 64A9 9A82 0104 5933 _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
