Skip to content
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

[SDL 0317] SDL Protocol Security Specification #40

Closed
theresalech opened this issue Jun 10, 2021 · 1 comment · Fixed by #41
Closed

[SDL 0317] SDL Protocol Security Specification #40

theresalech opened this issue Jun 10, 2021 · 1 comment · Fixed by #41
Labels
Projects

Comments

@theresalech
Copy link

Proposal: SDL Protocol Security Specification

This proposal adds the documentation and specification around protected communication, encryption and handshake to the SDL protocol specification. It is a collaborated effort with Ford and Luxoft to protect the implemented SDL security from unexpected changes and to allow SDL Evolution proposals to improve it.

Review: smartdevicelink/sdl_evolution#1070

Steering Committee Decision: The Steering Committee voted to accept this proposal with the following revisions:

  1. Remove "Note: Communication partners should set this field to zero" from the "Frame Info" and "Data Size" descriptions in the Change 1 table (https://github.com/smartdevicelink/sdl_evolution/blob/master/proposals/0317-sdl-protocol-security-specification.md#change-1-update-frame-header-fields-description).
  2. In Proposed solution section (4.2.5 Start Service), change "See "Secured Communication" section for more details." to "See "7. Secured Communication" section for more details."
  3. In Proposed solution section (7. Secured Communication), change "It is possible to establish a secured and encrypted communication with the system by setting the frame header encryption flag to 1 when starting a new service." to "It is possible to establish a secured and encrypted communication with the system by setting the frame header encryption flag to 1 when starting a new service or by sending another StartService with the encryption flag to 1 when the service is already established (this the required flow for the RPC service)."
  4. Update Impact on existing code section to remove code changes related to Core/Mobile libraries, and update Impacted Platforms to only include "Protocol".

The proposal .md file was updated to reflect these revisions on 6/10/21

@jacobkeeler
Copy link
Contributor

Closing via #41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
5.4.1
Done
Development

Successfully merging a pull request may close this issue.

2 participants