it will be but we first prefer to do some final tests with that version. Feel free to also test. Either this or the next micro version will eventually be announced.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 7 2022
Feb 2 2022
Hi there, is this the new stable version of libgcrypt? Apologies if this is the wrong place to ask; I just couldn’t find any other release announcement for 1.10.0.
Feb 1 2022
Thanks, Werner. This was originally reported by Alejandro Masino.
Jan 31 2022
Thanks
Jan 29 2022
Jan 28 2022
Jan 27 2022
@jukivili , thank you for your comment.
Jan 26 2022
I planned to reply to your email on mailing-list, but I just have too little time.
Jan 25 2022
For the record, there is a new report on the mailing list about this module on MacOS:
Thank you, applied both of two patches.
Jan 24 2022
Thanks. Looks good to me.
struct thread_creation { void (*compute) (void *arg); void *arg; void (*create_done) (gcry_kdf_handle_t *hd, void *tid); };
Jan 22 2022
Jan 20 2022
Test cases are recovered in rC535a4d345872: fips: Recover test cases for selftest, add skipping in FIPS mode..
Jan 19 2022
Sorry, it's my misunderstanding.
_gcry_fips_run_selftest can be run by GCRYCTL_SELFTEST.
I was confused by the function name. Perhaps, it is good to change the name of function to _gcry_run_selftest.
@werner Those removed tests are selftests which are only invoked by FIPS mode for its requirement of selftests.
AFAICS, the last commit removes some tests. We should never remove a test just because FIPS does not allow it. The old tests need to be run in non-fips mode.
Pushed the change in rC76aad97dd312: fips: Reject shorter key for HMAC in FIPS mode..
Jan 18 2022
And we need to fix selftest for shorter keys.
@pmgdeb : IIUC, what we need is:
diff --git a/cipher/md.c b/cipher/md.c index 34336b5c..4f4fc9bf 100644 --- a/cipher/md.c +++ b/cipher/md.c @@ -903,6 +903,9 @@ prepare_macpads (gcry_md_hd_t a, const unsigned char *key, size_t keylen) { GcryDigestEntry *r;
Jan 17 2022
In T5512#153650, @Jakuje wrote:This is my draft for the FIPS indicator KDF. I think we do not need to keep the original GCRYCTL_FIPS_SERVICE_INDICATOR if we replace it also in the tests. This will also need some tests and documentation update.
libgcrypt-fips-indicator-kdf.patch3 KBDownload
I'm not completely sure but it might be convenient to mark HMAC keys with lengths less that 112 as non-approved in FIPS mode for both generation and verification. It could be easily implemented by adding a check using cipher/mac-hmac.c:hmac_get_keylen() or at the algo level. What do you think?
Thank you, applied.
Also, add another change.
Jan 12 2022
Jan 11 2022
I went through the documentation related to FIPS and updated some wording to match reality. It will probably require still some more work.
This is my draft for the FIPS indicator KDF. I think we do not need to keep the original GCRYCTL_FIPS_SERVICE_INDICATOR if we replace it also in the tests. This will also need some tests and documentation update.
Yes, we should introduce an INDICATOR_KDF thing.
Thank you.
Applied.
Patch applied, doc updated.
No change of FSM diagram.
I pushed the change: rC383866f014f2: cipher: Keep original behavior of Key Unwrap when not extended.
Jan 10 2022
The previous comment should have come to the T5600. Sorry for the noise.
Sorry for resurrecting the done task, but I got a message from @pmgdeb who noticed there is mismatch between parenthesis in the --with-fips-module-version help string. The attached patch fixes the issue and add proper help text.
Sorry for resurrecting the done task, but I got a message from @pmgdeb who noticed there is mismatch between parenthesis in the --with-fips-module-version help string. The attached patch fixes the issue and add proper help text.
Jan 9 2022
Jan 8 2022
Jan 7 2022
Jan 6 2022
Now, unwrapping supports both cases (KW and KWP).
Jan 5 2022
Jan 4 2022
For unwrapping, it is good if we can support "automatic" unwrapping, apply W^-1 and check the first 8 octets to see if it's KW or KWP.
Thanks. Looks good to me (both merged changes and the above proposal). In addition to the changes proposed above, we certainly need to update the documentation about this, probably also the FSM diagram.
And I'm testing following:
The "at first" change done.
At first, I think that we need to change the way how libgcrypt rejects non-approved cipher/md/mac/pk.