works fine for HTC WM6 smartphones, and should work for WM5
phones.
Thank you very much for your work.
Yours sincerely,
Pierre Delaage
diff -ur orig/apps/apps.c patched/apps/apps.c
--- orig/apps/apps.c2010-09-25 16:45:29.563877500 +0200
+++ patched/apps/apps.c 2010-09-26 07:12:44.368479500
for HTC WM6 smartphones, and should work for WM5
phones.
Thank you very much for your work.
Yours sincerely,
Pierre Delaage
diff -ur orig/apps/apps.c patched/apps/apps.c
--- orig/apps/apps.c2010-09-25 16:45:29.563877500 +0200
+++ patched/apps/apps.c 2010-09-26 07:12:44.368479500 +0200
such...it
is another question.
This is just a comment.
Pierre Delaage
Le 07/10/2010 03:05, Tristan Schmelcher a écrit :
I work on a proprietary Linux application that dynamically links to
OpenSSL for some cryptographic features (www.google.com/chat/video)
and I am considering switching to static linking
Hello,
All the answers to your questions are here :
http://delaage.pierre.free.fr/
good luck
Pierre Delaage
Le 14/07/2011 14:40, Kchitiz Saxena a écrit :
Hi
I am trying to compile openssl version 0.9.8p for Win CE 5.0 (Armv4i).
I am using Microsoft embedded VC++ 4.0 for the same. I followed
Hello,
I recommend you have a look at here, where I compiled 1.0.0a.
http://delaage.pierre.free.fr/
Best regards,
Pierre Delaage
Le 30/09/2011 15:41, Jim Row a écrit :
Has anyone gotten the 1.0.0e release to build/work on CE 5 or CE 6 (w/VS2008)?
I'm having a hard time making sense of all
(user guest password guest).
I confess that my patch still needs to be included in the openssl
mainstream because I have to adapt a few comments to strict C fashion
instead of C++ one.
I will try to do that this year...
Pierre Delaage
Le 31/10/2012 14:54, Mendonca, Joseph a écrit :
Steve,
FYI
. It will come later.
But if my patch is included in the openssl mainstream, my webpage
will be useless (and it will be good like this).
The result works fine for HTC WM6 smartphones, and should work for WM5
phones.
Thank you very much for your work.
Yours sincerely,
Pierre Delaage
p
by the mail system.
Pierre Delaage
Sujet:Re: [PATCH] for openssl v102snap20121213 for WCE 420/WM5/WM6
target platform, to fix compilation issues, resubmitted with bat scripts
De :Pierre DELAAGE delaage.pie...@free.fr
Date :17/12/2012 01:00
Pour :Andy Polyakov ap...@openssl.org
sincerely,
Pierre Delaage
Le 17/12/2012 01:08, Pierre DELAAGE a écrit :
aaargh, sorry I resent bat files instead of txt ones.
here are the promised txt files...
Resubmitted with bat scripts as txt files...
rename them as bat to use them, put them in openssl devroot dir.
following is my answer
Hi Andy,
Thank you for the comments and updates.
I will test e_capi.c this week and let you know: in fact I will try to
port the suggested modification to my patched v102 snap of 20121213.
I will also check your VC-32.pl script.
About common code : I agree with the objective, the philosophy
Bad new but for a little thing :
VC-32.pl typo at line 192 : wHecompatex must be wcecompatex...
That breaks the link stage for WCE...
Regards
Pierre
Le 18/12/2012 11:27, Andy Polyakov a écrit :
Hi,
One of the concern I am involved with is also UNICODE AND ANSI versions
of stunnel...
I
Andy,
As far as I can tell, compiling my patched version of
openssl102_snap20121213 is ok for WCE, WITH your crypto/bss_dgram.c and
your ssl.d1_lib.c,that include new ftime function.
and your VC-32.pl MODIFIED as I said about the typo on line 192.
And it is working with stunnel 500b3 for
Andy,
Hmmmyour new e_capi.c 1.39 does not compile on WCE nor any
W32...because of a typo !
line 1481 there is dwflags INSTEAD OF dwFlags (the F is uppercase in
the declared var).
fixed to dwFlags.
Well, with that fixed it compiles.
Do not know yet how to test, but I will check the
Andy,
I am reading carefully the e_capi.c code...
The piece of code Line 1119 is not clear :
len is a size in byte giving the size of the LP-T-STR name,
So, whatever is the sizeof(TCHAR), one is allowed to do : name = (TCHAR
*) malloc(len).
So it is not clear why one should use alloca when
Hi Andy
Le 19/12/2012 19:52, Andy Polyakov a écrit :
Hi,
I am reading carefully the e_capi.c code...
The piece of code Line 1119 is not clear :
len is a size in byte giving the size of the LP-T-STR name,
So, whatever is the sizeof(TCHAR), one is allowed to do : name =
(TCHAR *)
Hello Andy,
Thank you for the explanations.
Understood about alloca...as name is copied in pname later in
unicode case, it can NOT be taken on the stack with alloca.
if we were using a kind of tchar2char routine, doing malloc and memcpy
in char case, we could have simpler code...
But thanks
Dear Steve,
I was wondering whether the wiki could be fed at the beginning by all
the Documents available at http://www.openssl.org/docs/;.
Very often people are able to comment, eg, a command page with some
samples or error comments,
instead of rewriting from scratch a man page.
And this
Some broken links on online pages :
at http://www.openssl.org/related/ :
openssl / related / OpenSSL/SSLeay web page :
broken links are :
MS Dev Studio workspace for OpenSSL
http://openssl.governmentsecurity.org/
SSLeay Doc: FAQ List
http://www.psy.uq.oz.au/~ftp/Crypto/
SSLeay Doc:
its own doc space as usual, away from
the wiki.
Yours sincerely,
Pierre
Le 19/03/2013 20:15, Ben Laurie a écrit :
On 19 March 2013 18:53, Steve Marquess marqu...@opensslfoundation.com wrote:
On 03/19/2013 10:47 AM, Pierre DELAAGE wrote:
Dear Steve, I was wondering whether the wiki could be fed
.
With the wiki, I think that info will never get lost.
Yours sincerely,
Pierre
Le 19/03/2013 19:53, Steve Marquess a écrit :
On 03/19/2013 10:47 AM, Pierre DELAAGE wrote:
Dear Steve, I was wondering whether the wiki could be fed at the
beginning by all the Documents available at
http
its own doc space as usual, away from
the wiki.
Yours sincerely,
Pierre
Le 19/03/2013 20:15, Ben Laurie a écrit :
On 19 March 2013 18:53, Steve Marquess marqu...@opensslfoundation.com wrote:
On 03/19/2013 10:47 AM, Pierre DELAAGE wrote:
Dear Steve, I was wondering whether the wiki could be fed
Marquess a écrit :
On 03/19/2013 10:47 AM, Pierre DELAAGE wrote:
Dear Steve,
I was wondering whether the wiki could be fed at the beginning by all
the Documents available at http://www.openssl.org/docs/;.
Very often people are able to comment, eg, a command page with some
samples or error
:
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
Ok Ravi,
You asked me some help in private,
that I will reproduce here so that people can follow the complete thread :
Le 22/05/2014 15:39, Pierre DELAAGE a écrit :
Hello,
I am working on it myself,
and particularly for my stunnel port.
I will let you know.
In the meantime : if you have
you
Pierre
Le 23/05/2014 12:37, RaviVyas a écrit :
Hello Pierre DELAAGE,
Now i Am Following our Steps.
I Changed File makece.bat and wcedefs.bat file. also make a Chnage in Bat
File of WCEARMV4.
Title WCE ARMV4 Environment
MYBAT FILE IS:-
You are Setting Platform is
PLATFORM=STANDARDSDK
WHat
and mfc Folders Path.
ok
In NExt Include Directory Only 1 Folder is There ARMV4i
so How Can These Steps Performed.
On Fri, May 23, 2014 at 10:47 PM, Pierre DELAAGE
delaage.pie...@free.fr mailto:delaage.pie...@free.fr wrote:
Hello,
In the scripts, you only have to tweak :
1/ the CUSTOMIZE
Ok, good again
For execution time, when all is done with your app,
you do NOT need wcecompat NOR wcecompatex,
because those lib are STATIC libraries, that are now put inside your dll.
You noticed that your compilation of wcecompat DID NOT produce any dll,
just libs.
Those lib have been
, personnally, I already faced to produce many minor bug fixes
(some #include for WCE for example),
that were not included, in a reasonable time, to the main code stream.
And at a time, some time and info are lost...on any platform, not only
exotic ones...
Yours sincerely
Pierre Delaage
Le 01/06/2014
V102 for WCE to
see how things are going by myself.
Regards
Pierre
Le 02/06/2014 08:32, Ravi vyas a écrit :
Hello,
Pierre Delaage
Have you seen My Attached images .Screenshot Of Emulator.
i dont Know Which is Problem?
how casn i Solve this?Is There any problem in .LIb
Hmm...
Of course I can understand the purpose of a website modernization...
but I really think that, as for every other website,
the first question is : what is the purpose of the website..
then : what can be/should be its mission
and then : what can be / should be its content..
And thenwhen
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
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
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 wrote
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 :
definition, we use typedef instead of #define, to get stronger type
checking.
Yours sincerely,
Pierre Delaage
__
OpenSSL Project http://www.openssl.org
Development Mailing List
(and after improvment in the past
to switch to winsock2) , WCE code is just the same as win32 desktop code.
Yours sincerely
Pierre Delaage
Le 20/08/2014 18:32, stefan.n...@t-online.de a écrit :
And a question concerning a different platform. Is there any interest in
integrating
official support
...
If needed I CAN offer a WCE version.
Yours sincerely
Pierre Delaage
Le 14/09/2014 21:05, Salz, Rich a écrit :
Any input from Windows folks on the attached?
--
Principal Security Engineer, Akamai Technologies
IM: rs...@jabber.me mailto:rs...@jabber.me Twitter: RichSalz
I meant in fact that calling two times getdibits could have given the
necessary info to, then, allocate the proper buffer,
instead of using getobject.
Getdibits does not return a new pointer by itself.
Sorry for the mistake.
Le 18/09/2014 12:49, Pierre DELAAGE a écrit :
GetDibits COULD also
Hello,
I think that my patched version for WCE should work for windows phone :
https://www.mail-archive.com/openssl-dev@openssl.org/msg35958.html
reported (but with no details) to rt system here :
http://rt.openssl.org/Ticket/Display.html?id=3498
To my mind, shortly speaking : it is still easy
Dear Gilles,
I will have a look and let you know,
but my own experience, particularly with openssl, is that it is easier
to fork than to merge.
And I highly prefer to try-to-directly merge WinXX code into openssl
mainstream, by submitting patches through the dev-team mailing list or
40 matches
Mail list logo
