Source-linked AI summary
BARS: a Blockchain-based Anonymous Reputation System for Trust Management in VANETs
Zhaojun Lu, Qian Wang, Gang Qu, Zhenglin Liu
TL;DR
VANETs need to prevent authenticated vehicles from spreading forged messages while preserving privacy against tracking. BARS uses blockchain-based anonymous authentication and reputation management, and the reported evaluation finds improved message trustworthiness and protected vehicle privacy with high efficiency.
Problem
VANETs still face trust and privacy issues, including forged messages from authenticated vehicles and tracking of vehicles or drivers.
Method
BARS combines blockchain-based anonymous PKI authentication, two certificate and revocation blockchains, and reputation evaluation using message authenticity and vehicle opinions.
Results
BARS establishes distributed trust management, improves the trustworthiness of broadcast messages, and protects vehicle privacy with high efficiency.
Takeaways & Limitations
Public keys serve as anonymous pseudonyms while blockchain records support authentication, persistent message evidence, and reputation assessment.
Abstract
from arXiv · showhide
The public key infrastructure (PKI) based authentication protocol provides the basic security services for vehicular ad-hoc networks (VANETs). However, trust and privacy are still open issues due to the unique characteristics of vehicles. It is crucial for VANETs to prevent internal vehicles from broadcasting forged messages while simultaneously protecting the privacy of each vehicle against tracking attacks. In this paper, we propose a blockchain-based anonymous reputation system (BARS) to break the linkability between real identities and public keys to preserve privacy. The certificate and revocation transparency is implemented efficiently using two blockchains. We design a trust model to improve the trustworthiness of messages relying on the reputation of the sender based on both direct historical interactions and indirect opinions about the sender. Experiments are conducted to evaluate BARS in terms of security and performance and the results show that BARS is able to establish distributed trust management, while protecting the privacy of vehicles.
I. INTRODUCTION
VANETs need trust management and privacy protection because authenticated vehicles can distribute forged messages and be tracked. BARS combines blockchain-based anonymous authentication with reputation management to address both issues.
- Motivation: VANETs remain vulnerable to forged messages from authenticated vehicles and tracking of vehicles or drivers.These threats can reduce transportation efficiency, cause accidents, and expose driving behavior.
- Requirements: Effective VANET trust models should evaluate messages using direct historical interactions and indirect opinions while supporting efficiency, privacy, and robustness.The model should work in congested and sparse situations without revealing senders’ real identities or being disabled by attacks.
- Design challenge: Blockchain provides immutable, publicly verifiable records but its transparency can make actions associated with a public key traceable to a real identity.BARS must therefore combine blockchain’s auditability with privacy protection.
- BARS: BARS establishes distributed trust management while protecting vehicle privacy through blockchain-based anonymous reputation and authentication.The system extends PKI so public keys can serve as authenticated pseudonyms without remaining linkable to real identities.
- BARS: BARS evaluates vehicle trustworthiness from message authenticity and other vehicles’ opinions, recording messages as persistent evidence for reputation assessment.The reputation score is intended to incentivize vehicles to prevent misbehavior and mitigate forged-message distribution.
II. TRUST MODELS IN VANETS
Prior VANET trust models are organized around entities, data, or both. The surveyed approaches use reputation, neighbor opinions, and other evidence to assess trustworthiness.
- Overview: State-of-the-art VANET trust models are classified as entity-centric, data-centric, or combined, but none meets all desirable requirements.The classification is presented as a comparison of recent trust models.
- Entity-centric Trust Models: Entity-centric models evaluate vehicle trustworthiness using reputation systems or neighbors’ opinions.Examples include multifaceted trust incorporating role, experience, priority, and majority information for real-time decisions.
- Data-centric Trust Models: Data-centric models evaluate received-data trustworthiness using cooperative information from neighbor vehicles or roadside units.Reported approaches use content similarity, conflict, route similarity, voting weights, signal strength, geolocation, or social trust.
C. Combined Trust Models
Combined trust models assess both vehicles and data, inheriting benefits and drawbacks from entity-centric and data-centric approaches. The paper then introduces blockchain foundations and certificate transparency for BARS.
- C. Combined Trust Models: Combined trust models evaluate vehicle trust and data trust together.They inherit the benefits and drawbacks of both entity-centric and data-centric models.
- C. Combined Trust Models: ART resists malicious attacks by evaluating data from multiple vehicles and determining node trust from functional and recommendation trust.The cited scheme combines data-level evidence with node-level trust factors.
- Background: The paper introduces blockchain operation, conventional PKI problems, certificate transparency, BARS components, and necessary assumptions before presenting the system.This background frames the later anonymous-authentication and reputation mechanisms.
- A. Blockchain: Blockchain is a cryptographically enforced distributed ledger carried out collectively in a peer-to-peer network.The paper presents it as decentralized infrastructure for storing, tracking, monitoring, managing, and sharing data.
- B. Certificate Transparency: Certificate transparency maintains a public append-only log of issued certificates and supports proofs of certificate inclusion and append-only extension.Auditors can verify that a certificate is present and that one log snapshot extends another.
C. Components of BARS
BARS uses CA and LEA roles alongside separate blockchains for certificates, revoked keys, and messages. Vehicles verify blockchain records and monitor one another for misbehavior.
- Authorities: CA issues and revokes certificates only with LEA authorization, while recording its actions transparently on the blockchain.Every VANET entity can verify these recorded actions.
- Authorities: LEA registers and monitors vehicles, evaluates reputation scores, authorizes certificate operations, and securely stores public-key–identity correlations.This preserves a controlled capability to correlate pseudonyms with real identities.
- Certificate: BARS certificates contain a public key, expiration date, and reputation score but omit the vehicle’s real identity.The certificate design supports privacy-preserving vehicle authentication.
- Blockchains: CerBC records issued certificates and provides proof of presence, while RevBC records revoked public keys and provides proof of absence.The two ledgers support certificate and revocation checks during authentication.
- Blockchains: MesBC records all broadcast messages as persistent evidence for disputes and reputation evaluation.This ledger supports later assessment of vehicle behavior.
- Network roles: RSUs provide proof-of-work consensus, with BARS security guaranteed under the assumption that more than half of RSUs are uncompromised.Vehicles verify blockchain records and monitor one another to detect misbehavior and forged messages.
D. Assumptions
BARS assumes secure PKI communication, protected identity-correlation records, and blockchain security against control of more than half the RSUs.
- PKI provides secure communication between entities as long as secret keys remain uncompromised.
- LEA is assumed to protect the dataset linking vehicles’ public keys with their real identities using sufficient security levels.
- Blockchain security requires adversaries to be unable to compromise more than half of the RSUs.This condition is identified as a prerequisite for securing the blockchain itself.
- Anonymous authentication is supported by CA and LEA functions covering system initialization, certificate update, and public-key revocation.
- During enrollment, LEA validates legal-identity materials and sends a signed warrant to CA, which issues the vehicle’s initial certificate.
- LEA alone retains submitted private information in a high-security database for tracking a vehicle’s real identity during disputes.
B. Certificate Update
BARS updates certificates when they expire, private keys are threatened, or vehicles seek new public keys, while preserving privacy through separated roles and blockchain records.
- Certificates are updated before expiration, after private-key threats, or when vehicles replace public keys for privacy consideration.The new certificate updates the public key, reputation score, and expiration date.
- Vehicle A generates a new public-key and private-key pair for certificate updating.
- The encrypted update request includes current and updated public keys, real-identity proofs, and a signature using the current private key.
- After verification, LEA sends CA a signed warrant without revealing the link between the current and updated public keys to CA.
- CA issues an updated certificate containing the new public key, reputation score, and expiration time, then records it in CerBC.
- Public-key revocation instructions contain the revoked key and revocation time, after which CA broadcasts signed revocation messages.
- RSUs verify revocation messages, delete expired keys, and insert revoked keys lexicographically into RevBC’s Merkle tree for efficient absence proofs.
D. Authentication Process
Authentication checks certificate validity against separate certificate and revocation blockchains, using Merkle proofs of presence and absence to validate an unrevoked public key.
- A receiver accepts a certificate only after checking that it is unexpired, present in CerBC, and absent from RevBC.
- The presence proof reconstructs CerBC’s recorded root hash from direction and hash tuples; equality validates the certificate and associated public key.
- The absence proof uses adjacent revoked public keys and lexicographic ordering to show that the sender’s public key is not revoked.
- BARS uses vehicle reputation scores to determine the trust level of broadcast messages while protecting vehicle privacy.
A. Different Types of Messages
BARS distinguishes beacon, alert, and disclosure messages, and evaluates sender reputation through rewards for honest behavior and penalties for misbehavior or abusive reporting.
- Beacon messages periodically report driving status, alert messages report emergencies, and disclosure messages report disputed authenticity or misbehavior to LEA.
- Alert-message levels: Level 1 alerts automatically warn of loss of vehicle control to help avoid collisions.
- Alert-message levels: Level 2 alerts forewarn nearby vehicles before braking, lane changes, or other driving-status changes.
- Alert-message levels: Level 3 alerts warn following vehicles about poor road conditions such as obstructions or road damage.
- Reputation evaluation: The reputation algorithm rewards honest, active alert broadcasting and disclosure of witnessed misbehavior or forged messages.
- Reputation evaluation: Reputation evaluation factors include alert level L, relative vehicle density Dr, and sender sequence S.The paper sets average density Daver to 20 vehicles per Km and assigns the first alert sender S = 0.
- Reputation evaluation: Reward and penalty coefficients α and β implement the reward and punishment mechanisms.
- Reputation evaluation: Forged alert messages receive heavy punishment, while vehicles abusing disclosure messages to slander others are also penalized and published.
VI. RESULTS AND ANALYSIS
Blockchain is presented as satisfying the security requirement of certificates. In this design, certificate security is tied to blockchain-based recordkeeping.
- Blockchain satisfies the security requirement of certificates.
- Certificate security is implemented through the blockchain.
- The certificate system relies on blockchain technology to meet its security requirement.
1) Security of Certificates:
BARS uses blockchain records and pseudonymous public keys to support certificate security while preserving vehicle privacy. Its reputation evaluation also reflects different vehicle behaviors over time.
- Security of Certificates: RSUs verify CA and LEA signatures and record certificate issuance or revocation messages in CerBC and RevBC.
- Security of Certificates: Proofs of presence in CerBC and absence in RevBC authenticate a vehicle’s public key, while MesBC stores broadcast messages as dispute evidence.
- Security of Certificates: Using a public key as a pseudonym breaks its linkability with the vehicle’s real identity, while LEA retains the identity–key pairs for disputes.
- Security of Certificates: Vehicle A and B gain reputation by broadcasting authentic messages, whereas forged or slanderous disclosures reduce vehicle B’s score.
1) Storage & Transmission Overhead:
BARS uses logarithmic authentication proofs and evaluates storage and transmission overhead for anonymous authentication. The reported overhead is described as acceptable, including for large-scale networks.
- Storage & Transmission Overhead: 0.177 M/s is the reported total transmission overhead when i = 100, j = i * 10%, n = 1 000 000, and m = n * 10%.The paper describes the storage and transmission overhead of anonymous authentication as acceptable.
- Storage & Transmission Overhead: Authentication proofs based on SHA-256 require time and space O(logn), supporting efficient authentication in large-scale VANETs.
- Storage & Transmission Overhead: BARS uses CerBC and RevBC proofs of presence and absence for authentication, while MesBC records broadcast messages for reputation evaluation.