Deciphering General-Signing (0xDF) APDUs with ECDSA in DLMS Security Suite 1
-
Digital Signatures for Legal Non-Repudiation in Smart Meter Billing
Under European PTB / BSI TR-03109 regulations, billing measurements must be cryptographically signed by the meter's on-chip private key using
General-Signing(0xDF).Wire Format (APDU Tag 0xDF)
DF 08 47 55 52 55 58 31 32 33 00 00 00 1A 21 00 00 00 55 ... 30 44 02 20 ... 02 20 ...Field Breakdown
- Tag:
DF(general-signing) - System Title: 8 bytes (
47 55 52 55 58 31 32 33) - Signature Length:
00 00 00 1A - Security Control Byte:
21(Signed with Suite 1) - Transaction Counter: 4 bytes
- Signed Plaintext APDU: Includes meter serial, OBIS code, measurement value, and timestamp.
- ECDSA Signature (DER format): $R$ and $S$ integers (P-256 curve, 64-72 bytes).
Anyone (including consumers and third-party auditors) can verify the signature using the meter's publicly certified X.509 root key!
- Tag:
-
In firmware, we generate ECDSA signatures inside a dedicated hardware Secure Element (SE) with side-channel attack countermeasures (DPA/SPA resistance).
-
Our HES archives the signed 0xDF APDUs in immutable cold storage for 10 years to satisfy fiscal regulatory audit mandates.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login