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
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
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
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
__
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
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.
--
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
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
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
+1 for keeping the features (I use AmiSSL ;) )
alan
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
+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
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
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
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
14 matches
Mail list logo
