Ticket #61 (closed defect: wontfix)
include zcrypt in the zephyr client distribution
| Reported by: | geofft@… | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | never |
| Component: | zephyr.clients | Version: | |
| Keywords: | Cc: | ||
| Platform: |
Description
or come up with something better. Because enhancing my security by running some binary out of outland is dumb.
Change History
comment:1 follow-up: ↓ 2 Changed 3 years ago by kcr@…
- Status changed from new to closed
- Version 3.0 deleted
- Resolution set to wontfix
- Milestone set to grim darkness of the far future
comment:2 in reply to: ↑ 1 Changed 3 years ago by adehnert@…
Replying to kcr@…:
See #29 for something better on the roadmap.
My impression has generally been that at MIT, at least, zcrypt is used at least as much as an alternative to ACL'd classes as it is to prevent sniffing wire traffic. #29 doesn't sound like it solves the problem of ACL'd classes being (mostly politically, I think) hard to get.
Note: See
TracTickets for help on using
tickets.

See #29 for something better on the roadmap.
Including zcrypt would be tantamount to recommending it as "secure", and there just aren't enough scare quotes