DDS Security: How are key generated for different publisher
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
After reading the OMG specification about secure DDS: https://www.omg.org/spec/DDS-SECURITY/1.1/
I understood that DDS participants will authenticate each others though a handshake and deduce a secret using DH.
This shared secret is used for the publisher (writer) to share the key used to encrypt the messages published in order for a subscriber (reader) to decrypt the message.
However, what happens if there are multiple publishers for the same topic?
- Do they agree on the same key?
- Do they generate they own key and send them to each reader ?
I am expecting the first option, but could not find confirmation within the OMG specification.
dds data-distribution-service
asked Nov 23 '18 at 12:21
StoogyStoogy
761825
add a comment |
After reading the OMG specification about secure DDS: https://www.omg.org/spec/DDS-SECURITY/1.1/
I understood that DDS participants will authenticate each others though a handshake and deduce a secret using DH.
This shared secret is used for the publisher (writer) to share the key used to encrypt the messages published in order for a subscriber (reader) to decrypt the message.
However, what happens if there are multiple publishers for the same topic?
- Do they agree on the same key?
- Do they generate they own key and send them to each reader ?
I am expecting the first option, but could not find confirmation within the OMG specification.
dds data-distribution-service
asked Nov 23 '18 at 12:21
StoogyStoogy
761825
add a comment |
After reading the OMG specification about secure DDS: https://www.omg.org/spec/DDS-SECURITY/1.1/
I understood that DDS participants will authenticate each others though a handshake and deduce a secret using DH.
This shared secret is used for the publisher (writer) to share the key used to encrypt the messages published in order for a subscriber (reader) to decrypt the message.
However, what happens if there are multiple publishers for the same topic?
- Do they agree on the same key?
- Do they generate they own key and send them to each reader ?
I am expecting the first option, but could not find confirmation within the OMG specification.
dds data-distribution-service
asked Nov 23 '18 at 12:21
StoogyStoogy
761825
After reading the OMG specification about secure DDS: https://www.omg.org/spec/DDS-SECURITY/1.1/
I understood that DDS participants will authenticate each others though a handshake and deduce a secret using DH.
This shared secret is used for the publisher (writer) to share the key used to encrypt the messages published in order for a subscriber (reader) to decrypt the message.
However, what happens if there are multiple publishers for the same topic?
- Do they agree on the same key?
- Do they generate they own key and send them to each reader ?
I am expecting the first option, but could not find confirmation within the OMG specification.
dds data-distribution-service
dds data-distribution-service
asked Nov 23 '18 at 12:21
StoogyStoogy
761825
asked Nov 23 '18 at 12:21
StoogyStoogy
761825
asked Nov 23 '18 at 12:21
StoogyStoogy
761825
asked Nov 23 '18 at 12:21
StoogyStoogy
761825
asked Nov 23 '18 at 12:21
StoogyStoogy
761825
761825
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
However, what happens if there are multiple publishers for the same
topic?
Each DataWriter (not Publisher) generates its own symmetric key which gets shared with all its matched DataReaders. The fact that multiple DataWriters may be writing to the same Topic does not change this -- each of them generates their own key and uses it to protects its own updates.
Note that this is the behavior as prescribed by the so-called built-in plugins as defined in Chapter 9 of the specification that you mentioned. These are defined to provide out-of-the-box functionality with interoperability between vendors. Customized plugins may behave differently.
answered Nov 23 '18 at 19:47
Reinier TorenbeekReinier Torenbeek
10k32848
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53446640%2fdds-security-how-are-key-generated-for-different-publisher%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
However, what happens if there are multiple publishers for the same
topic?
Each DataWriter (not Publisher) generates its own symmetric key which gets shared with all its matched DataReaders. The fact that multiple DataWriters may be writing to the same Topic does not change this -- each of them generates their own key and uses it to protects its own updates.
Note that this is the behavior as prescribed by the so-called built-in plugins as defined in Chapter 9 of the specification that you mentioned. These are defined to provide out-of-the-box functionality with interoperability between vendors. Customized plugins may behave differently.
answered Nov 23 '18 at 19:47
Reinier TorenbeekReinier Torenbeek
10k32848
add a comment |
However, what happens if there are multiple publishers for the same
topic?
Each DataWriter (not Publisher) generates its own symmetric key which gets shared with all its matched DataReaders. The fact that multiple DataWriters may be writing to the same Topic does not change this -- each of them generates their own key and uses it to protects its own updates.
Note that this is the behavior as prescribed by the so-called built-in plugins as defined in Chapter 9 of the specification that you mentioned. These are defined to provide out-of-the-box functionality with interoperability between vendors. Customized plugins may behave differently.
answered Nov 23 '18 at 19:47
Reinier TorenbeekReinier Torenbeek
10k32848
add a comment |
However, what happens if there are multiple publishers for the same
topic?
Each DataWriter (not Publisher) generates its own symmetric key which gets shared with all its matched DataReaders. The fact that multiple DataWriters may be writing to the same Topic does not change this -- each of them generates their own key and uses it to protects its own updates.
Note that this is the behavior as prescribed by the so-called built-in plugins as defined in Chapter 9 of the specification that you mentioned. These are defined to provide out-of-the-box functionality with interoperability between vendors. Customized plugins may behave differently.
answered Nov 23 '18 at 19:47
Reinier TorenbeekReinier Torenbeek
10k32848
However, what happens if there are multiple publishers for the same
topic?
Each DataWriter (not Publisher) generates its own symmetric key which gets shared with all its matched DataReaders. The fact that multiple DataWriters may be writing to the same Topic does not change this -- each of them generates their own key and uses it to protects its own updates.
Note that this is the behavior as prescribed by the so-called built-in plugins as defined in Chapter 9 of the specification that you mentioned. These are defined to provide out-of-the-box functionality with interoperability between vendors. Customized plugins may behave differently.
answered Nov 23 '18 at 19:47
Reinier TorenbeekReinier Torenbeek
10k32848
edited Nov 23 '18 at 19:53
answered Nov 23 '18 at 19:47
Reinier TorenbeekReinier Torenbeek
10k32848
answered Nov 23 '18 at 19:47
Reinier TorenbeekReinier Torenbeek
10k32848
answered Nov 23 '18 at 19:47
Reinier TorenbeekReinier Torenbeek
10k32848
10k32848
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53446640%2fdds-security-how-are-key-generated-for-different-publisher%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
