Hi,
Implementation of common option processing for OpenSSL commands broke
ENGINE key
format.
The patches attached to this email are only for tested command.
1) dgst command (see 0003-dgst-cmd-restore-keys-from-engine.patch)
Key form is described as any but value type of input ('<') is too
Salz, Rich via RT wrote:
> I don't know that I would call it a regression, but rather a difference. :)
> I'll fix the summary but not the old uncommon behavior.
Unlike other commands engine is flexible and documented behaviour (see
previous post with quoted text).
As result in samples first is
The patch is wrong, this one is better.
diff --git a/apps/engine.c b/apps/engine.c
index c373df5..ab663ea 100644
--- a/apps/engine.c
+++ b/apps/engine.c
@@ -312,12 +312,17 @@ int engine_main(int argc, char **argv)
BIO *out;
const char *indent = " ";
OPTION_CHOICE o;
- char *prog;
+ char *prog,
Does this diff fix it?
; g diff apps/engine.c
diff --git a/apps/engine.c b/apps/engine.c
index c373df5..3c0ff96 100644
--- a/apps/engine.c
+++ b/apps/engine.c
@@ -312,12 +312,17 @@ int engine_main(int argc, char **argv)
BIO *out;
const char *indent = " ";
OPTION_CHOICE o;
-
Does this diff fix it?
; g diff apps/engine.c
diff --git a/apps/engine.c b/apps/engine.c
index c373df5..3c0ff96 100644
--- a/apps/engine.c
+++ b/apps/engine.c
@@ -312,12 +312,17 @@ int engine_main(int argc, char **argv)
BIO *out;
const char *indent = " ";
OPTION_CHOICE o;
-
I have been using the DJGPP port of OpenSSL for a couple of years and I would
like to propose some fixes and improvements. No one of the proporsed changes
have impact on any other port. I supply two patches, one for today's
OpenSSL_1_0_1-stable
and one for today's openssl-OpenSSL_1_0_2-stable.
Hi,
Lets assume i have a RSA public key file (xyz_file.pem) and cipher text that
is encrypted using same RSA public key file (xyz_file.pem) now i want to
decrypt the cipher text using same RSA public key file (xyz_file.pem).
Ya i know its not a correct way of encryption and decryption concept.
