The change in itself is quite trivial, just editing the dgst manpage to
remove the reference to pkeyutl.
The issue has more instructions and the idea was to use it as a way to let
a new developer familiarize with OpenSSL contributing guidelines and
process.
Another user already started working
Sure, I can help.
It's my pleasure to help with the project.
Since you have opened an issue. Then what should I do?
Nicola Tuveri 于2020年4月24日周五 下午11:17写道：
> That's right! Thanks Viktor for pointing that out!!
>
> I just opened an issue to track this:
>
That's right! Thanks Viktor for pointing that out!!
I just opened an issue to track this:
https://github.com/openssl/openssl/issues/11633
We warmly welcome contributions from everyone and this could be a good
first issue to work on: Yang (as the person that started this thread and
noticed the
On Thu, Apr 23, 2020 at 11:23:35AM +0200, Nicola Tuveri wrote:
> > On 22/04/2020 18:12, Viktor Dukhovni wrote:
> > > sadly the
> > > EVP_PKEY_METHOD for ed25519 has a NULL sign() member, instead, somewhat
> > > ironically, it has a digestsign() method. This is presumably to
> > > distinguish
On Thu, 23 Apr 2020 at 11:02, Matt Caswell wrote:
>
>
> On 22/04/2020 18:12, Viktor Dukhovni wrote:
> > sadly the
> > EVP_PKEY_METHOD for ed25519 has a NULL sign() member, instead, somewhat
> > ironically, it has a digestsign() method. This is presumably to
> > distinguish between the pure and
On 22/04/2020 18:12, Viktor Dukhovni wrote:
> sadly the
> EVP_PKEY_METHOD for ed25519 has a NULL sign() member, instead, somewhat
> ironically, it has a digestsign() method. This is presumably to
> distinguish between the pure and prehash variants. Therefore, presently
> pkeyutl(1) indeed
I have to correct myself, in `master` (and very soon in the 3.0.0 alpha1
release) `pkeyutl` already has support for sign/verify files with Ed25519
keys.
```
λ /tmp/test25519/ ### Ensure OpenSSL dev build is in use for this shell
λ /tmp/test25519/ which openssl ; openssl version
On Wed, Apr 22, 2020 at 01:27:03PM +0200, Nicola Tuveri wrote:
> Unfortunately at the moment the command line utilities do not support
> generating Ed25519 or Ed448 signatures for files.
>
> The reason is that in OpenSSL at the moment we only support pureEd25519,
> which does not prehash the
Unfortunately at the moment the command line utilities do not support
generating Ed25519 or Ed448 signatures for files.
The reason is that in OpenSSL at the moment we only support pureEd25519,
which does not prehash the "message" to be signed, as Viktor mentioned
before.
With other prehashed
Hello, I checked the pkeyutl manpage, but it says that
-The Ed25519 and Ed448 signature algorithms are not supported by this
utility. They accept non-hashed input, but this utility can only be used to
sign hashed input.
So what command should I use to simply sign or encrypt a message with
ed25519
On Wed, Apr 22, 2020 at 11:46:16AM +0800, yang berlin wrote:
> Wow, thanks for the detailed reply!
> Actually I am a master student and my teacher wants me to figure out the
> use of ed25519. So I went to see openssl.
> I thought ed25519 can sign messages so I tried the dgst command. Now I know
>
Wow, thanks for the detailed reply!
Actually I am a master student and my teacher wants me to figure out the
use of ed25519. So I went to see openssl.
I thought ed25519 can sign messages so I tried the dgst command. Now I know
that I was wrong.
Anyway, thank you again!
Viktor Dukhovni
On Tue, Apr 21, 2020 at 05:48:19PM +0800, yang berlin wrote:
> I want to use ed25519 in openssl.
Why? What actual real-world purpose do you have for ed25519?
> The problem I met is: I can use "speed ed25519" to test the speed of
> ed25519, but when I use "dgst -ed25519", it tells me that
13 matches
Mail list logo
