Files
MicrOBU/microbu-esp32c5/external/vanetza-idf/tools/certify/commands/generate-aa.hpp
T
Ashin Walpola 0e9525162d Keep the colleague's microbu-esp32c5 tree in this repository
obu-firmware builds against vanetza-idf from microbu-esp32c5/external, but
that tree was gitignored, so a clone of this repository could not build the
firmware it ships. It is now committed here as ordinary files in its own
folder, microbu-esp32c5/: the colleague's commit cf4b99f plus the V2X2MAP
bridge's signature verification (--trust) used on the bench. Nothing is
fetched from or pushed to the colleague's repository; this repository and
its remotes carry everything. The folder's own .gitignore keeps build output,
downloaded components and private key material out, as it did there; the
committed file set is identical to that repository's tracked files.

The ESP32-C5 is still flashed from obu-firmware/, which only takes
vanetza-idf from microbu-esp32c5/, so the two stay separate folders.
FLASHING.md says how to take a newer version of the colleague's tree (copy
it over the folder, rebuild, test, commit).
2026-09-23 17:46:40 +02:00

23 lines
510 B
C++

#ifndef CERTIFY_COMMANDS_GENERATE_AA_HPP
#define CERTIFY_COMMANDS_GENERATE_AA_HPP
#include "command.hpp"
class GenerateAaCommand : public Command
{
public:
bool parse(const std::vector<std::string>&) override;
int execute() override;
private:
std::string output;
std::string sign_key_path;
std::string sign_cert_path;
std::string subject_key_path;
std::string subject_name;
int validity_days;
std::vector<unsigned> aids;
};
#endif /* CERTIFY_COMMANDS_GENERATE_AA_HPP */