4.1 Security Considerations for Implementers

This algorithm does not have any security implications beyond those described in [RFC5751]. Furthermore, this algorithm treats S/MIME content as opaque binary data and does not deal with any sensitive material or data such as encryption keys. Although it is best for clients or servers that render, interpret, or compose S/MIME data to do so in a secure manner, that subject area is beyond the scope of this specification.