When the thread starts on the separate S/MIME policy update thread let me know, I work on a project that relies on S/MIME for transferring medical files and want to keep open the FOSS component of that. While that project has a strong server reference implementation, the private keys are held at the sever, which creates a MITM risk that is mitigated if the peer to peer is done correctly for end to end. _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy
- Re: Policy Update Propo... Kathleen Wilson
- Re: Policy Update Propo... Peter Kurrasch
- Re: Policy Update Propo... Gervase Markham
- Re: Policy Update Propo... Richard Wang
- Re: Policy Update Propo... Richard Barnes
- Re: Policy Update Propo... Gervase Markham
- Re: Policy Update Proposal: Remo... David E. Ross
- Re: Policy Update Proposal: Remo... Kathleen Wilson
- Re: Policy Update Proposal: Remove Code ... R Kent James
- Re: Policy Update Proposal: Remove Code Signing T... David E. Ross
- Policy Update Proposal: Remove Code Signing Trust... Peter Bachman
- Re: Policy Update Proposal: Remove Code Signing T... Kathleen Wilson
- Policy Update Proposal: Remove Code Signing Trust... [email protected]
- Re: Policy Update Proposal: Remove Code Sign... Brian Smith
- Re: Policy Update Proposal: Remove Code Sign... Matt Palmer
- Re: Policy Update Proposal: Remove Code Sign... Gervase Markham
- Fwd: Policy Update Proposal: Remove Code... Brian Smith
- Re: Policy Update Proposal: Remove C... Phillip Hallam-Baker
- Re: Fwd: Policy Update Proposal: Remove ... Joshua Cranmer 🐧
- Re: Fwd: Policy Update Proposal: Rem... Brian Smith
- Re: Fwd: Policy Update Proposal: Remove ... Wayne

