On Friday, September 17, 2021 at 8:25:00 PM UTC-4 Jeffrey Walton wrote:
> On Thu, Sep 16, 2021 at 8:42 PM austin clifton
> wrote:
> >
> > I have an issue which I believe may be a bug. I followed the
> instructions from the "Bug Report" page on the cryptopp wiki and all tests
> in
On Friday, September 17, 2021 at 11:26:25 AM UTC-4 skullm...@gmail.com
wrote:
> ... The final goal is to build a JWT and sign it with the public key,
> constructed out of x and y. If I can find a way to use the public key
> directly, that may be a workaround of that problem - in the end I
Great, thanks for the update. I'll follow the conversation over there.
On Friday, September 17, 2021 at 5:42:17 PM UTC-7 Jeffrey Walton wrote:
> On Friday, September 17, 2021 at 8:25:00 PM UTC-4 Jeffrey Walton wrote:
>
>> On Thu, Sep 16, 2021 at 8:42 PM austin clifton
>> wrote:
>> >
>> > I
Correction: I have to encrypt the JWT, not sign it. Signing is with the
private key - which I don't have. I will take a look at the article and the
linking. Maybe that will bring some hints for me. Thanks again :)
Jeffrey Walton schrieb am Samstag, 18. September 2021 um 05:11:31 UTC+2:
> On
Thanks for your help! Resolved, the issue was in my Makefile flags.
On Friday, September 17, 2021 at 3:11:53 PM UTC-7 Mouse wrote:
> Sorry, I've no idea what your makefile looks like, or how to convey the
> working flags to it.
>
> On Sep 17, 2021, at 16:39, Samyukta Yagati wrote:
>
> (I
On Fri, Sep 17, 2021 at 2:31 PM austin clifton wrote:
>
> Hey Jeff, thanks for the fast response!
>
> Yes, the encrypted sha from your AMD CPUs matches what I get on my Ryzen 7
> 3700X.
>
> The encrypted sha from the i7 is
> 8F16077454F8477594CAD4304126B0A6F30C8C4D2536E2441FFFD320656E1DF1.
On Thu, Sep 16, 2021 at 8:42 PM austin clifton wrote:
>
> I have an issue which I believe may be a bug. I followed the instructions
> from the "Bug Report" page on the cryptopp wiki and all tests in cryptest.exe
> are passing, so figured I should post here first and make sure it isn't a
>
Sorry, I've no idea what your makefile looks like, or how to convey the working
flags to it.
> On Sep 17, 2021, at 16:39, Samyukta Yagati wrote:
>
> (I currently have -l:libcryptopp.a in my LDFLAGS)
>
>> On Friday, September 17, 2021 at 1:38:31 PM UTC-7 Samyukta Yagati wrote:
>> Ah I see --
On Fri, Sep 17, 2021 at 4:32 AM Benjamin Schäfer wrote:
>
> Could you provide me your .exe to test it on my machine? I still don't get it
> and will try it on a fresh and clean machine also.
Sure. https://www.cryptopp.com/test_pem.exe.zip
I don't recall if that was built with VS2017 or VS2019.
Your exe works perfectly on my machine. I only have VS2019 on my machine
here, it says:
**
** Visual Studio 2019 Developer Command Prompt v16.10.1
** Copyright (c) 2021 Microsoft Corporation
On Fri, Sep 17, 2021 at 6:06 AM Jeffrey Walton wrote:
>
> ...
> I've got a Windows 10 VM somewhere. Let me see if I can get closer to
> v16.10.1.
I just tried with my Windows 10 VM. It was OK there, too.
Do you know how to do something like SSH access on Windows? I'll give
you an account on my
On Fri, Sep 17, 2021 at 5:11 AM Benjamin Schäfer wrote:
>
> Your exe works perfectly on my machine.
I don't know if that's good or bad...
> I only have VS2019 on my machine here, it says:
>
> **
> ** Visual Studio 2019
On Thu, Sep 16, 2021 at 8:42 PM austin clifton wrote:
>
> I have an issue which I believe may be a bug. I followed the instructions
> from the "Bug Report" page on the cryptopp wiki and all tests in cryptest.exe
> are passing, so figured I should post here first and make sure it isn't a
>
Could you provide me your .exe to test it on my machine? I still don't get
it and will try it on a fresh and clean machine also.
Benjamin Schäfer schrieb am Donnerstag, 16. September 2021 um 17:50:42
UTC+2:
> Well, I tested it on another machine at home, but the result remains the
> same :(
This is somehow ridiculus. I just set up a brand new VM with Win10, new
version. Also installed VS2019 Community. Nothing else, ran the upper
commands on the content of the 7zip archive and I still get the same
result. This can't be something with Intel vs. AMD, could it?
Your offer is
Hey Jeff, thanks for the fast response!
Yes, the encrypted sha from your AMD CPUs matches what I get on my Ryzen 7
3700X.
The encrypted sha from the i7 is
8F16077454F8477594CAD4304126B0A6F30C8C4D2536E2441FFFD320656E1DF1. That's
also the sha I get if I disable AVX on my Ryzen when compiling
FWIW, I have two more test results from Windows machines with Intel CPUs:
- i7 8750h
- i9 10980KK
Both are AVX-capable and produce the encrypted sha
6FBEE484EE64A2AB02235DDF29CA0B61EE3B811D227C2729836D3BD6161C9B18.
On Friday, September 17, 2021 at 11:31:48 AM UTC-7 austin clifton
Ah I see -- I'm using make with a custom makefile to build the source files
in my project, is there a way to translate this to flags in the makefile?
On Thursday, September 16, 2021 at 6:31:25 PM UTC-7 Mouse wrote:
> Say, you have a file that includes Crypto++ headers and needs linking with
>
18 matches
Mail list logo
