On Tue, Sep 21, 2021 at 10:40 AM Jeffrey Walton wrote:
> ...
> Typically you don't simply encrypt with an elliptic curve. Typically
> encryption using elliptic curves is a hybrid public key encryption
> scheme, like ECIES. In ECIES, you encrypt a bulk encryption key for a
> block cipher like AES u
On Tue, Sep 21, 2021 at 9:54 AM Benjamin Schäfer wrote:
>
> In the end it could be broke down to: I want to encrypt a std::string (the
> JSON Web Token) with the public key I created out of x and y with crypto++. I
> will take a look into OpenSSL and what I could do with that, but this project
In the end it could be broke down to: I want to encrypt a std::string (the
JSON Web Token) with the public key I created out of x and y with crypto++.
I will take a look into OpenSSL and what I could do with that, but this
project seems to get out of hand.
Jeffrey Walton schrieb am Dienstag, 21.
> How can I "convert" the public key I got from
>
> CryptoPP::ECDSA::PublicKey publicKey;
> publicKey.Initialize(CryptoPP::ASN1::brainpoolP256r1(), q);
>
> to the needed byte array. What do I have to use as initialisation vector? I'm
> no pro in crypto-algorithms but I have to use them for a s
Okay, I've read the articles, but somehow I don't know where to start. I
have to use the public key, generated out of x and y, algorith brainpool,
to encrypt a JWT. The JWT is generated with the cpp-jwt library and now I
really don't know what to do. How can I "convert" the public key I got from
On Fri, Sep 17, 2021 at 11:59 PM Benjamin Schäfer
wrote:
>
> 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 :)
This may help if
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 Fri
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 don
On Friday, September 17, 2021 at 11:26:25 AM UTC-4 skullm...@gmail.com
wrote:
> 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 sam
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 fantast
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 Developer
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 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.
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 :(
>
Well, I tested it on another machine at home, but the result remains the
same :(
Benjamin Schäfer schrieb am Donnerstag, 16. September 2021 um 13:37:01
UTC+2:
> I've put a 7z archive with all file I've used into the repository. On the
> CTL I switched the working directory to the extracted one
I've put a 7z archive with all file I've used into the repository. On the
CTL I switched the working directory to the extracted one. Then I ran the
following commands:
nmake /f cryptest.nmake
cl.exe /nologo /W4 /wd4231 /wd4511 /wd4156 /D_MBCS /Zi /TP /GR /EHsc
/DNDEBUG /D_NDEBUG /Oi /Oy /O2 /
I just don't get it. Somehow I can't force the platform toolkit to be used.
It remains at 140, when I compile with cl.exe. Going to the UI of VS2019,
building the library with toolset 142 and cryptolib with 142 produces those
results. When I open the CTL of VS2019 and run the cl.exe command, I g
On Thu, Sep 16, 2021 at 4:37 AM Benjamin Schäfer wrote:
> I've made the same steps with nmake and built the library. Then I did the
> same steps with my source file you mentioned, everything on the CTL that came
> with VS2019 (should make no difference).
>
> I uploaded the files here:
> https://
On Thu, Sep 16, 2021 at 4:37 AM Benjamin Schäfer wrote:
>
> First of all: Thank you for your help and your patience! I really appreciate
> that.
>
> I've made the same steps with nmake and built the library. Then I did the
> same steps with my source file you mentioned, everything on the CTL tha
First of all: Thank you for your help and your patience! I really
appreciate that.
I've made the same steps with nmake and built the library. Then I did the
same steps with my source file you mentioned, everything on the CTL that
came with VS2019 (should make no difference).
I uploaded the fi
On Thu, Sep 16, 2021 at 2:44 AM Benjamin Schäfer wrote:
>
> Ok, at least this gives me a ray of hope. So, to get rid of any interfering
> codelines, I did:
>
> - Start Visual Studio
> - New project (MFC Console, static linked MFC, Multibyte (unicode brings up
> the same result)
My Windows testi
Ok, at least this gives me a ray of hope. So, to get rid of any interfering
codelines, I did:
- Start Visual Studio
- New project (MFC Console, static linked MFC, Multibyte (unicode brings up
the same result)
Full code:
#include
#include
#include "cryptlib.h"
#include "filters.h"
#include "ec
On Wed, Sep 15, 2021 at 12:01 PM Jeffrey Walton wrote:
>
> > But my problem afterward (which I didn't mention to this point, because I
> > thought it will solve itself when I have a correct y-coordinate) is, that
> > if I try to save this public key as PEM, I only get
> >
> > -BEGIN PUBLIC K
> But my problem afterward (which I didn't mention to this point, because I
> thought it will solve itself when I have a correct y-coordinate) is, that if
> I try to save this public key as PEM, I only get
>
> -BEGIN PUBLIC KEY-
> MFowMFow-END PUBLIC KEY-
>
> as result. This was a
Ok, I was able to find out, why I get a wrong y coordinate (leading zeros
in Hex-String brings up this crap). Validation seems to be okay.
But my problem afterward (which I didn't mention to this point, because I
thought it will solve itself when I have a correct y-coordinate) is, that
if I tr
26 matches
Mail list logo
