Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-22 Thread Richard Levitte 
In message <20151222101434.116043c95betf...@www.polarhome.com> on Tue, 22 Dec 
2015 10:14:34 +0100, Zoltan Arpadffy  said:

zoli> Thank you Richard.
zoli> 
zoli> What "slowly" means? Will you be able to commit the OpenVMS build
zoli> scripts before the 1.1.0's release?

Yes.  At the latest, it should be fully present in alpha3.  See the
end of https://openssl.org/policies/releasestrat.html for planned
release dates.

zoli> Do you need some help with coding, testing?

Yes please.

zoli> Should I try to repair the old build scripts?

No.  Thanks for the reminder, they should all go.

My plan for "new and shiny" is based on perl, running Configure and
have it generate a top level descrip.mms.  Requirements will be a perl
installation (minimum version 5.12) plus Text::Template.

Cheers,
Richard

-- 
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-22 Thread Richard Levitte 
In message <20151222111022.44086nc6688vq...@www.polarhome.com> on Tue, 22 Dec 
2015 11:10:22 +0100, Zoltan Arpadffy  said:

zoli> Richard,
zoli> 
zoli> > My plan for "new and shiny" is based on perl, running Configure and
zoli> > have it generate a top level descrip.mms.  Requirements will be a perl
zoli> > installation (minimum version 5.12) plus Text::Template.
zoli> 
zoli> Thank you for the information.
zoli> 
zoli> I am aware that having perl installed on a modern operating system is
zoli> not a very tough requirement - but experience shows that external
zoli> dependencies often cause problems on OpenVMS.

For perl, it's not that hard: http://sourceforge.net/projects/vmsperlkit/files/

zoli> I would suggest to include/commit the perl scripts into the OpenSSL
zoli> source code (for developers convenience only), but they should be ran
zoli> and commit the OpenVMS descrip.mms build files matching the current
zoli> code base - as a step in the OpenSSL source code release process.

I was thinking that it might be a good idea to bundle Text::Template,
if that's what you meant.  We try to make sure to only use core perl
modules, but considering there's no template module among the core
ones and I hardly want to reinvent the wheel, I might make an
exception there.  I haven't decided, though, it's not like it's very
hard to do a "cpan download Text::Template" and then install it
(unfortunately, "cpan install Text::Template" doesn't work because
there's a lack of action lines in the test: target it its Makefile,
and mms isn't too happy about that...)

zoli> Unix make files are also made in forehand. Right?

Nope.

zoli> What is your opinion about this?

Considering there's Alpha, IA64 and VSI is building VMS for x86_64,
and let's not forget pointer size options, the different possible
configurations is already not a small number, and will only increase.
How many variants of descrip.mms did you want?

So, uhmm, nah.  Frankly, it's time (it's been time for long) for the
OpenVMS community to catch up with the rest of the world re open
source building...  or for someone to produce OpenSSL install kits
(it's possible that the vms-ports effort will do so, possibly by yours
truly... no promises, though).

zoli> > zoli> Do you need some help with coding, testing?
zoli> >
zoli> > Yes please.
zoli> 
zoli> Please, let me know how... or should I just wait for the make files
zoli> release?

I'll have a branch in g...@github.com:levitte/openssl.git
I'll get back when it starts going live.

Cheers,
Richard

-- 
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-22 Thread Zoltan Arpadffy 

Thank you Richard.

What "slowly" means? Will you be able to commit the OpenVMS build  
scripts before the 1.1.0's release?


Do you need some help with coding, testing?
Should I try to repair the old build scripts?

Thanks,
Z



Quoting Richard Levitte <levi...@openssl.org>:

The building scripts are not at all updated, it's beyond repair. I'm  
(slowly) working on a new solution that doesn't require the separate  
update hell...


Cheers
Richard

Zoltan Arpadffy <z...@polarhome.com> skrev: (21 december 2015 20:36:13 CET)

Hi,

I am sorry, but because of the relocation of the header files the 1.1.0
does
not build on OpenVMS.
Please, allow some time to fix the OpenVMS build scripts.

Thank you.
Regards,
Z

-Original Message-
From: openssl-dev [mailto:openssl-dev-boun...@openssl.org] On Behalf Of
OpenSSL
Sent: den 10 december 2015 16:02
To: OpenSSL Developer ML; OpenSSL User Support ML; OpenSSL Announce ML
Subject: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


  OpenSSL version 1.1.0 pre release 1 (alpha)
  ===

  OpenSSL - The Open Source toolkit for SSL/TLS
  http://www.openssl.org/

OpenSSL 1.1.0 is currently in alpha. OpenSSL 1.1.0 pre release 1 has
now
  been made available. For details of changes and known issues see the
  release notes at:

   http://www.openssl.org/news/openssl-1.1.0-notes.html

  Note: This OpenSSL pre-release has been provided for testing ONLY.
  It should NOT be used for security critical purposes.

 The alpha release is available for download via HTTP and FTP from the
following master locations (you can find the various FTP mirrors under
  http://www.openssl.org/source/mirror.html):

* http://www.openssl.org/source/
* ftp://ftp.openssl.org/source/

  The distribution file name is:

   o openssl-1.1.0-pre1.tar.gz
 Size: 4990889
 SHA1 checksum: a058b999e17e0c40988bd7b9b280c9876f62684e
 SHA256 checksum:
79da49c38464a19d1b328c2f4a3661849bd2eb3d54a37fdb6a56d9b8a18e87bd

  The checksums were calculated using the following commands:

   openssl sha1 openssl-1.1.0-pre1.tar.gz
   openssl sha256 openssl-1.1.0-pre1.tar.gz

 Please download and check this alpha release as soon as possible. Bug
reports
  should go to r...@openssl.org. Please check the release notes
  and mailing lists to avoid duplicate reports of known issues.

  Yours,

  The OpenSSL Project Team.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJWaYrRAAoJENnE0m0OYESRh5gIAJ8WrkPPV8CW2xWmtyIjAxpz
7FvvpxBWHaBgJcCrvNomh2JJupXa+enWCTsskIyH0+FtS85VeOKNvQg68xbCOvLl
I0dWxMNb8SCxuagvEje8xGEnf8by8pZdYaK8ERASlNoGVIgN8CwppiKnY8c1yRYn
Ti0dUZLyVZvT5Qm2Q3k4pOvfS/+rvFjHiuUllFzfHlp6mdk4573w5eneoTINQvRK
OC8iAnSiINQWQvuiavLVIgw7VFBD1WC2iKWuSA3+31YuM8CUpvbbnJHh2QUfGkIw
oNTkflxgQJhk/txwqvCSzZsVddhvQLZtiRZYQcG4WUuskygCENeieJGPOXN6ioI=
=LY4X
-END PGP SIGNATURE-
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev





---
WebMail, polarhome.com

___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-22 Thread Richard Levitte 
In message <20151222122349.916552ojkzhe5...@www.polarhome.com> on Tue, 22 Dec 
2015 12:23:49 +0100, Zoltan Arpadffy  said:

zoli> Hi,
zoli> 
zoli> > zoli> I am aware that having perl installed on a modern operating
zoli> > system is
zoli> > zoli> not a very tough requirement - but experience shows that
zoli> > external
zoli> > zoli> dependencies often cause problems on OpenVMS.
zoli> >
zoli> > For perl, it's not that hard:
zoli> > http://sourceforge.net/projects/vmsperlkit/files/
zoli> 
zoli> > (unfortunately, "cpan install Text::Template" doesn't work because
zoli> > there's a lack of action lines in the test: target it its Makefile,
zoli> > and mms isn't too happy about that...)
zoli> 
zoli> > So, uhmm, nah.  Frankly, it's time (it's been time for long) for the
zoli> > OpenVMS community to catch up with the rest of the world re open
zoli> > source building...
zoli> 
zoli> Please, do not misunderstand me - I am on your side and I would be the
zoli> most happy if that would work.
zoli> 
zoli> But there is a problem:
zoli> The files currently featured are kits for installing
zoli> Perl 5.22.1 on OpenVMS Alpha or Itanium v8.3 and later. (from the home
zoli> page)... but many OpenVMS systems are not on v8.3 yet.

There are older kits in the Archive folder.  I don't know for the
moment what VMS version they're built for.

zoli> This is not good - I know. But this is a fact we need to face when we
zoli> develop for this system.

That's tough, unfortunately...  I've only access to a V8.4 cluster
(Alpha and IA64), so I don't know how to help you further.  Of course,
there's the option to build perl from source, which isn't very hard at
all (I've done so a few times).

zoli> One descript.mms file would be enough. Thank you for asking :)
zoli> MMS/MMK accepts parameters that could be used within the descript file
zoli> making possible the different choices - if it is written on that way,
zoli> especially that architecture and some other parameters can be
zoli> successfully guessed within the MMS file.

Well, the aim is to have a common structure to build from on all
architectures we claim to support.  You've seen for yourself how the
scripts for VMS builds were lagging behind, and quite frankly, it's
hellish to keep them up to date (I've completely dropped the ball for
1.1).  That's not something I'm willing to have us do all over again.

zoli> > zoli> > zoli> Do you need some help with coding, testing?
zoli> >
zoli> > I'll have a branch in g...@github.com:levitte/openssl.git
zoli> > I'll get back when it starts going live.
zoli> 
zoli> Thank you, Richard.
zoli> I am looking forward to help you.

Thanks :-)

-- 
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-22 Thread Zoltan Arpadffy 

Hi,


zoli> > (unfortunately, "cpan install Text::Template" doesn't work because
zoli> > there's a lack of action lines in the test: target it its Makefile,
zoli> > and mms isn't too happy about that...)



That's tough, unfortunately...  I've only access to a V8.4 cluster
(Alpha and IA64), so I don't know how to help you further.  Of course,
there's the option to build perl from source, which isn't very hard at
all (I've done so a few times).


I do have access to VAX, Alpha and IA64 architectures... on range of  
7.3 to 8.3 OpenVMS versions.

Also I do have functional perl installed on them.
I am not the problem here, but ordinary developers that work on an old  
system developing for a legacy program and do not have SYSTEM rights -  
what is the common case.

The build solution should be designed to be usable by those developers too.


Well, the aim is to have a common structure to build from on all
architectures we claim to support.  You've seen for yourself how the
scripts for VMS builds were lagging behind, and quite frankly, it's
hellish to keep them up to date (I've completely dropped the ball for
1.1).  That's not something I'm willing to have us do all over again.


Absolutely agree with you. This is the way forward.

May I ask you, if the new build will cover the long names issue (  
symhacks.h ) too?


Thanks,
Z

---
WebMail, polarhome.com

___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-22 Thread Richard Levitte 
In message <20151222134741.72034a0b79m0z...@www.polarhome.com> on Tue, 22 Dec 
2015 13:47:41 +0100, Zoltan Arpadffy  said:

zoli> Hi,
zoli> 
zoli> > zoli> > (unfortunately, "cpan install Text::Template" doesn't work
zoli> > because
zoli> > zoli> > there's a lack of action lines in the test: target it its
zoli> > Makefile,
zoli> > zoli> > and mms isn't too happy about that...)
zoli> 
zoli> > That's tough, unfortunately...  I've only access to a V8.4 cluster
zoli> > (Alpha and IA64), so I don't know how to help you further.  Of course,
zoli> > there's the option to build perl from source, which isn't very hard at
zoli> > all (I've done so a few times).
zoli> 
zoli> I do have access to VAX, Alpha and IA64 architectures... on range of
zoli> 7.3 to 8.3 OpenVMS versions.
zoli> Also I do have functional perl installed on them.
zoli> I am not the problem here, but ordinary developers that work on an old
zoli> system developing for a legacy program and do not have SYSTEM rights -
zoli> what is the common case.
zoli> The build solution should be designed to be usable by those developers
zoli> too.

Is perl still that uncommon on VMS?  I'm sorry to say that's gonna be
tough, then.  Just as an example, the old test scripts are gone, and
have been replaced with Test::More / Test::Harness recipes, and I'm
pretty sure VMS devs who're building OpenSSL are just as eager to run
the test scripts as anyone.

I could argue that for a developer to work, he/she needs a functional
development environment.  In this day and age, that should include
perl.  Pressure on the sysadmin!  (having been a VMS sysadmin, I'm
saying that very much toungue in cheak ;-))

zoli> > Well, the aim is to have a common structure to build from on all
zoli> > architectures we claim to support.  You've seen for yourself how the
zoli> > scripts for VMS builds were lagging behind, and quite frankly, it's
zoli> > hellish to keep them up to date (I've completely dropped the ball for
zoli> > 1.1).  That's not something I'm willing to have us do all over again.
zoli> 
zoli> Absolutely agree with you. This is the way forward.

Good :-)

zoli> May I ask you, if the new build will cover the long names issue (
zoli> symhacks.h ) too?

It's been pointed out to me by the vms-ports folks that it should be
possible to solve using the compiler's "#pragma names shortened"
rather than maintaining symhacks...  Then, it's just a matter of doing
the same thing manually when producing the SYMBOL_VECTOR for a
shareable image.  I'm also thinking that "#pragma names as_is" should
be norm and that we could produce upper case aliases in SYMBOL_VECTOR
(you know how that's done, right?).  Does that sound like a way
forward to you?

Cheers,
Richard

-- 
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-22 Thread Zoltan Arpadffy 

Hi,


zoli> May I ask you, if the new build will cover the long names issue (
zoli> symhacks.h ) too?

It's been pointed out to me by the vms-ports folks that it should be
possible to solve using the compiler's "#pragma names shortened"
rather than maintaining symhacks...  Then, it's just a matter of doing
the same thing manually when producing the SYMBOL_VECTOR for a
shareable image.  I'm also thinking that "#pragma names as_is" should
be norm and that we could produce upper case aliases in SYMBOL_VECTOR
(you know how that's done, right?).  Does that sound like a way
forward to you?


It is not my decision, but I don't like either of these approaches.

The code itself needs to be written that it is as much as possible portable.

It is not impossible to maintain a code base that uses up to 32 char  
long function names - without losing the readability of the code.
I agree that it requires some extra focus from the developers side -  
but coding a security software needs that (and even more) focus anyway.


Thanks,
Z

---
WebMail, polarhome.com

___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-22 Thread Salz, Rich 
> It is not impossible to maintain a code base that uses up to 32 char long
> function names - without losing the readability of the code.
> I agree that it requires some extra focus from the developers side - but
> coding a security software needs that (and even more) focus anyway.

Yes, but symbol names are a distraction from the main focus of security.

Many of the >32 char names are auto-generated via #define's an ASN1 parsing.  
Most of the others follow common convention used elsewhere in the code. 
Consistency is more important than support for old platforms :)
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-22 Thread Richard Levitte 
In message <20151222153437.192023un5jh69...@www.polarhome.com> on Tue, 22 Dec 
2015 15:34:37 +0100, Zoltan Arpadffy  said:

zoli> Hi,
zoli> 
zoli> > zoli> May I ask you, if the new build will cover the long names issue
zoli> > (
zoli> > zoli> symhacks.h ) too?
zoli> >
zoli> > It's been pointed out to me by the vms-ports folks that it should be
zoli> > possible to solve using the compiler's "#pragma names shortened"
zoli> > rather than maintaining symhacks...  Then, it's just a matter of doing
zoli> > the same thing manually when producing the SYMBOL_VECTOR for a
zoli> > shareable image.  I'm also thinking that "#pragma names as_is" should
zoli> > be norm and that we could produce upper case aliases in SYMBOL_VECTOR
zoli> > (you know how that's done, right?).  Does that sound like a way
zoli> > forward to you?
zoli> 
zoli> It is not my decision, but I don't like either of these approaches.
zoli> 
zoli> The code itself needs to be written that it is as much as possible
zoli> portable.

In the end, this is a LINKER vs rest of the world issue.  In this day
and age, the 31 char limitation is a bit aged, and LINKER should
really be updated to allow longer symbol names.  If nothing else, C++
symbol munging would require it.  I certainly hope VSI receives the
messages and starts dealing with it.

Either way, we're dealing with C, with case sensitive symbols and
symbols longer than 31 chars.  The names pragmas are helpful
portability tools, the smoothest at this point is to put them to good
use.

zoli> It is not impossible to maintain a code base that uses up to 32 char
zoli> long function names - without losing the readability of the code.
zoli> I agree that it requires some extra focus from the developers side -
zoli> but coding a security software needs that (and even more) focus
zoli> anyway.

That can certainly be argued...  Again, that's more of a LINKER issue
than anything else.

Cheers,
Richard

-- 
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-22 Thread Richard Levitte 
In message 
 on Tue, 
22 Dec 2015 14:41:16 +, "Salz, Rich"  said:

rsalz> Consistency is more important than support for old platforms :)

Side note: I'd like it if we skipped the age slurs, especially since
we're commonly working on operating systems that come from a decade
more history than VMS. ;-)

Cheers,
Richard

-- 
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-21 Thread Zoltan Arpadffy 
Hi,

I am sorry, but because of the relocation of the header files the 1.1.0 does
not build on OpenVMS.
Please, allow some time to fix the OpenVMS build scripts.

Thank you.
Regards,
Z 

-Original Message-
From: openssl-dev [mailto:openssl-dev-boun...@openssl.org] On Behalf Of
OpenSSL
Sent: den 10 december 2015 16:02
To: OpenSSL Developer ML; OpenSSL User Support ML; OpenSSL Announce ML
Subject: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


   OpenSSL version 1.1.0 pre release 1 (alpha)
   ===

   OpenSSL - The Open Source toolkit for SSL/TLS
   http://www.openssl.org/

   OpenSSL 1.1.0 is currently in alpha. OpenSSL 1.1.0 pre release 1 has now
   been made available. For details of changes and known issues see the
   release notes at:

http://www.openssl.org/news/openssl-1.1.0-notes.html

   Note: This OpenSSL pre-release has been provided for testing ONLY.
   It should NOT be used for security critical purposes.

   The alpha release is available for download via HTTP and FTP from the
   following master locations (you can find the various FTP mirrors under
   http://www.openssl.org/source/mirror.html):

 * http://www.openssl.org/source/
 * ftp://ftp.openssl.org/source/

   The distribution file name is:

o openssl-1.1.0-pre1.tar.gz
  Size: 4990889
  SHA1 checksum: a058b999e17e0c40988bd7b9b280c9876f62684e
  SHA256 checksum:
79da49c38464a19d1b328c2f4a3661849bd2eb3d54a37fdb6a56d9b8a18e87bd

   The checksums were calculated using the following commands:

openssl sha1 openssl-1.1.0-pre1.tar.gz
openssl sha256 openssl-1.1.0-pre1.tar.gz

   Please download and check this alpha release as soon as possible. Bug
reports
   should go to r...@openssl.org. Please check the release notes
   and mailing lists to avoid duplicate reports of known issues.

   Yours,

   The OpenSSL Project Team.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJWaYrRAAoJENnE0m0OYESRh5gIAJ8WrkPPV8CW2xWmtyIjAxpz
7FvvpxBWHaBgJcCrvNomh2JJupXa+enWCTsskIyH0+FtS85VeOKNvQg68xbCOvLl
I0dWxMNb8SCxuagvEje8xGEnf8by8pZdYaK8ERASlNoGVIgN8CwppiKnY8c1yRYn
Ti0dUZLyVZvT5Qm2Q3k4pOvfS/+rvFjHiuUllFzfHlp6mdk4573w5eneoTINQvRK
OC8iAnSiINQWQvuiavLVIgw7VFBD1WC2iKWuSA3+31YuM8CUpvbbnJHh2QUfGkIw
oNTkflxgQJhk/txwqvCSzZsVddhvQLZtiRZYQcG4WUuskygCENeieJGPOXN6ioI=
=LY4X
-END PGP SIGNATURE-
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-21 Thread Richard Levitte 
The building scripts are not at all updated, it's beyond repair. I'm (slowly) 
working on a new solution that doesn't require the separate update hell... 

Cheers 
Richard 

Zoltan Arpadffy <z...@polarhome.com> skrev: (21 december 2015 20:36:13 CET)
>Hi,
>
>I am sorry, but because of the relocation of the header files the 1.1.0
>does
>not build on OpenVMS.
>Please, allow some time to fix the OpenVMS build scripts.
>
>Thank you.
>Regards,
>Z 
>
>-Original Message-
>From: openssl-dev [mailto:openssl-dev-boun...@openssl.org] On Behalf Of
>OpenSSL
>Sent: den 10 december 2015 16:02
>To: OpenSSL Developer ML; OpenSSL User Support ML; OpenSSL Announce ML
>Subject: [openssl-dev] OpenSSL version 1.1.0 pre release 1 published
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>
>   OpenSSL version 1.1.0 pre release 1 (alpha)
>   ===
>
>   OpenSSL - The Open Source toolkit for SSL/TLS
>   http://www.openssl.org/
>
>OpenSSL 1.1.0 is currently in alpha. OpenSSL 1.1.0 pre release 1 has
>now
>   been made available. For details of changes and known issues see the
>   release notes at:
>
>http://www.openssl.org/news/openssl-1.1.0-notes.html
>
>   Note: This OpenSSL pre-release has been provided for testing ONLY.
>   It should NOT be used for security critical purposes.
>
>  The alpha release is available for download via HTTP and FTP from the
> following master locations (you can find the various FTP mirrors under
>   http://www.openssl.org/source/mirror.html):
>
> * http://www.openssl.org/source/
> * ftp://ftp.openssl.org/source/
>
>   The distribution file name is:
>
>o openssl-1.1.0-pre1.tar.gz
>  Size: 4990889
>  SHA1 checksum: a058b999e17e0c40988bd7b9b280c9876f62684e
>  SHA256 checksum:
>79da49c38464a19d1b328c2f4a3661849bd2eb3d54a37fdb6a56d9b8a18e87bd
>
>   The checksums were calculated using the following commands:
>
>openssl sha1 openssl-1.1.0-pre1.tar.gz
>openssl sha256 openssl-1.1.0-pre1.tar.gz
>
>  Please download and check this alpha release as soon as possible. Bug
>reports
>   should go to r...@openssl.org. Please check the release notes
>   and mailing lists to avoid duplicate reports of known issues.
>
>   Yours,
>
>   The OpenSSL Project Team.
>
>-BEGIN PGP SIGNATURE-
>Version: GnuPG v1
>
>iQEcBAEBAgAGBQJWaYrRAAoJENnE0m0OYESRh5gIAJ8WrkPPV8CW2xWmtyIjAxpz
>7FvvpxBWHaBgJcCrvNomh2JJupXa+enWCTsskIyH0+FtS85VeOKNvQg68xbCOvLl
>I0dWxMNb8SCxuagvEje8xGEnf8by8pZdYaK8ERASlNoGVIgN8CwppiKnY8c1yRYn
>Ti0dUZLyVZvT5Qm2Q3k4pOvfS/+rvFjHiuUllFzfHlp6mdk4573w5eneoTINQvRK
>OC8iAnSiINQWQvuiavLVIgw7VFBD1WC2iKWuSA3+31YuM8CUpvbbnJHh2QUfGkIw
>oNTkflxgQJhk/txwqvCSzZsVddhvQLZtiRZYQcG4WUuskygCENeieJGPOXN6ioI=
>=LY4X
>-END PGP SIGNATURE-
>___
>openssl-dev mailing list
>To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
>
>___
>openssl-dev mailing list
>To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

[openssl-dev] OpenSSL version 1.1.0 pre release 1 published

2015-12-10 Thread OpenSSL 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


   OpenSSL version 1.1.0 pre release 1 (alpha)
   ===

   OpenSSL - The Open Source toolkit for SSL/TLS
   http://www.openssl.org/

   OpenSSL 1.1.0 is currently in alpha. OpenSSL 1.1.0 pre release 1 has now
   been made available. For details of changes and known issues see the
   release notes at:

http://www.openssl.org/news/openssl-1.1.0-notes.html

   Note: This OpenSSL pre-release has been provided for testing ONLY.
   It should NOT be used for security critical purposes.

   The alpha release is available for download via HTTP and FTP from the
   following master locations (you can find the various FTP mirrors under
   http://www.openssl.org/source/mirror.html):

 * http://www.openssl.org/source/
 * ftp://ftp.openssl.org/source/

   The distribution file name is:

o openssl-1.1.0-pre1.tar.gz
  Size: 4990889
  SHA1 checksum: a058b999e17e0c40988bd7b9b280c9876f62684e
  SHA256 checksum: 
79da49c38464a19d1b328c2f4a3661849bd2eb3d54a37fdb6a56d9b8a18e87bd

   The checksums were calculated using the following commands:

openssl sha1 openssl-1.1.0-pre1.tar.gz
openssl sha256 openssl-1.1.0-pre1.tar.gz

   Please download and check this alpha release as soon as possible. Bug reports
   should go to r...@openssl.org. Please check the release notes
   and mailing lists to avoid duplicate reports of known issues.

   Yours,

   The OpenSSL Project Team.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJWaYrRAAoJENnE0m0OYESRh5gIAJ8WrkPPV8CW2xWmtyIjAxpz
7FvvpxBWHaBgJcCrvNomh2JJupXa+enWCTsskIyH0+FtS85VeOKNvQg68xbCOvLl
I0dWxMNb8SCxuagvEje8xGEnf8by8pZdYaK8ERASlNoGVIgN8CwppiKnY8c1yRYn
Ti0dUZLyVZvT5Qm2Q3k4pOvfS/+rvFjHiuUllFzfHlp6mdk4573w5eneoTINQvRK
OC8iAnSiINQWQvuiavLVIgw7VFBD1WC2iKWuSA3+31YuM8CUpvbbnJHh2QUfGkIw
oNTkflxgQJhk/txwqvCSzZsVddhvQLZtiRZYQcG4WUuskygCENeieJGPOXN6ioI=
=LY4X
-END PGP SIGNATURE-
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev