Mixing
maskGenAlgorithm for RSA signature with PKCS1-PSS padding
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am generating RSA signature using RSA_PKCS1_PSS_PADDING. I am setting digest algorithm as SHA256 using EVP_get_digestbyname() and EVP_DigestSignInit(). And salt length parameter as -1 using EVP_PKEY_CTX_set_rsa_pss_saltlen().
I have EVP_MD_CTX, EVP_MD and EVP_PKEY_CTX structures used for signature generation.
How can I get the name of Mask generation algorithm name used by OpenSSL by default? Is there any API provided for getting it?
Edit: OpenSSL version used: 1.1.0g.
rsa signature openssl
asked Jan 3 at 5:49
mk09mk09
586
migrated from crypto.stackexchange.com Jan 3 at 11:33
This question came from our site for software developers, mathematicians and others interested in cryptography.
add a comment |
I am generating RSA signature using RSA_PKCS1_PSS_PADDING. I am setting digest algorithm as SHA256 using EVP_get_digestbyname() and EVP_DigestSignInit(). And salt length parameter as -1 using EVP_PKEY_CTX_set_rsa_pss_saltlen().
I have EVP_MD_CTX, EVP_MD and EVP_PKEY_CTX structures used for signature generation.
How can I get the name of Mask generation algorithm name used by OpenSSL by default? Is there any API provided for getting it?
Edit: OpenSSL version used: 1.1.0g.
rsa signature openssl
asked Jan 3 at 5:49
mk09mk09
586
migrated from crypto.stackexchange.com Jan 3 at 11:33
This question came from our site for software developers, mathematicians and others interested in cryptography.
EVP_PKEY_CTX_set_rsa_pss_keygen_mgf1_mdsets mgf1 digest. I need to get the digest name used by OpenSSL by default.
– mk09
Jan 3 at 10:36
add a comment |
I am generating RSA signature using RSA_PKCS1_PSS_PADDING. I am setting digest algorithm as SHA256 using EVP_get_digestbyname() and EVP_DigestSignInit(). And salt length parameter as -1 using EVP_PKEY_CTX_set_rsa_pss_saltlen().
I have EVP_MD_CTX, EVP_MD and EVP_PKEY_CTX structures used for signature generation.
How can I get the name of Mask generation algorithm name used by OpenSSL by default? Is there any API provided for getting it?
Edit: OpenSSL version used: 1.1.0g.
rsa signature openssl
asked Jan 3 at 5:49
mk09mk09
586
I am generating RSA signature using RSA_PKCS1_PSS_PADDING. I am setting digest algorithm as SHA256 using EVP_get_digestbyname() and EVP_DigestSignInit(). And salt length parameter as -1 using EVP_PKEY_CTX_set_rsa_pss_saltlen().
I have EVP_MD_CTX, EVP_MD and EVP_PKEY_CTX structures used for signature generation.
How can I get the name of Mask generation algorithm name used by OpenSSL by default? Is there any API provided for getting it?
Edit: OpenSSL version used: 1.1.0g.
rsa signature openssl
rsa signature openssl
asked Jan 3 at 5:49
mk09mk09
586
asked Jan 3 at 5:49
mk09mk09
586
asked Jan 3 at 5:49
mk09mk09
586
asked Jan 3 at 5:49
mk09mk09
586
asked Jan 3 at 5:49
mk09mk09
586
586
migrated from crypto.stackexchange.com Jan 3 at 11:33
This question came from our site for software developers, mathematicians and others interested in cryptography.
migrated from crypto.stackexchange.com Jan 3 at 11:33
This question came from our site for software developers, mathematicians and others interested in cryptography.
EVP_PKEY_CTX_set_rsa_pss_keygen_mgf1_mdsets mgf1 digest. I need to get the digest name used by OpenSSL by default.
– mk09
Jan 3 at 10:36
add a comment |
EVP_PKEY_CTX_set_rsa_pss_keygen_mgf1_mdsets mgf1 digest. I need to get the digest name used by OpenSSL by default.
– mk09
Jan 3 at 10:36
EVP_PKEY_CTX_set_rsa_pss_keygen_mgf1_md sets mgf1 digest. I need to get the digest name used by OpenSSL by default.– mk09
Jan 3 at 10:36
EVP_PKEY_CTX_set_rsa_pss_keygen_mgf1_md sets mgf1 digest. I need to get the digest name used by OpenSSL by default.– mk09
Jan 3 at 10:36
add a comment |
1 Answer
1
active
oldest
votes
RSASSA-PSS is in practice always used with MGF1 as the Mask Generation Function. The only variation is which Message Digest is used internally by MGF1.
Sometime that's the same Message Digest as the one used for hashing the message and building the tag in PSS, because that makes the most sense. Other times it is SHA-1 because that used to be the default MD for early RSASSA-PSS APIs, thus for the associated MGF1.
In an ideal world, some attribute (in the signature, or/and in the public key certificate used to check the signature) would tell MGF1-with-such-MD, perhaps by way of some Object IDentifier like we have to specify PSS. But crypto APIs are hell.
In order to control what Message Digest is used by MGF1, we want something on the tune of what -sigopt rsa_mgf1_md:sha256 does in the openssl dgst command.
My best guess is to set the MGF1 digest using
assert(EVP_PKEY_CTX_set_rsa_mgf1_md(ctx, EVP_sha256)>=0);
or get it using EVP_PKEY_CTX_get_rsa_mgf1_md() as documented:
The
EVP_PKEY_CTX_get_rsa_mgf1_md()macro gets the MGF1 digest forctx. If not explicitly set the signing digest is used. The padding mode must have been set toRSA_PKCS1_OAEP_PADDINGorRSA_PKCS1_PSS_PADDING.
answered Jan 3 at 14:25
fgrieufgrieu
1,26211327
1
A.2.3 in v2.2 defines an ASN.1 structure for PSS parameters, which OpenSSL does implement when used in CMS (and SMIME), but AFAICS does not expose otherwise.
– dave_thompson_085
Jan 4 at 5:25
EVP_PKEY_CTX_get_rsa_mgf1_mdgivesEVP_MD **mdstructure as output. But I'm unable to find a way to get digest name out of it. Can we get digest name from this structure?
– mk09
Jan 4 at 9:00
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%2f54021467%2fmaskgenalgorithm-for-rsa-signature-with-pkcs1-pss-padding%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
RSASSA-PSS is in practice always used with MGF1 as the Mask Generation Function. The only variation is which Message Digest is used internally by MGF1.
Sometime that's the same Message Digest as the one used for hashing the message and building the tag in PSS, because that makes the most sense. Other times it is SHA-1 because that used to be the default MD for early RSASSA-PSS APIs, thus for the associated MGF1.
In an ideal world, some attribute (in the signature, or/and in the public key certificate used to check the signature) would tell MGF1-with-such-MD, perhaps by way of some Object IDentifier like we have to specify PSS. But crypto APIs are hell.
In order to control what Message Digest is used by MGF1, we want something on the tune of what -sigopt rsa_mgf1_md:sha256 does in the openssl dgst command.
My best guess is to set the MGF1 digest using
assert(EVP_PKEY_CTX_set_rsa_mgf1_md(ctx, EVP_sha256)>=0);
or get it using EVP_PKEY_CTX_get_rsa_mgf1_md() as documented:
The
EVP_PKEY_CTX_get_rsa_mgf1_md()macro gets the MGF1 digest forctx. If not explicitly set the signing digest is used. The padding mode must have been set toRSA_PKCS1_OAEP_PADDINGorRSA_PKCS1_PSS_PADDING.
answered Jan 3 at 14:25
fgrieufgrieu
1,26211327
1
A.2.3 in v2.2 defines an ASN.1 structure for PSS parameters, which OpenSSL does implement when used in CMS (and SMIME), but AFAICS does not expose otherwise.
– dave_thompson_085
Jan 4 at 5:25
EVP_PKEY_CTX_get_rsa_mgf1_mdgivesEVP_MD **mdstructure as output. But I'm unable to find a way to get digest name out of it. Can we get digest name from this structure?
– mk09
Jan 4 at 9:00
add a comment |
RSASSA-PSS is in practice always used with MGF1 as the Mask Generation Function. The only variation is which Message Digest is used internally by MGF1.
Sometime that's the same Message Digest as the one used for hashing the message and building the tag in PSS, because that makes the most sense. Other times it is SHA-1 because that used to be the default MD for early RSASSA-PSS APIs, thus for the associated MGF1.
In an ideal world, some attribute (in the signature, or/and in the public key certificate used to check the signature) would tell MGF1-with-such-MD, perhaps by way of some Object IDentifier like we have to specify PSS. But crypto APIs are hell.
In order to control what Message Digest is used by MGF1, we want something on the tune of what -sigopt rsa_mgf1_md:sha256 does in the openssl dgst command.
My best guess is to set the MGF1 digest using
assert(EVP_PKEY_CTX_set_rsa_mgf1_md(ctx, EVP_sha256)>=0);
or get it using EVP_PKEY_CTX_get_rsa_mgf1_md() as documented:
The
EVP_PKEY_CTX_get_rsa_mgf1_md()macro gets the MGF1 digest forctx. If not explicitly set the signing digest is used. The padding mode must have been set toRSA_PKCS1_OAEP_PADDINGorRSA_PKCS1_PSS_PADDING.
answered Jan 3 at 14:25
fgrieufgrieu
1,26211327
1
A.2.3 in v2.2 defines an ASN.1 structure for PSS parameters, which OpenSSL does implement when used in CMS (and SMIME), but AFAICS does not expose otherwise.
– dave_thompson_085
Jan 4 at 5:25
EVP_PKEY_CTX_get_rsa_mgf1_mdgivesEVP_MD **mdstructure as output. But I'm unable to find a way to get digest name out of it. Can we get digest name from this structure?
– mk09
Jan 4 at 9:00
add a comment |
RSASSA-PSS is in practice always used with MGF1 as the Mask Generation Function. The only variation is which Message Digest is used internally by MGF1.
Sometime that's the same Message Digest as the one used for hashing the message and building the tag in PSS, because that makes the most sense. Other times it is SHA-1 because that used to be the default MD for early RSASSA-PSS APIs, thus for the associated MGF1.
In an ideal world, some attribute (in the signature, or/and in the public key certificate used to check the signature) would tell MGF1-with-such-MD, perhaps by way of some Object IDentifier like we have to specify PSS. But crypto APIs are hell.
In order to control what Message Digest is used by MGF1, we want something on the tune of what -sigopt rsa_mgf1_md:sha256 does in the openssl dgst command.
My best guess is to set the MGF1 digest using
assert(EVP_PKEY_CTX_set_rsa_mgf1_md(ctx, EVP_sha256)>=0);
or get it using EVP_PKEY_CTX_get_rsa_mgf1_md() as documented:
The
EVP_PKEY_CTX_get_rsa_mgf1_md()macro gets the MGF1 digest forctx. If not explicitly set the signing digest is used. The padding mode must have been set toRSA_PKCS1_OAEP_PADDINGorRSA_PKCS1_PSS_PADDING.
answered Jan 3 at 14:25
fgrieufgrieu
1,26211327
RSASSA-PSS is in practice always used with MGF1 as the Mask Generation Function. The only variation is which Message Digest is used internally by MGF1.
Sometime that's the same Message Digest as the one used for hashing the message and building the tag in PSS, because that makes the most sense. Other times it is SHA-1 because that used to be the default MD for early RSASSA-PSS APIs, thus for the associated MGF1.
In an ideal world, some attribute (in the signature, or/and in the public key certificate used to check the signature) would tell MGF1-with-such-MD, perhaps by way of some Object IDentifier like we have to specify PSS. But crypto APIs are hell.
In order to control what Message Digest is used by MGF1, we want something on the tune of what -sigopt rsa_mgf1_md:sha256 does in the openssl dgst command.
My best guess is to set the MGF1 digest using
assert(EVP_PKEY_CTX_set_rsa_mgf1_md(ctx, EVP_sha256)>=0);
or get it using EVP_PKEY_CTX_get_rsa_mgf1_md() as documented:
The
EVP_PKEY_CTX_get_rsa_mgf1_md()macro gets the MGF1 digest forctx. If not explicitly set the signing digest is used. The padding mode must have been set toRSA_PKCS1_OAEP_PADDINGorRSA_PKCS1_PSS_PADDING.
answered Jan 3 at 14:25
fgrieufgrieu
1,26211327
edited Jan 4 at 8:24
answered Jan 3 at 14:25
fgrieufgrieu
1,26211327
answered Jan 3 at 14:25
fgrieufgrieu
1,26211327
answered Jan 3 at 14:25
fgrieufgrieu
1,26211327
1,26211327
1
A.2.3 in v2.2 defines an ASN.1 structure for PSS parameters, which OpenSSL does implement when used in CMS (and SMIME), but AFAICS does not expose otherwise.
– dave_thompson_085
Jan 4 at 5:25
EVP_PKEY_CTX_get_rsa_mgf1_mdgivesEVP_MD **mdstructure as output. But I'm unable to find a way to get digest name out of it. Can we get digest name from this structure?
– mk09
Jan 4 at 9:00
add a comment |
1
A.2.3 in v2.2 defines an ASN.1 structure for PSS parameters, which OpenSSL does implement when used in CMS (and SMIME), but AFAICS does not expose otherwise.
– dave_thompson_085
Jan 4 at 5:25
EVP_PKEY_CTX_get_rsa_mgf1_mdgivesEVP_MD **mdstructure as output. But I'm unable to find a way to get digest name out of it. Can we get digest name from this structure?
– mk09
Jan 4 at 9:00
1
1
A.2.3 in v2.2 defines an ASN.1 structure for PSS parameters, which OpenSSL does implement when used in CMS (and SMIME), but AFAICS does not expose otherwise.
– dave_thompson_085
Jan 4 at 5:25
A.2.3 in v2.2 defines an ASN.1 structure for PSS parameters, which OpenSSL does implement when used in CMS (and SMIME), but AFAICS does not expose otherwise.
– dave_thompson_085
Jan 4 at 5:25
EVP_PKEY_CTX_get_rsa_mgf1_md gives EVP_MD **md structure as output. But I'm unable to find a way to get digest name out of it. Can we get digest name from this structure?– mk09
Jan 4 at 9:00
EVP_PKEY_CTX_get_rsa_mgf1_md gives EVP_MD **md structure as output. But I'm unable to find a way to get digest name out of it. Can we get digest name from this structure?– mk09
Jan 4 at 9:00
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%2f54021467%2fmaskgenalgorithm-for-rsa-signature-with-pkcs1-pss-padding%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
EVP_PKEY_CTX_set_rsa_pss_keygen_mgf1_mdsets mgf1 digest. I need to get the digest name used by OpenSSL by default.– mk09
Jan 3 at 10:36