Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons
Pierre THIERRY <[email protected]>
| Newsgroups | gmane.os.hurd.l4 |
|---|---|
| Message-ID | <[email protected]> |
Scribit Neal H. Walfield dies 15/01/2007 hora 18:48: > > One purpose of the constructor mechanism is to allow (e.g.) an > > instantiated password agent to have access to the password database > > when I do not. > ... and likely should not have. Yet, if the yield is running our of > client provided transparent storage, the client effectively has access > to the database. So, don't you want these types of services to run as > daemons? Wouldn't it be more vulnerable to DoS than confined processes instanciated on opaque storage provided by the client? Curiously, Pierre -- [email protected] OpenPGP 0xD9D50D8A _______________________________________________ L4-hurd mailing list [email protected] http://lists.gnu.org/mailman/listinfo/l4-hurd
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFq+GZxe13INnVDYoRAl9xAKD74sQRlaX89zt/t+NFNXhnt7lnHACfUmas wH+RhVwKxfWECBwk2eZq1kU= =NV6P -----END PGP SIGNATURE-----