Encrypted communication can be accomplished using Bitcoin Public Keys. Verifying the authenticity and integrity of files can be accomplished by having a designated Bitcoin Public Address to serve as your public identity for signing messages. By including the file name and file hash within a signed message from a particular identity, the risk of a compromised website is largely mitigated as any potential tampering of a message (or file within it) would be apparent to all as it would break the digital signature/fingerprint.
To be clear, I am not advocating for the use of actual public addresses (or public keys) that have ever been used in bitcoin transactions as there are many problems (privacy and other) with this which have been pointed out over the years. What am I missing?
We are cloud-only using Azure AD with Azure AD Domain Services deployed, so Active Directory Certificate Services doesn't seem like the right fit. Cloudfare’s CFSSL open source project is interesting too. I'm curious what others are using for internal PKI.
Phone scams (eg. IRS scam,Microsoft tech suppport scam etc.) and spam calls have gone from nuisance to a serious issue. A solution might be to create a PKI that your phone app validates against to check that this is indeed who they claim they are.
tl;dr: Essentially "certificates" that are used for online SSL transactions, but for phone calls.
This way I can block anyone who's not registered there (and not in my contacts)