-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to TS 103 097 v1.3.1 #18
Comments
I'm leaving this comment to ask if you are already developing the upgrade Vanetza to 1.3.1 version or if you are awaiting for the release 2 of the ETSI ITS protocols or the release of the asn1c to COER. For researching purposes I've been using vanetza and I would like to know if you have any roadmap in mind. Thanks |
I have the intention to upgrade Vanetza's security entity, however, no definite schedule exists. If you can support this endeavour, your help is much appreciated. |
Maybe I can offer some support, because I've been prototyping with security 1.3.1 some time ago. But I can see one possible problem: the quality of my created code is rather "dirty" and equal to prototyping level. So it's questionable whether this code can be beneficial for further implementation. |
Thanks for your offer @valt2017! I am happy to have a look at your "dirty" code :-) |
Hi @riebl , The thing is that I ended starting the development of the V1.3.1 security. Which can be found on my fork of the project under the branch of "feature/security3". It can be run just by compiling "socktap" and then running it with the following commands (and the files attached to the comment): The development still has some path to walk; both for the project that is intended for and Vanetza; but I would be glad to contribute to the general project and not let this code waste. I'm quite a young researcher and still need to interiorize some of the good practices although I've tried to code following the practices of the project. The code written by now is thought to reuse as much older code as possible. I've created the pull request JordiMarias#1 to comment on the code while I'm developing on the feature branch. Example Certificate: |
Hi @JordiMarias, your support is much appreciated! My plan is to hide the security details (for now: if it is v2 or v3) behind a nice interface. I see that you have added variants for this purpose, which is also a nice option. Do you know if the security logic has changed, i.e. the steps to verify signatures? If the logic is still the same, I would like to have only one implementation of the sign and verify services. As always, tests and documentation are highly welcome too. Related to security, I am currently preparing an initial release of some PKI integration, i.e. fetching the ECTL, station enrolment at EA and loading ATs from AA. |
Hi @riebl , If I open a pull request to your main branch will you comment on relevant changes to the code? Thanks in advance. |
Sure, I will be happy to review your pull request :-) |
TS 103 097 v1.3.1 has been published. Seems like quite a lot of names changed.
I'm just adding this issue as a reminder.
The text was updated successfully, but these errors were encountered: