Cryptographic protocols

Hypertext Transfer Protocol Secure (HTTPS) is an extension of the Hypertext Transfer Protocol (HTTP). It uses encryption for secure communication over a computer network, and is widely used on the Internet. In HTTPS, the communication protocol is encrypted using Transport Layer Security (TLS) or, formerly, Secure Sockets Layer (SSL). The protocol is therefore also referred to as HTTP over TLS, or HTTP over SSL.

cryptosystem that uses both public and private keys

cryptographic protocols for securing data in transit

In computing, Internet Protocol Security (IPsec) is a secure network protocol suite that authenticates and encrypts packets of data to provide secure encrypted communication between two computers over an Internet Protocol network. It is used in virtual private networks (VPNs).

security protocol to secure wireless computer networks

deprecated security algorithm for wireless networks

In cryptography, X.509 is an International Telecommunication Union (ITU) standard defining the format of public key certificates. X.509 certificates are used in many Internet protocols, including TLS/SSL, which is the basis for HTTPS, the secure protocol for browsing the web. They are also used in offline applications, like electronic signatures.

protocol that performs a security-related function

technique for anonymous communication

network protocol and program for copying files between computers

email authentication method designed to detect email spoofing

standard for certified Wi-Fi products designed to ease the setup of Wi-Fi networks in home and small office environments

part of the IPsec protocol suite for securing IP communications

a stopgap security protocol used in the IEEE 802.11 wireless networking standard; was deprecated in the 2012 revision of the 802.11 standard

non-federated cryptographic protocol

communications protocol

framework for authentication and data security in Internet protocols

Encryption protocol for Wireless LAN

cryptographic protocol for instant messaging providing forward secrecy and malleable encryption using 128-bit AES, 1536-bit Diffie–Hellman, and SHA-1

Nostr (acronym for Notes and Other Stuff Transmitted by Relays) is an open protocol for decentralized message transmission, with the intention to be able to resist internet censorship while maintaining session integrity. "Noster" can also be translated as "our" or "ours" from Latin. The protocol achieves decentralization through users publishing content associated with a cryptographic public key to various "relays", which are WebSocket servers that store and distribute an activity stream of received data from users. This allows the network to verify users and achieve account portability on Nos

IEEE standard version

communications protocol; lets datagram-based applications communicate in a way designed to prevent eavesdropping, tampering, or message forgery

Hashcash is a proof-of-work system used to limit email spam and denial-of-service attacks. Hashcash was proposed in 1997 by Adam Back and described more formally in Back's 2002 paper "Hashcash – A Denial of Service Counter-Measure". In Hashcash the client has to concatenate a random number with a string several times and hash this new string. It then has to do so over and over until a hash beginning with a certain number of zeros is found.

cryptographic protocol enabling the sharing of a secret key over an insecure channel

subfield of cryptography

routing protocol

security profile for Real-time Transport Protocol

Internet protocol

encryption technology

thumb|Logo of OMEMO OMEMO is an extension to the Extensible Messaging and Presence Protocol (XMPP) for multi-client end-to-end encryption developed by Andreas Straub. According to Straub, OMEMO uses the Double Ratchet Algorithm "to provide multi-end to multi-end encryption, allowing messages to be synchronized securely across multiple clients, even if some of them are offline". The name "OMEMO" is a recursive acronym for "OMEMO Multi-End Message and Object Encryption". It is an open standard based on the Double Ratchet Algorithm and the Personal Eventing Protocol (PEP, XEP-0163). OMEMO offers

method of negotiating credentials between web server and browser

family of file formats associated with RFC 1421

cryptographic standard

web encryption method similar to HTTPS

ZRTP (composed of Z and Real-time Transport Protocol) is a cryptographic key-agreement protocol to negotiate the keys for encryption between two end points in a Voice over IP (VoIP) phone telephony call based on the Real-time Transport Protocol. It uses Diffie–Hellman key exchange and the Secure Real-time Transport Protocol (SRTP) for encryption. ZRTP was developed by Phil Zimmermann, with help from Bryce Wilcox-O'Hearn, Colin Plumb, Jon Callas and Alan Johnston and was submitted to the Internet Engineering Task Force (IETF) by Zimmermann, Callas and Johnston on March 5, 2006, and published on

Ecash was conceived by David Chaum as an anonymous cryptographic electronic money or electronic cash system in 1982. It was realized through his corporation Digicash and used as micropayment system at one US bank from 1995 to 1998.

computer network protocol

AS2 (Applicability Statement 2) is a specification on how to transport structured business-to-business data securely and reliably over the Internet. Security is achieved by using digital certificates and encryption.

Chinese National Standard for Wireless LANs

Multimedia Internet KEYing (MIKEY) is a key management protocol that is intended for use with real-time applications. It can specifically be used to set up encryption keys for multimedia sessions that are secured using SRTP, the security protocol commonly used for securing real-time communications such as VoIP.

IPv6 network protocol extension

WAP security protocol

Internet protocol for obtaining X.509 digital certificates in a public key infrastructure

XML Key Management Specification (XKMS) uses the web services framework to make it easier for developers to secure inter-application communication using public key infrastructure (PKI). XML Key Management Specification is a protocol developed by W3C which describes the distribution and registration of public keys. Services can access an XKMS compliant server in order to receive updated key information for encryption and authentication.

data serialization format

in cryptography, a public key cryptosystem