EVerest ChargeSOM 0.9.0#99
Open
FaHaGit wants to merge 7 commits intoeverest/charge_somfrom
Open
Conversation
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com> docs: fix GitHub link for evse_board_support in EVerest documentation Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
barsnick
requested changes
May 5, 2026
| This is the Hardware Abstraction Layer (HAL) for Charge SOM in EVerest. It implements | ||
| the `evse_board_support <https://github.com/EVerest/everest-core/blob/main/interfaces/evse_board_support.yaml>`_ | ||
| This is the Hardware Abstraction Layer (HAL) for the Charge SOM in EVerest. It implements | ||
| the `evse_board_support <https://github.com/EVerest/everest/blob/main/interfaces/evse_board_support.yaml>`_ |
Contributor
There was a problem hiding this comment.
Suggested change
| the `evse_board_support <https://github.com/EVerest/everest/blob/main/interfaces/evse_board_support.yaml>`_ | |
| the `evse_board_support <https://github.com/EVerest/EVerest/blob/main/interfaces/evse_board_support.yaml>`_ |
lategoodbye
requested changes
May 5, 2026
| For TLS and especially Plug & Charge, private keys should be protected according to the requirements of the | ||
| certificate authority or certificate management system. In many production environments, this means using | ||
| hardware-backed key storage such as a TPM, HSM, or comparable technology. | ||
| Charge SOM already includes a TPM and is therefore suitable for the secure storage of private keys. |
Member
There was a problem hiding this comment.
Yes, it's correct that the Charge SOM has a TPM. But as long as it hasn't been proplerly evaluate as a key storage, I would suggest our customers should contact us in case they want to implement a real world PnC scenario.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refresh EVerest ChargeSOM documentation for release 0.9.0