Is the AES key good enough?
When the System.Security.Cryptography.Aes.Create(algorithmName) method is called, a new key and IV are generated. Are these good enough to use?
cryptography bcl system.security
asked Nov 16 '18 at 14:37
Old GeezerOld Geezer
3,8601149100
add a comment |
When the System.Security.Cryptography.Aes.Create(algorithmName) method is called, a new key and IV are generated. Are these good enough to use?
cryptography bcl system.security
asked Nov 16 '18 at 14:37
Old GeezerOld Geezer
3,8601149100
add a comment |
When the System.Security.Cryptography.Aes.Create(algorithmName) method is called, a new key and IV are generated. Are these good enough to use?
cryptography bcl system.security
asked Nov 16 '18 at 14:37
Old GeezerOld Geezer
3,8601149100
When the System.Security.Cryptography.Aes.Create(algorithmName) method is called, a new key and IV are generated. Are these good enough to use?
cryptography bcl system.security
cryptography bcl system.security
asked Nov 16 '18 at 14:37
Old GeezerOld Geezer
3,8601149100
asked Nov 16 '18 at 14:37
Old GeezerOld Geezer
3,8601149100
asked Nov 16 '18 at 14:37
Old GeezerOld Geezer
3,8601149100
asked Nov 16 '18 at 14:37
Old GeezerOld Geezer
3,8601149100
asked Nov 16 '18 at 14:37
Old GeezerOld Geezer
3,8601149100
3,8601149100
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Those values are safe to use. The whole purpose of frameworks like this one is to make the generation of cryptographically random values easier. Aes.Create() is also used in the sample code
Additionally, the documentation describes Aes.Create():
Creates a cryptographic object that is used to perform the symmetric
algorithm.
This library is maintained by Microsoft, I think it is safe to say their values are "safe" to use.
answered Nov 16 '18 at 15:25
DoesDataDoesData
1,90511226
What I am asking is thatCreategenerates akeythat is random enough to be used. I am planning to use a different key/IV for every message.
– Old Geezer
Nov 16 '18 at 16:27
1
Yes those values are safe to use. They are cryptographically generated. If they weren't the entire library would be useless.
– DoesData
Nov 16 '18 at 16:42
1
Yes, Microsoft .Net cryptography is generally secure by default, and can be trusted: you should use it rather than trying to generate values your own way. .Net cryptography is a big step forward from older languages like Java. I'm planning a blog on the evolution of cryptographic APIs that covers exactly this topic.
– TheGreatContini
Nov 16 '18 at 19:52
@TheGreatContini That's very opinionated. I think both languages have their advantages and disadvantages. I don't see any reasons for this kind of remark given the topic.
– Maarten Bodewes
Nov 17 '18 at 23:23
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%2f53339925%2fis-the-aes-key-good-enough%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
Those values are safe to use. The whole purpose of frameworks like this one is to make the generation of cryptographically random values easier. Aes.Create() is also used in the sample code
Additionally, the documentation describes Aes.Create():
Creates a cryptographic object that is used to perform the symmetric
algorithm.
This library is maintained by Microsoft, I think it is safe to say their values are "safe" to use.
answered Nov 16 '18 at 15:25
DoesDataDoesData
1,90511226
What I am asking is thatCreategenerates akeythat is random enough to be used. I am planning to use a different key/IV for every message.
– Old Geezer
Nov 16 '18 at 16:27
1
Yes those values are safe to use. They are cryptographically generated. If they weren't the entire library would be useless.
– DoesData
Nov 16 '18 at 16:42
1
Yes, Microsoft .Net cryptography is generally secure by default, and can be trusted: you should use it rather than trying to generate values your own way. .Net cryptography is a big step forward from older languages like Java. I'm planning a blog on the evolution of cryptographic APIs that covers exactly this topic.
– TheGreatContini
Nov 16 '18 at 19:52
@TheGreatContini That's very opinionated. I think both languages have their advantages and disadvantages. I don't see any reasons for this kind of remark given the topic.
– Maarten Bodewes
Nov 17 '18 at 23:23
add a comment |
Those values are safe to use. The whole purpose of frameworks like this one is to make the generation of cryptographically random values easier. Aes.Create() is also used in the sample code
Additionally, the documentation describes Aes.Create():
Creates a cryptographic object that is used to perform the symmetric
algorithm.
This library is maintained by Microsoft, I think it is safe to say their values are "safe" to use.
answered Nov 16 '18 at 15:25
DoesDataDoesData
1,90511226
What I am asking is thatCreategenerates akeythat is random enough to be used. I am planning to use a different key/IV for every message.
– Old Geezer
Nov 16 '18 at 16:27
1
Yes those values are safe to use. They are cryptographically generated. If they weren't the entire library would be useless.
– DoesData
Nov 16 '18 at 16:42
1
Yes, Microsoft .Net cryptography is generally secure by default, and can be trusted: you should use it rather than trying to generate values your own way. .Net cryptography is a big step forward from older languages like Java. I'm planning a blog on the evolution of cryptographic APIs that covers exactly this topic.
– TheGreatContini
Nov 16 '18 at 19:52
@TheGreatContini That's very opinionated. I think both languages have their advantages and disadvantages. I don't see any reasons for this kind of remark given the topic.
– Maarten Bodewes
Nov 17 '18 at 23:23
add a comment |
Those values are safe to use. The whole purpose of frameworks like this one is to make the generation of cryptographically random values easier. Aes.Create() is also used in the sample code
Additionally, the documentation describes Aes.Create():
Creates a cryptographic object that is used to perform the symmetric
algorithm.
This library is maintained by Microsoft, I think it is safe to say their values are "safe" to use.
answered Nov 16 '18 at 15:25
DoesDataDoesData
1,90511226
Those values are safe to use. The whole purpose of frameworks like this one is to make the generation of cryptographically random values easier. Aes.Create() is also used in the sample code
Additionally, the documentation describes Aes.Create():
Creates a cryptographic object that is used to perform the symmetric
algorithm.
This library is maintained by Microsoft, I think it is safe to say their values are "safe" to use.
answered Nov 16 '18 at 15:25
DoesDataDoesData
1,90511226
edited Nov 16 '18 at 16:41
answered Nov 16 '18 at 15:25
DoesDataDoesData
1,90511226
answered Nov 16 '18 at 15:25
DoesDataDoesData
1,90511226
answered Nov 16 '18 at 15:25
DoesDataDoesData
1,90511226
1,90511226
What I am asking is thatCreategenerates akeythat is random enough to be used. I am planning to use a different key/IV for every message.
– Old Geezer
Nov 16 '18 at 16:27
1
Yes those values are safe to use. They are cryptographically generated. If they weren't the entire library would be useless.
– DoesData
Nov 16 '18 at 16:42
1
Yes, Microsoft .Net cryptography is generally secure by default, and can be trusted: you should use it rather than trying to generate values your own way. .Net cryptography is a big step forward from older languages like Java. I'm planning a blog on the evolution of cryptographic APIs that covers exactly this topic.
– TheGreatContini
Nov 16 '18 at 19:52
@TheGreatContini That's very opinionated. I think both languages have their advantages and disadvantages. I don't see any reasons for this kind of remark given the topic.
– Maarten Bodewes
Nov 17 '18 at 23:23
add a comment |
What I am asking is thatCreategenerates akeythat is random enough to be used. I am planning to use a different key/IV for every message.
– Old Geezer
Nov 16 '18 at 16:27
1
Yes those values are safe to use. They are cryptographically generated. If they weren't the entire library would be useless.
– DoesData
Nov 16 '18 at 16:42
1
Yes, Microsoft .Net cryptography is generally secure by default, and can be trusted: you should use it rather than trying to generate values your own way. .Net cryptography is a big step forward from older languages like Java. I'm planning a blog on the evolution of cryptographic APIs that covers exactly this topic.
– TheGreatContini
Nov 16 '18 at 19:52
@TheGreatContini That's very opinionated. I think both languages have their advantages and disadvantages. I don't see any reasons for this kind of remark given the topic.
– Maarten Bodewes
Nov 17 '18 at 23:23
What I am asking is that
Create generates a key that is random enough to be used. I am planning to use a different key/IV for every message.– Old Geezer
Nov 16 '18 at 16:27
What I am asking is that
Create generates a key that is random enough to be used. I am planning to use a different key/IV for every message.– Old Geezer
Nov 16 '18 at 16:27
1
1
Yes those values are safe to use. They are cryptographically generated. If they weren't the entire library would be useless.
– DoesData
Nov 16 '18 at 16:42
Yes those values are safe to use. They are cryptographically generated. If they weren't the entire library would be useless.
– DoesData
Nov 16 '18 at 16:42
1
1
Yes, Microsoft .Net cryptography is generally secure by default, and can be trusted: you should use it rather than trying to generate values your own way. .Net cryptography is a big step forward from older languages like Java. I'm planning a blog on the evolution of cryptographic APIs that covers exactly this topic.
– TheGreatContini
Nov 16 '18 at 19:52
Yes, Microsoft .Net cryptography is generally secure by default, and can be trusted: you should use it rather than trying to generate values your own way. .Net cryptography is a big step forward from older languages like Java. I'm planning a blog on the evolution of cryptographic APIs that covers exactly this topic.
– TheGreatContini
Nov 16 '18 at 19:52
@TheGreatContini That's very opinionated. I think both languages have their advantages and disadvantages. I don't see any reasons for this kind of remark given the topic.
– Maarten Bodewes
Nov 17 '18 at 23:23
@TheGreatContini That's very opinionated. I think both languages have their advantages and disadvantages. I don't see any reasons for this kind of remark given the topic.
– Maarten Bodewes
Nov 17 '18 at 23:23
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%2f53339925%2fis-the-aes-key-good-enough%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
