Tagged articles
nonce
19 articles · Page 1 of 1
This comprehensive guide answers 12 critical API security questions covering HMAC signatures, timestamp and nonce replay prevention, constant-time comparison against timing attacks, Redis SETNX atomic operations, appId/appSecret management, and key rotation strategies for robust API protection.
API SecurityHMACIdempotency
0 likes · 25 min read

This article explains why token authentication alone is insufficient for open APIs and details a three-layer defense using HMAC-SHA256 signatures, timestamps, and nonces to prevent tampering, long-term replay, and short-term replay attacks, with Java implementation examples.
API SecurityHMACRedis
0 likes · 25 min read

This article explains five practical solutions to prevent API replay attacks, including unique nonces with Redis storage, timestamp validation, combined signature-timestamp-nonce schemes, backend-issued one-time tokens, and business-level idempotency keys for critical operations like payments.
API SecurityIdempotencyRedis
0 likes · 6 min read

The article defines replay attacks, outlines high‑risk scenarios such as payment and coupon redemption, demonstrates two real‑world exploits, and presents four practical mitigation techniques—including unique transaction IDs, timestamp windows, one‑time nonces, and signature verification—to protect APIs.
API Securitynoncereplay attack
0 likes · 10 min read

Security researchers discovered that VECT ransomware unintentionally embeds the ChaCha20 key and nonce for files under 128 KB, allowing easy decryption, while its chunked encryption of larger files loses three of four nonces, rendering those files permanently unrecoverable even after ransom payment.
ChaCha20Malware AnalysisVECT
0 likes · 5 min read

This article presents a comprehensive guide to designing secure third‑party APIs, covering the generation and management of Access Key/Secret Key pairs, signature creation, timestamp and nonce anti‑replay techniques, token handling, request throttling, IP whitelisting, idempotency, versioning, response standards, and practical code examples in Java and SQL.
AK/SKAPI SecurityAuthentication
0 likes · 32 min read

This guide details a secure third‑party API design, covering API key generation, request signing with timestamps and nonces, permission division, CRUD endpoint definitions, unified response structures, and best‑practice security measures such as HTTPS, IP whitelisting, rate limiting, logging, and idempotency handling.
API SecurityAuthenticationBackend
0 likes · 29 min read

This article presents a comprehensive design scheme for third‑party API interfaces, covering access‑key/secret‑key generation, permission segmentation, signature flow and rules, anti‑replay mechanisms, token handling, and concrete Java code examples for secure request validation.
API SecurityAccess KeySecret Key
0 likes · 29 min read

The article presents a comprehensive design for third‑party APIs that protects against data tampering, replay attacks, and unauthorized access by using AK/SK key pairs, timestamp and nonce signatures, TLS encryption, fine‑grained permission models, rate limiting, idempotency handling, versioning, standardized response formats, and detailed implementation examples in Java.
AK/SKAPI SecurityREST API
0 likes · 32 min read

The article presents a comprehensive guide to designing secure third‑party APIs, covering access‑key/secret‑key generation, token management, signature algorithms, timestamp and nonce anti‑replay mechanisms, permission granularity, request logging, rate limiting, and example Java and SQL implementations.
Access KeySecret Keynonce
0 likes · 28 min read

This article explains how to protect microservice APIs from tampering and replay attacks by using HTTPS, request signing, nonce‑timestamp mechanisms, and AppId/AppSecret authentication, and demonstrates a complete Java/Spring implementation with a responsibility‑chain based verification filter.
API SecurityJavaSpring
0 likes · 14 min read


ITPUBJul 4, 2022 · Information Security
This article outlines ten practical methods for protecting API data, covering transmission encryption, digital signatures, token authentication, timestamp and nonce mechanisms, rate limiting, blacklist/whitelist controls, data masking, and parameter validation to ensure comprehensive interface security.
API Securitydata maskingdigital-signature
0 likes · 14 min read

The article explains replay attacks, describes how using a timestamp, a nonce, or a combination of both can protect API requests, and provides complete PHP code examples for signing and verifying requests to ensure each call is accepted only once.
PHPnoncereplay attack
0 likes · 7 min read

This article explains how timestamp and nonce mechanisms can be combined to protect API endpoints from parameter tampering and replay attacks, illustrating the approach with a Java Spring interceptor that stores nonces in Redis and validates signatures on each request.
API SecurityJavanonce
0 likes · 8 min read

This article explains the role of the txpool in Ethereum, details its configurable startup parameters, shows how to inspect pending and queued transactions, clarifies the nonce‑based placement of transactions, and offers practical tips for managing gas price and queue limits.
Ethereumgethnonce
0 likes · 7 min read

This guide explains why Ethereum transactions may remain unpicked, then shows how to cancel or replace them by manually managing the nonce and adjusting the txpool lifetime setting, including the required command‑line flags and default configuration values.
Ethereumnoncetransaction cancellation
0 likes · 4 min read

When a frequently used Ethereum account (hot account) sends multiple transactions, an incorrect nonce can cause the 'replacement transaction underpriced' error, but by understanding pending transactions, gas price requirements, and choosing either client‑managed or custom nonce strategies, developers can reliably prevent and resolve this issue.
Ethereumhot accountsnonce
0 likes · 5 min read

The article explains how Ethereum and Ethereum Classic handle transaction nonces via RPC interfaces, why incorrect nonces cause pending or queued transactions, and provides practical ways to obtain the correct nonce using eth_getTransactionCount to ensure reliable transaction submission.
EthereumRPCeth_getTransactionCount
0 likes · 5 min read

When sending Ethereum transactions via JSON‑RPC, a mismatched nonce can cause the transaction hash to appear while the transaction remains unconfirmed, staying in the queue indefinitely until the nonce order is corrected.
EthereumJSON-RPCnonce
0 likes · 4 min read
