

I think encrypting with a public key is mostly used in client -> server traffic (client encrypts with server’s public key, server decrypts with private), and not code signing. However, I’m no TLS/asymmetric crypto savant.
I think encrypting with a public key is mostly used in client -> server traffic (client encrypts with server’s public key, server decrypts with private), and not code signing. However, I’m no TLS/asymmetric crypto savant.
There are people that think this post is wrong because the equation is wrong or due to a lack of units
The equation for cylindrical volume is correct (circular area multipled by height).
And the units are unimportant (can be described as cubed units)
The issue is that Pi is a constant. Constants and variables are different things.
Other examples of constants: 1, 24, 7, -1 … Etc.
Saying Pi = 5 is like saying 1 = 5 … Both Pi and numbers like 1,2,3, etc. have a constant (non-varying) value.
You can’t reassign a value on a constant. It’s like me sticking up 3 fingers and claiming there are 5 fingers there.
This 100%. I liked bash scripting when I was in college. Took some time to actually learn powershell, and it’s been amazing. Steep learning curve in the beginning, but it’s worth it
Edit: I had also meant to mention the fact that powershell definitely feels a little similar to bash. I mean, not quite the same. Powershell is more object oriented, whereas bash is more text oriented. Powershell for structured data is nice.
I don’t have much experience in the realm of gpg. My experience is mostly with TLS. From what I know, if you’re doing client authentication, you encrypt your message with your private key, and then the public key on a cert is used for validating that the message actually came from you.
I think code signing is similar to client auth, but not positive. Again, I use TLS, but I’m not a professional
https://about.signpath.io/code-signing/theory#%3A~%3Atext=Software+publishers+use+a+secret%2Cpart+of+the+distribution+package.
Edit:
What I found from Wikipedia:
The client sends a CertificateVerify message, which is a signature over the previous handshake messages using the client’s certificate’s private key. This signature can be verified by using the client’s certificate’s public key. This lets the server know that the client has access to the private key of the certificate and thus owns the certificate.
https://en.m.wikipedia.org/wiki/Transport_Layer_Security#Client-authenticated_TLS_handshake