Ben Bucksch wrote: > It would make a lot more sense to me to show the type of "security" > (signed yes/no *and* encrypted yes/no) and the strength (algorithm, key > length) there. I must be missing something... Encryption means little without signing. Without signing, you could easily have a 128-bit encrypted conversation with an impersonator.
- Re: PSM 2.0 (PIP) docs now available Bob Lord
- Re: PSM 2.0 (PIP) docs now available John Gardiner Myers
- Re: PSM 2.0 (PIP) docs now available Ben Bucksch
- Re: PSM 2.0 (PIP) docs now available Nelson B. Bolyard
- Re: PSM 2.0 (PIP) docs now available Ben Bucksch
- Re: PSM 2.0 (PIP) docs now available Ben Bucksch
- Re: PSM 2.0 (PIP) docs now available Bob Lord
- Re: PSM 2.0 (PIP) docs now available Ben Bucksch
- Re: PSM 2.0 (PIP) docs now available John Gardiner Myers
- Re: PSM 2.0 (PIP) docs now available John Gardiner Myers
- Re: PSM 2.0 (PIP) docs now available Ben Bucksch
- Re: PSM 2.0 (PIP) docs now available John Gardiner Myers
- Re: PSM 2.0 (PIP) docs now available relyea
- Re: PSM 2.0 (PIP) docs now available Bob Lord
- Re: PSM 2.0 (PIP) docs now available Ben Bucksch
- Re: PSM 2.0 (PIP) docs now available Ben Bucksch
- Re: PSM 2.0 (PIP) docs now available relyea
- Re: PSM 2.0 (PIP) docs now available Ben Bucksch
- Re: PSM 2.0 (PIP) docs now available Nelson B. Bolyard
- Re: PSM 2.0 (PIP) docs now available Ben Bucksch
S/MIME Cryptographic Signature