NDN...UMP(1)

πŸ“¦
version 0.9.0 Β· 2 versions
, in nixos 26.05

🌈 NDN...UMP(1) 🌈

okay bestie, this is the NDN...UMP(1) page from ndn-cxx: the NDN C++ library with eXperimental eXtensions πŸ’…βœ¨ We're talking about ndnsec-cert-dump, and it's lowkey iconic.

✨ NAME ✨

ndnsec-cert-dump β€” export an NDN certificate πŸ’–

πŸ¦‹ SYNOPSIS πŸ¦‹

ndnsec cert-dump [-h] [-p] [-r [-H host] [-P port]] [-i|-k|-f] name
btw, the synopsis also has -h, -r, -H host, and -P port. The OPTIONS section below only gives its own little writeups to the four flags after it, so I'm not inventing extra lore, iykyk. 🫢

🌸 DESCRIPTION 🌸

This command reads an NDN certificate β€” either from the Public Information Base (PIB) or from the specified file β€” and prints it on the standard output. It can print it either in Base64 encoding or in a human-readable format. No cap. πŸ’–

By default, name is interpreted as a certificate name. That's the default vibe, periodt. ✨

πŸ’… OPTIONS πŸ’…

  • -i, --identity β€” interpret name as an identity name. If you use this, the certificate to dump is the default certificate of the identity. πŸ’–
  • -k, --key β€” interpret name as a key name. If you use this, the certificate to dump is the default certificate of the key. πŸ”‘
  • -f, --file β€” interpret name as a path to a file containing the certificate. If name is "-", the certificate will be read from the standard input. πŸŽ€
  • -p, --pretty β€” print the certificate in a human-readable format. It's giving readable, bestie. ✨

πŸ”₯ EXAMPLES πŸ”₯

Okay so example one: export a certificate from the local PIB to the standard output with Base64 encoding, and it goes like this:

$ ndnsec cert-dump /ndn/test/david/KEY/%7FE%1C%18%D2%03%BD%3F/self/v=1719080300644
Bv0BOAcxCANuZG4IBHRlc3QIBWRhdmlkCANLRVkICH9FHBjSA70/CARzZWxmNggA
AAGQQSuwZBQJGAECGQQANu6AFVswWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAAQ8
7QbdgubF3IznydpZ8PuppHgVRufGsUMDvHpS8Rw93rAAsw+8aVcNmw94wzpALWzD
3femcs+qHaWoIOBOn26SFlIbAQMcIwchCANuZG4IBHRlc3QIBWRhdmlkCANLRVkI
CH9FHBjSA70//QD9Jv0A/g8yMDI0MDYyMlQxODE4MjD9AP8PMjA0NDA2MTdUMTgx
ODIwF0cwRQIhAPqG+GtIQlbcgB9ZFAGCKcO7DBMK+K3RinEAbzqKpFTcAiAp+D8L
z/S6nPNtSTGBBxr4cdUecjIHxKN6DoP3K1o2yg==

And here's printing the NDN testbed root certificate in human-readable format β€” the -fp - combo is doing its thing:

$ curl -A ndnsec -fsLS https://named-data.net/ndnsec/ndn-testbed-root.ndncert.x3.base64 | ndnsec cert-dump -fp -
Certificate Name:
  /ndn/KEY/%EC%F1L%8EQ%23%15%E0/ndn/%FD%00%00%01u%E6%7F2%10
Additional Description:
  fullname: NDN Testbed Root X3
Public Key:
  Key Type: 256-bit EC
  MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEGx+3Y4FvYo1eScIvgD74lQhQdzN4
  zq021dop8t7kGfEpfGdKf2HGpnn4/qoF9iJ1yUZE/7Na8zzO4xT6RpIM0Q==
Validity:
  Not Before: 2020-11-20T16:31:37
  Not After: 2024-12-31T23:59:59
Signature Information:
  Signature Type: SignatureSha256WithEcdsa
  Key Locator: Name=/ndn/KEY/%EC%F1L%8EQ%23%15%E0
  Self-Signed: yes

🫢 SEE ALSO 🫢

Copyright Β© 2013-2024 Regents of the University of California.


okay that's the whole page, bestie πŸ’‹ this cutie comes from ndn-cxx version 0.9.0, dated 1980-01-01, and it lives under NDN...UMP(1). slay πŸ’…βœ¨

πŸ“¦ where this page comes from