Finaldata Enterprise 3.0 Serial 104
We hope that we have a second line of defense for SHA-1: after the MD5 Collisions Inc demo, CAs were required to use random serial numbers. A chosen-prefix attack requires being able to predict the certificate contents that will be signed and the random serial number should thwart that. With random serials we should be resting on a stronger hash function property called target-collision resistance. (Although I'm not aware of any proofs that random serials actually put us on TCR.)
finaldata enterprise 3.0 serial 104
I've been looking through the documentation for something like the new Ceph enterprise release and I have to wonder if the product was designed under a power outage, or a power overflow. I know I'd be panicking a bit less if I just knew when I'd be restarting the service.
The goal of this particular implementation is to end users with an MP-Lab-X environment that is essentially identical to the serial, in terms of key and functionality, to what the serial is expected to provide. To this end, I have not attempted to "fix" a known bug in the serial to support software keys.
Looking at the current stage of the CS for IoT program, some of the things I'd love to be able to do for that are: Identify impact to privacy and security of customer systems from insecure credentials and services. I could deal with this all day long, but I'm not quite sure yet where to start.
Integrate with existing infrastructure to reduce cost. Our "enterprise" markets tend to be large and have lots of maturity in enterprise IT, which means we often have perfectly good, secure systems already in place