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

PolicyTableUpdate is failed by any reason and "ForceProtectedService"=ON at .ini file #1923

Closed
6 of 9 tasks
AStasiuk opened this issue Nov 24, 2017 · 4 comments
Closed
6 of 9 tasks
Labels
Projects

Comments

@AStasiuk
Copy link

AStasiuk commented Nov 24, 2017

Occurrence: Always

Steps to reproduce

  1. Make sure SDL is built with default flags
  2. Set audio/video service as ForceProtectedService value (ForceProtectedService = 0x0A, 0x0B) in smartDeviceLink.ini
  3. Start SDL and HMI
  4. Connect mobile device
  5. Register navi mobile application
  6. PTU is triggered and failed because of invalid PT( In script missed seconds_between_retries in PT )
  7. Activate App
  8. Start secure audio/video service

Expected result

SDL responds StartService NACK to this mobile application and does not start service.

Actual result

SDL responds StartService ACK(encryption = false) to this mobile application and starts not secure service.

Test scripts

1923_1_navi_audio.lua
1923_2_navi_video.lua

Environment

Attachments

Expected delivery

  • Source code updates
  • Code comments
  • UTs add/update (not required)
  • ATF tests add/update
  • Manual tests (not required)
  • Add/update CI plans/jobs (not required)
  • SDD updates (not required)
  • Guidelines update (sdl_core_guides) (not required)
  • Guidelines update (sdl_hmi_integration_guidelines) (not required)
@AStasiuk AStasiuk added the Bug label Nov 24, 2017
@AStasiuk AStasiuk changed the title SDL behavior in case PolicyTableUpdate is failed by any reason and "ForceProtectedService"=ON at .ini file PolicyTableUpdate is failed by any reason and "ForceProtectedService"=ON at .ini file Nov 24, 2017
@dboltovskyi
Copy link
Contributor

Priority was set to High. Issue breaks correct secure session establishing process. Also application would not be aware about secure session establishing status.

@dboltovskyi
Copy link
Contributor

Issue is reproduced on develop branch (0b19cf4)

@jacobkeeler
Copy link
Contributor

Verified that this is fixed by #1971.

@jacobkeeler
Copy link
Contributor

Fixed with the merge of #1971

@theresalech theresalech added this to Completed Bug Fixes in 4.5.0 Feb 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
4.5.0
Completed Bug Fixes
Development

No branches or pull requests

3 participants