Ruby One V2
  • Ruby One V2 - Your Complete Ruby One Wallet Guide
  • General Introduction
    • Vision of Ruby One
    • What is Ruby One V2?
    • What is MPC technology?
    • Is MPC technology secure?
    • What are the benefits of MPC technology?
  • Why Use Ruby One
    • High-Security Wallet Access Through MPC
    • Contract Accounts for Secure and User-Friendly Blockchain Interaction
    • Third-Party DApp Integration with the Ruby DApp Bridge
    • Bridging the Web2-Web3 Gap
  • Tech Introduction
    • MPC-Secret Sharing
    • MPC-Threshold Signature Scheme
    • Social Recovery - DKIM
    • Contract Account Dynamic Upgrade
    • DApp Bridge
    • Ruby One V2 Upgrade Log
  • How to Use Ruby One V2
    • Launch App
    • Sign Up
    • Login Via Google
    • Login Via Email
    • Set Local Password
    • Backup Key Fragments
    • Three Test Networks
    • Send & Receive Crypto
    • Social Recovery Your Account
    • Sign Out & Clear Data
  • Term of Use
    • Welcome to Ruby Protocol
    • About the Website
    • Intellectual Property
    • Acceptable Use of the Website
    • Wallet Address, Private Key, and Backup Capabilities
    • Accuracy of Information Provided by User
    • Your Use of Ruby’s Services
    • Privacy Policies
    • Disclosure of Information
    • Changes and Availability
    • Contacting us via the Website
    • Age Restriction and Eligibility
    • Disclaimer of Warranty
    • Limitation of Liability
    • Changes to the Terms
    • Contact Us
  • Ruby One - MPC Wallet
Powered by GitBook
On this page
  1. Tech Introduction

Social Recovery - DKIM

DomainKeys Identified Mail (DKIM) is an email authentication method that allows the receiving mail server to check if the domain sent the email it claims to be sent from and if the content was tampered with during transit.

Here is how DKIM works:

  • The sender's mail server generates a unique hash value of the email content.

  • This hash value is then encrypted with a private key, which only the sender's server knows. The encrypted hash is also known as the DKIM signature and is inserted into the email header.

  • The receiving server gets the email and sees in the header that it has a DKIM signature.

  • The receiving server retrieves the corresponding public key from the sender's DNS records.

  • Using this public key, the receiving server decrypts the hash value.

  • The receiving server also generates its hash value of the received email content.

  • It then compares this value with the decrypted hash value. If they match, the email is authenticated, meaning that it did indeed come from the claimed domain and was not tampered with during transit.

DKIM is often used in combination with SPF (Sender Policy Framework) and DMARC (Domain-based Message Authentication, Reporting & Conformance) to provide robust protection against email spoofing and phishing. While SPF checks the sender's IP against a list of authorized IPs in the sender's DNS records, DMARC specifies what should be done if the SPF or DKIM checks fail.

In essence, DKIM validates a domain name identity associated with a message through cryptographic authentication.

PreviousMPC-Threshold Signature SchemeNextContract Account Dynamic Upgrade

Last updated 1 year ago