network profile
| bio | website | shawnjgoff.com |
|---|---|---|
| location | Tampa, FL | |
| age | 32 | |
| visits | member for | 4 months |
| seen | May 13 at 14:21 | |
| stats | profile views | 1 |
I've grown up with computers around me my whole life. I started programming when I was a kid, and stuck with it ever since. I came across Linux around 1999 and have enjoyed working with it ever since.
For a job, I get to write software that runs on embedded Linux devices. I do everything from working on low-level drivers to writing shell scripts and even web apps.
|
Apr 16 |
awarded | Student |
|
Mar 25 |
awarded | Scholar |
|
Mar 25 |
awarded | Supporter |
|
Mar 25 |
accepted | x509: must the signature algorithm and public key algorithm match? |
|
Mar 24 |
comment |
x509: must the signature algorithm and public key algorithm match? @mkl That's probably what's happening. The CA key is definitely RSA. The openssl output isn't very clear. |
|
Mar 24 |
comment |
x509: must the signature algorithm and public key algorithm match? I do not know. I got the request, imported it into XCA, signed it, exported the resulting cert in PEM format, inspected with openssl x509 and that's what it shows - a DSA key, but a signature algorithm that says RSA. |
|
Mar 24 |
awarded | Editor |
|
Mar 24 |
revised |
x509: must the signature algorithm and public key algorithm match? added 61 characters in body |
|
Mar 24 |
asked | x509: must the signature algorithm and public key algorithm match? |
|
Jan 11 |
awarded | Autobiographer |
