I have to following cert that I am building for our DRIP work:
-----BEGIN CERTIFICATE-----
MIH9MIGwoAMCAQICAghxMAUGAytlcDAsMSowKAYDVQQDDCEyMDAxMDAzMDAwMDAw
MDA1MGVkYThhNjQ0MDkzYWFkZEkwHhcNMjQwOTAyMTY1NDM5WhcNMjQxMDAzMTY1
NDM5WjAAMCowBQYDK2VwAyEAKizr+94BfDjE/Xb1yGotBzs8qE9JFpMM4rjzm52/
j22jIjAgMB4GA1UdEQEB/wQUMBKHECABAD/+P/gFcCAiN/ucXUwwBQYDK2VwA0EA
FRUk+4nVBZ4aQGM+Z+OcMm1htt9dwUhBk9m1L1TZSJ2H34fKvkTtnRTg5VWhldpB
pEQmR24en/FyD0pOVnGnCg==
-----END CERTIFICATE-----
which dumps as:
$ openssl x509 -noout -text -in UA1.pem
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 2161 (0x871)
Signature Algorithm: ED25519
Issuer: CN = 20010030000000050eda8a644093aaddI
Validity
Not Before: Sep 2 16:54:39 2024 GMT
Not After : Oct 3 16:54:39 2024 GMT
Subject:
Subject Public Key Info:
Public Key Algorithm: ED25519
ED25519 Public-Key:
pub:
2a:2c:eb:fb:de:01:7c:38:c4:fd:76:f5:c8:6a:2d:
07:3b:3c:a8:4f:49:16:93:0c:e2:b8:f3:9b:9d:bf:
8f:6d
X509v3 extensions:
X509v3 Subject Alternative Name: critical
IP Address:2001:3F:FE3F:F805:7020:2237:FB9C:5D4C
Signature Algorithm: ED25519
Signature Value:
15:15:24:fb:89:d5:05:9e:1a:40:63:3e:67:e3:9c:32:6d:61:
b6:df:5d:c1:48:41:93:d9:b5:2f:54:d9:48:9d:87:df:87:ca:
be:44:ed:9d:14:e0:e5:55:a1:95:da:41:a4:44:26:47:6e:1e:
9f:f1:72:0f:4a:4e:56:71:a7:0a
First there were warnings on the RUST build (on Fedora):
warning: use of deprecated method `chrono::TimeZone::timestamp`: use
`timestamp_opt()` instead
--> src/main.rs:2155:40
|
2155 | ... let ts = chrono::TimeZone::timestamp(&chrono::Utc, *val as
i64, 0);
| ^^^^^^^^^
|
= note: `#[warn(deprecated)]` on by default
warning: use of deprecated method `chrono::NaiveDateTime::timestamp`:
use `.and_utc().timestamp()` instead
--> src/main.rs:546:116
|
546 | ...g, "%Y%m%d%H%M%SZ").unwrap().timestamp() as u64);
| ^^^^^^^^^
warning: `c509` (bin "c509") generated 2 warnings
Finished `dev` profile [unoptimized + debuginfo] target(s) in 2m 37s
------------------------
Then I ran
$ ./target/debug/c509 f
/home/rgm/data/htt/Projects/Critical/drafts/draft-ietf-drip-rid/UA1.pem
[2024-09-04T13:53:51Z INFO c509] Logger initialized!
thread 'main' panicked at src/main.rs:3872:9:
Unexpected type! Expected 30 but got 2d
stack backtrace:
0: rust_begin_unwind
at
/builddir/build/BUILD/rustc-1.78.0-src/library/std/src/panicking.rs:645:5
1: core::panicking::panic_fmt
at
/builddir/build/BUILD/rustc-1.78.0-src/library/core/src/panicking.rs:72:14
2: c509::lder::lder
at ./src/main.rs:3872:9
3: c509::lder::lder_vec
at ./src/main.rs:3889:24
4: c509::lder::lder_vec_len
at ./src/main.rs:3899:19
5: c509::parse_x509_cert
at ./src/main.rs:296:23
6: c509::main
at ./src/main.rs:166:21
7: core::ops::function::FnOnce::call_once
at
/builddir/build/BUILD/rustc-1.78.0-src/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
Help?
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]
