Yes, I encountered the same problem in my OS/400 port of OpenSSL 1.1.1.
Am 14.04.20 um 14:57 schrieb K Lengauer:
Hi Stephan,
Thank you for your quick response and also the link to your github issue. I
must have brushed over it when searching for similar issues, apologies.
Anyway, this seems to further confirm the issue(s) at hand...
Did you have any success or have
Hi Stephan,
Thank you for your quick response and also the link to your github issue. I
must have brushed over it when searching for similar issues, apologies.
Anyway, this seems to further confirm the issue(s) at hand...
Did you have any success or have you made any attempts at fixing this so
far
Hello Kevin,
Am 14.04.20 um 10:00 schrieb K Lengauer:
Dear all,
I want to add another issue that occurred to me and would appreciate some
input from others using zOS OpenSSL.
Calls like "ossl_isascii(c)" such as is done in "a_print.c" in method "int
ASN1_PRINTABLE_type(const unsigned char *s,
Dear all,
I want to add another issue that occurred to me and would appreciate some
input from others using zOS OpenSSL.
Calls like "ossl_isascii(c)" such as is done in "a_print.c" in method "int
ASN1_PRINTABLE_type(const unsigned char *s, int len)" lead to wrong behavior
for me on zOS if the in
First of all, thanks Michael Wojcik for your answer regarding the datasets. I
was able to get it working.
In the meantime I got the whole build done and am working on my tests. One
thing that I noticed recently is a wrong certificate X509 name output that
happens because of the following code sect
behalf of K Lengauer
Sent: Monday, March 9, 2020 10:29
To: openssl-users@openssl.org
Subject: Re: Problems porting Openssl 1.1.1d to zos.
Dear Patrick and co
I am currently stuck during my build with the following error:
IKJ56228I DATA SET CEE.SCEEBND2 NOT IN CATALOG OR CATALOG CAN NOT BE
ACCESS
Dear Patrick and co
I am currently stuck during my build with the following error:
IKJ56228I DATA SET CEE.SCEEBND2 NOT IN CATALOG OR CATALOG CAN NOT BE
ACCESSED
FSUM3052 The data definition name SYSLIB cannot be resolved. The data set
was not found. Ensure that data set name CEE.SCEEBND2 is s
On 3/4/20 5:31 PM, Salz, Rich via openssl-users wrote:
Perhaps someone should writeup and submit a "NOTES.zos" file to add?
I could put the contents of my previous mail in a NOTES.zos file,
if that would be considered helpful, knowing it works for us
at the moment and might not to the trick for
Perhaps someone should writeup and submit a "NOTES.zos" file to add?
Regarding perl, this is the version which works for us :
> perl -v
This is perl 5, version 24, subversion 0 (v5.24.0) built for os390
Copyright 1987-2016, Larry Wall
MVS (OS390) port by Mortice Kern Systems, 1997-1999
Perl may be copied only under the terms of either the Artistic License
or t
Thank you very much Patrick Steuer.
This certainly helps! I am now also in the progress of building OpenSSL and
come across missing "cflags" and the likes so with your config I can
hopefully save some time as well as verify what I already use.
I will also share my config in the near future once I
This is a very helpful post. Thank you.
We lacked Perl and had no clear path to getting it. Can't say this
deficiency caused our project to miss generous targets, but it certainly
contributed.
On Wed, Mar 4, 2020, 6:07 AM Patrick Steuer wrote:
> > I stumbled across this mails when looking for
I stumbled across this mails when looking for information regarding OpenSSL
on zOS. Currently, I am working on getting OpenSSL 1.1.1c running on zOS. So
far I created my own config "target" inside 10-main.conf based on the old
configuration that was used pre OpenSSL 1.1.0.
Still, I was not able
We recently abandoned our effort to port 1.1.1d to zos. Attempting to use
GSK now. Lack of a zos dev community is a hurdle.
M
On Mon, Mar 2, 2020, 6:04 AM K Lengauer wrote:
> Dear all,
>
> I stumbled across this mails when looking for information regarding OpenSSL
> on zOS. Currently, I am work
Dear all,
I stumbled across this mails when looking for information regarding OpenSSL
on zOS. Currently, I am working on getting OpenSSL 1.1.1c running on zOS. So
far I created my own config "target" inside 10-main.conf based on the old
configuration that was used pre OpenSSL 1.1.0.
Still, I was
> An error occurred during a connection to cafe.na.tibco.com:1802. SSL
> received a record with an incorrect Message Authentication Code. Error
> code: SSL_ERROR_BAD_MAC_READ
In case this error occurs with a chacha-poly cipher suite,
the following PR probably has a fix:
https://github.com/openssl
Please see also GitHub issue #4154, in particular
https://github.com/openssl/openssl/issues/4154#issuecomment-552838141
On 11.11.19 16:42, Wendell Nichols via openssl-users wrote:
Is there anyone on this group with experience with ebcdic platforms,
specifically zOS? I have built 1.1.1d on zOS and connections to my server work
for firefox 60 but not newer versions. I don't know exactly where the cut off
is o
Is there anyone on this group with experience with ebcdic platforms,
specifically zOS? I have built 1.1.1d on zOS and connections to my
server work for firefox 60 but not newer versions. I don't know exactly
where the cut off is or what they changed but current versions get an
HMAC error. I
20 matches
Mail list logo
