Reply to thread

Message: [QUOTE="Twisted, post: 653502"] Hrm. "Sealed jar" just implies, to me, that the jar is rejected if it hasn't got a published md5sum or something, indicating that someone's changed, added, or removed something from the "official" version. Archive signing is a common security measure but not especially strong on its own, since it doesn't stop something not in the archive being bad, or badness that somehow got in before the signing. (Bugs; or the vendor of some classes is hostile.) Seems my proto-specification would be a bit more flexible than what you describe, since it dispenses with the artificial requirement to stuff everything into an archive, and does allow for extension *by authorized persons* in the future. [/QUOTE]