| bio | website | shawnjgoff.com |
|---|---|---|
| location | Tampa, FL | |
| age | 32 | |
| visits | member for | 11 months |
| seen | Apr 15 at 16:19 | |
| stats | profile views | 0 |
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.
|
Jun 10 |
awarded | Scholar |
|
Jun 10 |
accepted | Okay to use OpenSSL to encrypt then sign a message? |
|
Jun 10 |
comment |
Okay to use OpenSSL to encrypt then sign a message? @owlstead Right - the dgst function has a -sign option to "digitally sign the digest" with a private key. I believe that does protect it against alteration. |
|
Jun 10 |
awarded | Editor |
|
Jun 10 |
revised |
Okay to use OpenSSL to encrypt then sign a message? added how the information will be used |
|
Jun 10 |
comment |
Okay to use OpenSSL to encrypt then sign a message? I'm going to follow those steps, but I think none of the issues matter in my case. I don't care who knows that the sender signed the message (unless that causes additional problems I don't know about), and the recipient does not trust the message unless it is from the trusted sender. |
|
Jun 10 |
awarded | Supporter |
|
Jun 10 |
awarded | Student |
|
Jun 10 |
awarded | Autobiographer |
|
Jun 10 |
asked | Okay to use OpenSSL to encrypt then sign a message? |