To play devil's advocate, a lot of money that is tied up in retirement accounts of the "average Joe" would also be taxed, so if your retirement accounts aren't outpacing your income tax rate, then it'd hurt main street too
There is some interoperability with windows domains for bigger distros like RHEL and Ubuntu (there are even Ubuntu specific admx templates iirc). Check out SSSD
The most widely used operating systems in the world are based on unix/linux. Android (the most used OS in the world), MacOS, iOS, ESXi (as well as most hypervisors that aren't hyper-v) are all based on Linux/Unix. That's not even mentioning routers, switches, load balancers, and other high performance networking equipment. Other critical internet infrastructure (like root DNS servers) are all based on Unix or Unix-derivitives.
Just because it's not a widely used desktop OS doesn't mean that Linux/unix aren't relevant.
Not sure if you're being serious or not, but I've personally had very little issue with gaming on Linux. To the Unix/Linux folks, windows 11 feels like a trash heap of bugs and blue screen crashes that suck.
To be fair though: Desktop Linux isn't for everyone. Making generalized statements about Linux is silly when you aren't a Linux user. Feel free to keep doing it, though. And if this was bait: 10/10
I think TLA means "Three Letter Acronym" in some circles. So like, DBA would be a TLA meaning "database administrator" for example. Didn't read the article to get the context though, so not sure if it fits
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
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.
To play devil's advocate, a lot of money that is tied up in retirement accounts of the "average Joe" would also be taxed, so if your retirement accounts aren't outpacing your income tax rate, then it'd hurt main street too
Type 1 checking in
It's wild how quotable the Holy Grail is
UDP by itself has no state management, but some protocols will do state management at higher levels while using UDP as the transport
It's an old joke
There is some interoperability with windows domains for bigger distros like RHEL and Ubuntu (there are even Ubuntu specific admx templates iirc). Check out SSSD
We haven't been known for trains in a while, but America
You might also be able to see the information on IANA's website or ARIN's website
Hate to be that guy, but localhost is 127.0.0.1, not 172.0.0.1 (which is actually a public IP address)
Then vomit profusely and flop like a fish
I just looked online for 64GB of DDR5 and it was $900...
💀
The most widely used operating systems in the world are based on unix/linux. Android (the most used OS in the world), MacOS, iOS, ESXi (as well as most hypervisors that aren't hyper-v) are all based on Linux/Unix. That's not even mentioning routers, switches, load balancers, and other high performance networking equipment. Other critical internet infrastructure (like root DNS servers) are all based on Unix or Unix-derivitives.
Just because it's not a widely used desktop OS doesn't mean that Linux/unix aren't relevant.
Not sure if you're being serious or not, but I've personally had very little issue with gaming on Linux. To the Unix/Linux folks, windows 11 feels like a trash heap of bugs and blue screen crashes that suck.
To be fair though: Desktop Linux isn't for everyone. Making generalized statements about Linux is silly when you aren't a Linux user. Feel free to keep doing it, though. And if this was bait: 10/10
I work in I.T. on servers all day. I'm not always the best with endpoints/printers/home computers/etc.
The song is "Time" by Pink Floyd for anyone that doesn't get the reference. If you like that song, Dark Side of the Moon is definitely worth a listen
I think TLA means "Three Letter Acronym" in some circles. So like, DBA would be a TLA meaning "database administrator" for example. Didn't read the article to get the context though, so not sure if it fits
You forgot "hired by Joe Biden"
https://lemmy.world/c/the_pack
Drowsy Don...Sad!
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%7E%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