Manually using yum on Fedora.
regards
On 30 June 2014 22:24, Rich Salz via RT r...@openssl.org wrote:
Were these done manually or were there scripts?
If scripts, we'd like to see them as we're thinking about the POD format.
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
Personnally,
and although I am not at all a M$ fan, really not at all,
I would not consider XP or any win32-like platform since XP as outdated,
as, finally, what openssl needs from the platform ?
some standard-C lib, bsd-like sockets, and some (a very few) posix
services or equivalents.
Some
Hello Rich
I just need to build a windows version of openssl, I just work with
mingw to test a new autotest (source code test generation) approach.
If for some reason the distrib is to be abandonned, let me know, I'll
change, no pb.
Thanks
Le 01.07.2014 05:24, Salz, Rich a écrit :
Hi
I use a WIndows Mingw config, with default parameters
perl .\Configure mingw
make depend
make
make tests
Nothing special, in fact.
The make command fails with the errors below
The snapshots for versions 1.0.x are ok but not openssl-SNAP-20140630
I really don't understand why
Bye
Le
That was my main motivation to subscribe to the mailing lists and drop
here a line.
Yes, as I wrote at the beginning I would like to contribute and help to
make the website more modern and thats why I would like to see it on GitHub.
Thanks, for your reply Dr. Henson. I'll stick with the hourly snapshots from
now on.
J. Jeff Clemmer
IT Specialist
Phone: 434-980-7525
Email: john.j.clemmer4@mail.mil
-Original Message-
From: Stephen Henson via RT [mailto:r...@openssl.org]
Sent: Saturday, June 28, 2014 1:58 PM
Thank you, Mr. Roeckx.
J.J. Clemmer
-Original Message-
From: Kurt Roeckx via RT [mailto:r...@openssl.org]
Sent: Saturday, June 28, 2014 2:43 PM
To: Clemmer, John J CIV (US)
Cc: openssl-dev@openssl.org
Subject: Re: [openssl.org #3413] OpenSSL Bug Report Submission - related to
#3376
On
Manually using yum on Fedora.
regards
On 30 June 2014 22:24, Rich Salz via RT r...@openssl.org wrote:
Were these done manually or were there scripts?
If scripts, we'd like to see them as we're thinking about the POD format.
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
Hi,
My project is currently using OpenSSL-1.0.1g package and we are monitoring
the security vulenrabilities being reported to this package. I would like
to know the status of official fix for CVE-2014-0198 bug. Is this fixed
in OpenSSL-1.0.1h version ?
The below link does not list CVE-2014-0198,
I've been trying to figure out why my make depend differs from other
developers, and why it appears to be wrong.
For example, apps/dsa.o depends, according to makedepend, on dh.o, but
with the standard developer flags ($gcc_devteam_warn) it should not.
AFAICS, makedepend gets passed the right
On 1 July 2014 06:52, Zoltan Arpadffy z...@polarhome.com wrote:
Hi,
I see that Rich is doing a fantastic job by cleaning up the backlog...
I absolutely agree that very old releases cannot be supported, but what about
the platforms?
I thought until now, that as long there are developers who
On Tue, Jul 1, 2014 at 3:03 PM, Manjesh HS via RT r...@openssl.org wrote:
Hi,
My project is currently using OpenSSL-1.0.1g package and we are monitoring
the security vulenrabilities being reported to this package. I would like
to know the status of official fix for CVE-2014-0198 bug. Is this
In case people haven't noticed, Google has announced a reward program
for this (last year, in fact):
https://www.google.com/about/appsecurity/patch-rewards/
__
OpenSSL Project
Hi David,
It looks like the new feature of supporting unix domain sockets missed
some #ifndef NO_SYS_UN_H statements in s_client.c.
Please find attached the patch for Configure (to add the NON_SYS_UN_H as
default to the mingw and mingw64 targets), and the patch for
apps/s_client.c (for some
On Mon, Jun 30, 2014 at 5:14 PM, dcrue...@qualitesys.com wrote:
Hello
openssl-SNAP-20140630
make ko
in apps/speed.c:318:4
warning: format '%d' expects argument of type 'init', but
argument 3 has type 'DWORD' : BIO_printf(bio_err, unable do
CreateThread (%d),ret);
On 1 July 2014 10:50, Ben Laurie b...@links.org wrote:
On 1 July 2014 06:52, Zoltan Arpadffy z...@polarhome.com wrote:
Hi,
I see that Rich is doing a fantastic job by cleaning up the backlog...
I absolutely agree that very old releases cannot be supported, but what
about the platforms?
I
Hi,
With the second criteria Vendor Support,
M$ will dictate easily the openssl roadmap (?!?!?),
and, indirectly,
will force any openssl win-XX users to migrate to their last wonderful
products.
Clearly, above common sense, Vendor support is not a proper criteria
to offer something like
On 30/06/2014 10:23 PM, Salz, Rich wrote:
Feel free to re-open :)
--
Principal Security Engineer
Akamai Technologies, Cambridge, MA
IM: rs...@jabber.me; Twitter: RichSalz
-Original Message-
From: owner-openssl-...@openssl.org [mailto:owner-openssl-
d...@openssl.org] On Behalf
On Tue, Jul 01, 2014 at 12:37:31PM +0100, Matt Caswell wrote:
I just started to wonder, will soon come the time when my patches
will be also refused with the unsupported platform comment?
Our soon-to-be-released roadmap has this to say on supported platform:
* Currency, i.e. a platform
On 1 July 2014 13:37, Pierre DELAAGE delaage.pie...@free.fr wrote:
Hi,
With the second criteria Vendor Support,
M$ will dictate easily the openssl roadmap (?!?!?),
and, indirectly,
will force any openssl win-XX users to migrate to their last wonderful
products.
Clearly, above common
Ok, sounds that some logical operator is missing between criteria :
I understood AND
while you suggest it is OR ELSE
Hope you are right...but not sure..
Pierre
Le 01/07/2014 15:42, Felix Laurie von Massenbach a écrit :
On 1 July 2014 13:37, Pierre DELAAGE delaage.pie...@free.fr
I thought until now, that as long there are developers who are willing to
develop for a certain platform and there is some community interest in using
that - the platform will be supported as odd might it be in the Windows and
Linux dominated World.
With the releases now in github, one
Hope you are right...but not sure..
Neither are we. That is why the current roadmap says that we're working on it.
It's important to realize that supporting a platform incurs a cost, and we need
to have some way of making the appropriate trade-offs. Clearly, we don't want
to end up where
Of course supporting a platform is incurring some costs,
...that can be shared with the community:
this is one of its purpose.
I would like to point out that for some platform, devteam could propose
a limited support/usability statement :
Typically, for WCE on which I am regularly working :
Works in current release, closing ticket.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Works in current release, closing ticket.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Works in current release, closing ticket.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Works in current release, closing ticket.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Works in current release, closing ticket.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Investigating... It seems to be an issue with the makedepend tool itself.
I hacked util/domd to show the makedepend command line, and got this
command for apps/:
makedepend -D OPENSSL_DOING_MAKEDEPEND -- -O -I.. -I../include
-DOPENSSL_NO_DEPRECATED -DOPENSSL_NO_EC_NISTP_64_GCC_128
Does the right thing on the current release.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Does the right thing on the current release, closing ticket.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Does the right thing on the current release, closing ticket.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Whoops, of course, I meant it generates the same output for dsa.o, and
only dsa.o.
Mike
On Tue, Jul 1, 2014 at 11:58 AM, Mike Bland mbl...@acm.org wrote:
Investigating... It seems to be an issue with the makedepend tool itself.
I hacked util/domd to show the makedepend command line, and got
Cannot reproduce the problem, closing the ticket.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Unsupported feature, reading both key and passphrase on a single stream (stdin)
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Very old release, unsupported platform, can't reproduce the issue, closing the
ticket.
__
OpenSSL Project http://www.openssl.org
Development Mailing List
Question asked and apparently answered; closing the ticket.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Ah! Sorry for the spam, but I think I got it. According to the
makedepend man page:
http://www.x.org/archive/current/doc/man/man1/makedepend.1.xhtml
Makedepend makes assumptions about the #includes for files appearing
later on the command line:
But when the program parses file2.c and discovers
I can confirm that CVE-2014-0198 is fixed in OpenSSL-1.0.1h.
Setting this ticket to resolved.
Matt
__
OpenSSL Project http://www.openssl.org
Development Mailing List
On 1 July 2014 17:21, Mike Bland mbl...@acm.org wrote:
Ah! Sorry for the spam, but I think I got it. According to the
makedepend man page:
http://www.x.org/archive/current/doc/man/man1/makedepend.1.xhtml
Makedepend makes assumptions about the #includes for files appearing
later on the
; git push
Counting objects: 9, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 426 bytes, done.
Total 5 (delta 4), reused 0 (delta 0)
To openssl-...@git.openssl.org:openssl.git
29be3f6..d7003c4 master - master
; git push
Counting objects: 9, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 463 bytes, done.
Total 5 (delta 4), reused 0 (delta 0)
To openssl-...@git.openssl.org:openssl.git
d7003c4..42b91f2 master - master
I am 100% in support of that notion. That'd make my Makefile
restructuring experiment much more streamlined. That, and requiring
GNU make instead of supporting both GNU make and bsdmake syntax, from
the point of view of using included sub-Makefiles. (Says me talking
the FreeBSD 9.1 user. ;-)
Mike
fixed, thanks!
; git push
Counting objects: 9, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 437 bytes, done.
Total 5 (delta 4), reused 0 (delta 0)
To openssl-...@git.openssl.org:openssl.git
42b91f2..7b1d946 master - master
;
Somebody already fixed this. Who was that handsome stranger?
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
fixed; 7b1d946..854dfcd master - master
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
This is the copyright text we got and we can't change it.
Try to imagine rouines as a small fish, swimming around in a peaceful pond.
:)
__
OpenSSL Project http://www.openssl.org
Development
glad someone reads the comments. fixed, thanks.
762a44d..df8ef5f master - master
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Fixed, thanks!
854dfcd..762a44d master - master
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Somebody fixed it awhile ago. We can't change the copyright text, tho.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated
Thanks, fixed (finally)
df8ef5f..04f545a
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
This was a bug and someone fixed it some time ago. Thanks!
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
On 06/30/2014 05:14 PM, Rich Salz via RT wrote:
It's not immediately obvious, but enforcement of the keyUsage and other
attributes is something the relying party has to do. Anything else means just
trusting the signer, and that is not secure; how do you konw the signer is not
cheating?
I
Thanks foe the info,
It was trivial issue and good to know if it has been resolved.
Have no more concern
On Tue, Jul 1, 2014 at 10:31 PM, Rich Salz via RT r...@openssl.org wrote:
According to our records, your request has been resolved. If you have any
further questions or concerns, please
changed pre-master to master key thanks: c7ada16..e67ddd1
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
djgpp is no longer a supported toolchain; mingw, windows devstudio and (i
guess) cygwin
__
OpenSSL Project http://www.openssl.org
Development Mailing List
The OpenSSL FAQ says that with a -DPURIFY build no messages about
uninitialized data should appear:
https://www.openssl.org/support/faq.html#PROG14
14. Why does Valgrind complain about the use of uninitialized data?
When OpenSSL's PRNG routines are called to generate random numbers the
Cannot reproduce with current sources. If this is still a problem please open a
new ticket.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
On Tue, 1 Jul 2014, Ben Laurie wrote:
Aha! Well done.
I suspect there's not really any reason to support makedepend anymore
- should perhaps just switch to always using gcc/clang for
dependencies?
So now gcc/clang is required to build OpenSSL?
--
Tim Rice
So now gcc/clang is required to build OpenSSL?
No, nobody's said that. The phrase was perhaps And if openssl ships with a
default set of dependencies, which it does, there's no issue about which
compiler you use at all. Once we fix the make depend requirement.
--
Principal Security
I was wondering why 'make depend' output was saved in the Makefiles.
So I guess adding the .d files to the repository and using include
statements in the Makefiles is a reasonable possibility? (That's the
angle I'm taking with my experiment, though I hadn't thought to add
the .d's to the repo.)
I was wondering why 'make depend' output was saved in the Makefiles.
Because way back when (think like early X and xmkmf) that's the way things were
done.
So I guess adding the .d files to the repository and using include statements
in the Makefiles is a reasonable possibility? (That's the
On Jul 1 19:31, Rich Salz via RT wrote:
djgpp is no longer a supported toolchain; mingw, windows devstudio and (i
guess) cygwin
As for Cygwin, I really hope so. We're actively using OpenSSL in the
Cygwin distro and typically update to the latest OpenSSL release within
just a few days.
makedepend has been broken for a while now fully support getting rid of
it entirely!
On Tue, Jul 1, 2014 at 1:15 PM, Salz, Rich rs...@akamai.com wrote:
I was wondering why 'make depend' output was saved in the Makefiles.
Because way back when (think like early X and xmkmf) that's the
if you go to About, then to Contacts, Credits or Roadmap, there
is no General link only Gerneral text
Jan
__
OpenSSL Project http://www.openssl.org
Development Mailing List
Hi,
The recently released preview of MSVC14 has changed the ABI for the C
Runtime library. The intent is to avoid having to change it again in
the future, so that DLLs linked against the current version will be
able to safely use later versions.
In e_os.h there is the following code which
On 1 July 2014 18:34, Tim Rice t...@multitalents.net wrote:
On Tue, 1 Jul 2014, Ben Laurie wrote:
Aha! Well done.
I suspect there's not really any reason to support makedepend anymore
- should perhaps just switch to always using gcc/clang for
dependencies?
So now gcc/clang is required to
Andy Polyakov wrote:
Hi,
The recently released preview of MSVC14 has changed the ABI for the C
Runtime library. The intent is to avoid having to change it again in
the future, so that DLLs linked against the current version will be
able to safely use later versions.
In e_os.h there is
On 1 July 2014 19:15, Salz, Rich rs...@akamai.com wrote:
I was wondering why 'make depend' output was saved in the Makefiles.
Because way back when (think like early X and xmkmf) that's the way things
were done.
So I guess adding the .d files to the repository and using include statements
Andy Polyakov wrote:
Hi,
The recently released preview of MSVC14 has changed the ABI for the C
Runtime library. The intent is to avoid having to change it again in
the future, so that DLLs linked against the current version will be
able to safely use later versions.
In e_os.h there is
On Tue, Jul 01, 2014 at 02:10:31PM -0400, Mike Bland wrote:
I was wondering why 'make depend' output was saved in the Makefiles.
So I guess adding the .d files to the repository and using include
statements in the Makefiles is a reasonable possibility? (That's the
angle I'm taking with my
On 1 July 2014 04:24, Salz, Rich rs...@akamai.com wrote:
There are several tickets about mingw and djgpp builds breaking, or
building software that crashes, and so on.
If you can help me understand the current state of things with those
toolchains, please drop me a line.
DJGPP was a
Yeah, the portability angle is why I'm trying to move forward
carefully. That said, isn't GNU Make everywhere these days? Couldn't
we eliminate a lot of complexity by relying on its include syntax (and
other treats)? I'm still a n00b on this scene, so I don't aim to
offend anyone, but it's an
On 1 July 2014 22:09, Mike Bland mbl...@acm.org wrote:
Yeah, the portability angle is why I'm trying to move forward
carefully. That said, isn't GNU Make everywhere these days? Couldn't
we eliminate a lot of complexity by relying on its include syntax (and
other treats)? I'm still a n00b on
Really? Its much more efficient to update the .d files when you compile the
(changed) source - which more-or-less implies one per source file.
Not necessarily. One process scanning all the sources, and one file open/parse
in make is often more efficient.
I read this on the internet
ASN.1 sanity check added. All cases now resolved.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project
Fixed in current branched. Ticket resolved.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project
Fixed now (PR#3409 duplicates this report).
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project
Fixed now in all branches. Thanks for the report.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project
Applied now, thanks for the report.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project
Fixed now, duplicate of PR#3134
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project
Fixed now, thanks for the report.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project
Fixed (duplicate of PR#3161).
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project
So one possibility is Pod::DocBook. Do you have a feel for how good it is?
Right now, OpenSSL only depends on Perl. It would probably be a real problem
for us if we required an XML suite.
__
OpenSSL Project
Someone removed the patent link a long time ago.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Can't fix or change the copyright terms.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Questions on AES-NI and how to enable them have come up twice recently
on the stack exchanges (like stack overflow).
This patch documents use of the AES-NI instruction by way of the EVP_*
interface.
diff --git a/doc/crypto/EVP_EncryptInit.pod b/doc/crypto/EVP_EncryptInit.pod
index
88 matches
Mail list logo
