RE: argv/Argv hacks in openssl.c
From: ann-i...@hotmail.com To: openssl-dev@openssl.org Subject: RE: argv/Argv hacks in openssl.c Date: Mon, 7 Jul 2014 01:15:18 +0700 ควยไร ฮะ เหี้ย From: rs...@akamai.com To: openssl-dev@openssl.org Date: Sat, 5 Jul 2014 12:45:34 -0400 Subject: argv/Argv hacks in openssl.c There’s a bunch of hacks in apps/openssl.c to work around some old VMS releases; the coment is dated 2011-03-22.I am going to delete it.Speak up now if you can justify keeping it. -- Principal Security EngineerAkamai Technologies, Cambridge, MAIM: rs...@jabber.me; Twitter: RichSalz
RE: argv/Argv hacks in openssl.c
ควยไร ฮะ เหี้ย From: rs...@akamai.com To: openssl-dev@openssl.org Date: Sat, 5 Jul 2014 12:45:34 -0400 Subject: argv/Argv hacks in openssl.c There’s a bunch of hacks in apps/openssl.c to work around some old VMS releases; the coment is dated 2011-03-22.I am going to delete it.Speak up now if you can justify keeping it. -- Principal Security EngineerAkamai Technologies, Cambridge, MAIM: rs...@jabber.me; Twitter: RichSalz
RE: Small website bug
เหี้ยไร เนี่ย > Date: Tue, 1 Jul 2014 21:14:13 +0200 > From: janpo...@gmx.net > To: openssl-dev@openssl.org > Subject: Small website bug > > 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 openssl-dev@openssl.org > Automated List Manager majord...@openssl.org
RE: Makedepend bug?
ควยไง สัด > Date: Tue, 1 Jul 2014 16:57:59 -0400 > From: ty...@mit.edu > To: openssl-dev@openssl.org > Subject: Re: Makedepend bug? > > 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 experiment, though I hadn't thought to add > > the .d's to the repo.) > > The problem with using include statements in Makefiles is that's not > particularly portable. So what I do in e2fsprogs is to modify the > Makefile.in files directly (since I use autoconf, but NOT automake or > libtool): > > .depend: Makefile $(SRCS) $(top_srcdir)/depfix.sed $(top_srcdir)/wordwrap.pl > if test -n "$(SRCS)" ; then \ > $(CC) -M $(ALL_CFLAGS) $(DEPEND_CFLAGS) $(SRCS) | \ > $(SED) -f $(top_srcdir)/depfix.sed \ > -e 's; $(srcdir)/; $$(srcdir)/;g' \ > -e 's; $(top_srcdir)/; $$(top_srcdir)/;g' \ > -e 's; $(top_builddir)/; $$(top_builddir)/;g' \ > -e 's; \./; ;g' \ > -e '/^#/d' \ > -e '/^ *\\$$/d' | \ > $(PERL) $(top_srcdir)/wordwrap.pl > .depend; \ > else :; fi > > depend:: .depend > if test -n "$(SRCS)" ; then \ > sed -e '/^# +++ Dependency line eater +++/,$$d' \ > < $(srcdir)/Makefile.in | cat - .depend \ > > $(srcdir)/Makefile.in.new; \ > if cmp -s $(srcdir)/Makefile.in $(srcdir)/Makefile.in.new ; then \ > $(RM) $(srcdir)/Makefile.in.new ; \ > else \ > $(MV) $(srcdir)/Makefile.in $(srcdir)/Makefile.in.old; \ > $(MV) $(srcdir)/Makefile.in.new $(srcdir)/Makefile.in; \ > fi ; else :; fi > > ... and where depfix.sed is a sed script that strips out the system > header files, so that the resulting dependencies are portable across > different OS's. So this matches OpenSSL's requirements, I think. Gcc > is required to update the dependencies, but it's not required for > people who are building on systems that have old-style makes, > including ones that go as far back as Solaris 2.x, AIX, etc. (This is > a modified and updated version of something that I had originally > created for MIT Kerberos, which had a very wide portability > requirement, including creating NMAKE compatible files for a very old > version of Visual Studio, as well as makefiles that would work with > Apple's MPW. :-) > > - Ted > __ > OpenSSL Project http://www.openssl.org > Development Mailing List openssl-dev@openssl.org > Automated List Manager majord...@openssl.org
RE: please
อะไร งง? Date: Fri, 27 Jun 2014 21:59:42 -1000 Subject: please From: brudda@gmail.com To: openssl-dev@openssl.org tell me how to be done with your feed
Re: Re: sha1_block_data_order_avx() zeroes XMM11-XMM15 (non-volatile) registers
???:-D -Original Message- From: Petr Filipský Sent: 8/13/2013 1:41:50 PM To: openssl-dev@openssl.org Subject: Re: sha1_block_data_order_avx() zeroes XMM11-XMM15 (non-volatile) registers Hello Andy, thank you for the quick response, fixing the bug and even for build config advises. Keep up the great work! Kind regards, Petr
[no subject]
???:-D __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
[no subject]
-- ?? Nokia ?? __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
[no subject]
:o*@nn-idol*::D __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
[no subject]
:o*@nn-idol*::D __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
???: Re: OpenSSL Wiki (docbook and...)
:o*@nn-idol*::D -Original Message- From: Pierre DELAAGE Sent: 3/19/2013 11:49:24 PM To: openssl-dev@openssl.org Cc: Steve Marquess Subject: Re: OpenSSL Wiki (docbook and...) Hi Steve, My own experience in my company is that OpenOffice is perfectly suited for track changes in a collaborative env. Ok, allright, it cannot offer a line by line diff as in cvs systems, and return to specific version and so on, but the track changes can help. In my company, we were using latex...and track changes was in fact even more complicated with it. Not talking about "tables" and "graphics" that were painful. OpenOffice gives the advantages of various worlds : wisywyg, open format, quite robust for big doc compared to other similar products,.. xml based... Be careful before going away back to some raw xml format...even if it is better than latex. a question : Are you thinking to use "LyX" editor to produce Docbook ? Anyway I have 2 comments : 1/ fips guide seems good like it is : regularly updated and maintained. I do not think that people claimed for a wiki on that, so I think it can stay as it is. 2/ wiki was called by some of us to improve some old doc that do not seem to evolve regularly and that miss some details, explanations, samples. For the moment I would recommend that the wiki focuses on lib doc and command line doc, and not on fips guide. Well...now a question : I am not an expert with mediawiki format, but will you have also that "version control" issue with that format ? how to solve it then... or maybe it is not relevant for the wiki, but only for the fips guide... Regards, Pierre Le 20/03/2013 00:16, Steve Marquess a écrit : > On 03/19/2013 04:04 PM, Pierre DELAAGE wrote: >> hmm, Steve I highly suggest that we have a look at ...OpenOffice and its >> various export filters. >> >> for mediawiki it is there : >> http://extensions.services.openoffice.org/fr/node/738 >> >> for Docbook the filter is embedded (never tested by myself..). >> >> Does it help ? > Well, I haven't specifically tried Libreoffice filters for ODF to > markdown but the OpenSSL FIPS User Guide is currently in ODF and that's > what I'm trying to get away from. > > A major drawback of ODF is that is can't easily be version controlled in > a collaborative setting. Now that there are several people contributing > content to that document the ODF format is very limiting, hence the > ongoing attempt to convert to docbook. That has turned out to be a bit > of a challenge but I'm still hoping to pull it off. > > -Steve M. > __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
???: Re: OpenSSL Wiki (docbook and...)
:o*@nn-idol*::D -Original Message- From: Pierre DELAAGE Sent: 3/19/2013 11:49:24 PM To: openssl-dev@openssl.org Cc: Steve Marquess Subject: Re: OpenSSL Wiki (docbook and...) Hi Steve, My own experience in my company is that OpenOffice is perfectly suited for track changes in a collaborative env. Ok, allright, it cannot offer a line by line diff as in cvs systems, and return to specific version and so on, but the track changes can help. In my company, we were using latex...and track changes was in fact even more complicated with it. Not talking about "tables" and "graphics" that were painful. OpenOffice gives the advantages of various worlds : wisywyg, open format, quite robust for big doc compared to other similar products,.. xml based... Be careful before going away back to some raw xml format...even if it is better than latex. a question : Are you thinking to use "LyX" editor to produce Docbook ? Anyway I have 2 comments : 1/ fips guide seems good like it is : regularly updated and maintained. I do not think that people claimed for a wiki on that, so I think it can stay as it is. 2/ wiki was called by some of us to improve some old doc that do not seem to evolve regularly and that miss some details, explanations, samples. For the moment I would recommend that the wiki focuses on lib doc and command line doc, and not on fips guide. Well...now a question : I am not an expert with mediawiki format, but will you have also that "version control" issue with that format ? how to solve it then... or maybe it is not relevant for the wiki, but only for the fips guide... Regards, Pierre Le 20/03/2013 00:16, Steve Marquess a écrit : > On 03/19/2013 04:04 PM, Pierre DELAAGE wrote: >> hmm, Steve I highly suggest that we have a look at ...OpenOffice and its >> various export filters. >> >> for mediawiki it is there : >> http://extensions.services.openoffice.org/fr/node/738 >> >> for Docbook the filter is embedded (never tested by myself..). >> >> Does it help ? > Well, I haven't specifically tried Libreoffice filters for ODF to > markdown but the OpenSSL FIPS User Guide is currently in ODF and that's > what I'm trying to get away from. > > A major drawback of ODF is that is can't easily be version controlled in > a collaborative setting. Now that there are several people contributing > content to that document the ODF format is very limiting, hence the > ongoing attempt to convert to docbook. That has turned out to be a bit > of a challenge but I'm still hoping to pull it off. > > -Steve M. > __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
