Re: The no-stdio and NO_FP_API options
That sounds good. How do you want my changes to be submitted? Via an attached diff here or by private mail? regards, Jens -- Jens Maus, Dresden/Germany http://jens-maus.de/ (Please note a real name change effective since 5.9.2013. Previous name: Jens Langner) Am 05.09.2014 um 13:49 schrieb Salz, Rich rs...@akamai.com: Thanks. There is no big rush, knowing you're working on it, and this is for after 1.0.2. Perhaps by January/Feb? -- Principal Security Engineer Akamai Technologies, Cambridge MA IM: rs...@jabber.me Twitter: RichSalz __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org smime.p7s Description: S/MIME cryptographic signature
RE: The no-stdio and NO_FP_API options
It would be easiest if you attached them to RT 2279. If that’s a hassle, post them or email me. -- Principal Security Engineer Akamai Technologies, Cambridge MA IM: rs...@jabber.memailto:rs...@jabber.me Twitter: RichSalz
Re: The no-stdio and NO_FP_API options
Am 04.09.2014 um 17:56 schrieb Salz, Rich rs...@akamai.com: So please tell me *exactly* what you require to get the NO_FP_API support into a state that it is still acceptable for you. And please tell how and on which platform I can reproduce the problems you are seeing. Any Linux platform. ./config no-stdio -DNO_FP_API should build clean. Ok, just give me some time to examine this and to cleanup our AmiSSL SVN repository so that I can provide you more clean patches to keep these things alive. And of course its clear to me that I am the petitioner. That was clear right from the start. regards, jens -- Jens Maus, Dresden/Germany http://jens-maus.de/ (Please note a real name change effective since 5.9.2013. Former name: Jens Langner) *** Content is authentic only with digital signature *** smime.p7s Description: S/MIME cryptographic signature
RE: The no-stdio and NO_FP_API options
Thanks. There is no big rush, knowing you're working on it, and this is for after 1.0.2. Perhaps by January/Feb? -- Principal Security Engineer Akamai Technologies, Cambridge MA IM: rs...@jabber.me Twitter: RichSalz __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: The no-stdio and NO_FP_API options
Well, I would be happy to assist you in keeping NO_FP_API alive and supply you with adequate diffs and resources. However, I would first need to know what exactly is not working for you and where and on which platform exactly it breaks for you because actually it is *working* for us. Please note that the Amiga platform is substantially different to the usual Unix and Windows environments OpenSSL is build for. One important reason why we need the NO_FP_API support is, that AmigaOS comes with a variety of different c-library implementations which all have their own (thus incompatible) FP implementations. Thus, we need to have a possibility to easily compile OpenSSL without any FP depending function prototype so that our publicly released shared library can be used by applications being compile by different compilers and thus c-libraries implementation of FP. So please tell me *exactly* what you require to get the NO_FP_API support into a state that it is still acceptable for you. And please tell how and on which platform I can reproduce the problems you are seeing. best regards, jens Am 04.09.2014 um 03:02 schrieb Salz, Rich rs...@akamai.com: I am sorry that I was not clear. I am saying that if there are people who depend and want no-stdio and NO_FP_API to be kept in the OpenSSL source, then they need to feed their patches, just to make those things work, back to OpenSSL. My mind is not made up. I am asking for people who want us to keep this, to contribute code and effort so that we can do so. Right now it's a broken build that nobody else can use. Does that make more sense? -- Jens Maus, Dresden/Germany http://jens-maus.de/ (Please note a real name change effective since 5.9.2013. Former name: Jens Langner) *** Content is authentic only with digital signature *** smime.p7s Description: S/MIME cryptographic signature
RE: The no-stdio and NO_FP_API options
So please tell me *exactly* what you require to get the NO_FP_API support into a state that it is still acceptable for you. And please tell how and on which platform I can reproduce the problems you are seeing. Any Linux platform. ./config no-stdio -DNO_FP_API should build clean. -- Principal Security Engineer Akamai Technologies, Cambridge MA IM: rs...@jabber.me Twitter: RichSalz __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: The no-stdio and NO_FP_API options
We are using these options for an AmigaOS-based port of OpenSSL (which we call AmiSSL) which can be found here: http://sourceforge.net/projects/amissl/ In fact, we use these two options because file pointers are substantially handled differently on AmigaOS and we use no-stdio because we build AmiSSL as an Amiga shared library which doesn’t support stdio output. So please don’t remove these options but keep them. regards, jens Am 03.09.2014 um 18:10 schrieb Salz, Rich rs...@akamai.com: These configuration options do not build. I started to try and fix them, but after fixing the first few problems, things got really sticky. We hear that OpenSSL on embedded devices is important. Is anyone using this, willing to share their fixes, and help maintain it? If not, it will be removed post-1.0.2 Thanks. -- Principal Security Engineer Akamai Technologies, Cambridge MA IM: rs...@jabber.me Twitter: RichSalz -- Jens Maus, Dresden/Germany http://jens-maus.de/ (Please note a real name change effective since 5.9.2013. Former name: Jens Langner) *** Content is authentic only with digital signature *** smime.p7s Description: S/MIME cryptographic signature
RE: The no-stdio and NO_FP_API options
What config flags to you use? What changes have you made? It doesn't build for me. -- Principal Security Engineer Akamai Technologies, Cambridge MA IM: rs...@jabber.me Twitter: RichSalz __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: The no-stdio and NO_FP_API options
+1 for keeping the features (I use AmiSSL ;) ) alan -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
RE: The no-stdio and NO_FP_API options
+1 for keeping the features (I use AmiSSL ;) ) It doesn’t build. Unless that is addressed, it is highly likely that I will remove it from the tree after 1.0.2 -- Principal Security Engineer Akamai Technologies, Cambridge MA IM: rs...@jabber.me Twitter: RichSalz
Re: The no-stdio and NO_FP_API options
Am 03.09.2014 um 21:33 schrieb Salz, Rich rs...@akamai.com: +1 for keeping the features (I use AmiSSL ;) ) It doesn’t build. Unless that is addressed, it is highly likely that I will remove it from the tree after 1.0.2 Well, then why are you asking for opinions in first place if your decision is already made. All I can say is that AmiSSL perfectly builds without an file pointer based functions and without stdio. I can of course prepare a diff for you but this diff will then include other amiga related modifications as well. regards, jens -- Jens Maus, Dresden/Germany http://jens-maus.de/ (Please note a real name change effective since 5.9.2013. Former name: Jens Langner) *** Content is authentic only with digital signature *** smime.p7s Description: S/MIME cryptographic signature
Re: The no-stdio and NO_FP_API options
On Wed, Sep 3, 2014 at 4:21 PM, Jens Maus m...@jens-maus.de wrote: Am 03.09.2014 um 21:33 schrieb Salz, Rich rs...@akamai.com: +1 for keeping the features (I use AmiSSL ;) ) It doesn’t build. Unless that is addressed, it is highly likely that I will remove it from the tree after 1.0.2 Well, then why are you asking for opinions in first place if your decision is already made. All I can say is that AmiSSL perfectly builds without an file pointer based functions and without stdio. I can of course prepare a diff for you but this diff will then include other amiga related modifications as well. Please - show, don't tell. Diffs and some details of the build environment would be helpful. - M
RE: The no-stdio and NO_FP_API options
I am sorry that I was not clear. I am saying that if there are people who depend and want no-stdio and NO_FP_API to be kept in the OpenSSL source, then they need to feed their patches, just to make those things work, back to OpenSSL. My mind is not made up. I am asking for people who want us to keep this, to contribute code and effort so that we can do so. Right now it's a broken build that nobody else can use. Does that make more sense? -- Principal Security Engineer Akamai Technologies, Cambridge MA IM: rs...@jabber.me Twitter: RichSalz __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
