As we had a conversation, the V&V request can be covered in the effort of the three stacks checking their versions and compatibility, then a message can be sent over the HD channel.
As we had a conversation, the V&V request can be covered in the effort of the three stacks checking their versions and compatibility, then a message can be sent over the HD channel.
The UI is already talking with Dialin. Your simulator is using dialin to talk to the UI. Because the UI doesn't recognize Dialin at all, Dialin has to talk on the HD to UI or DG to UI channels inst...
The UI is already talking with Dialin. Your simulator is using dialin to talk to the UI. Because the UI doesn't recognize Dialin at all, Dialin has to talk on the HD to UI or DG to UI channels instead when sending up commands to the UI. This poses a security risk because the UI could never restrict communication to just the DG/HD only. If Dialin can talk to the UI on separate channels then those channels can be ignored in production mode later.
It's your stack so your call but something I think we should consider
These definitions force dialin to talk on an HD/DG channels in order to simulate the UI. Seems like a security risk and that the UI should be able to tell the difference.
These definitions force dialin to talk on an HD/DG channels in order to simulate the UI. Seems like a security risk and that the UI should be able to tell the difference.