openssl porting to rx111 to access twitter
Hello i am using rx111 platform to port openssl library. This is to develop an application to access the twitter for posting tweets. Since memory is the constraint i need demo code with bare minimum APIs and source code and header files for porting. Can somebody help me how to go about it? Also how to go about testing this application? Chowdary __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
RE: openssl porting to rx111 to access twitter
I suspect that you're going to have difficulty implementing TLS on a SoC with only 16K RAM, since TLS specifies a max message size of 16K. I think you've selected an underpowered SoC for the application. -Original Message- From: owner-openssl-...@openssl.org [mailto:owner-openssl-...@openssl.org] On Behalf Of Chowdary Sent: Monday, June 23, 2014 11:04 PM To: openssl-dev@openssl.org Cc: Chowdary Ch Subject: openssl porting to rx111 to access twitter Hello i am using rx111 platform to port openssl library. This is to develop an application to access the twitter for posting tweets. Since memory is the constraint i need demo code with bare minimum APIs and source code and header files for porting. Can somebody help me how to go about it? Also how to go about testing this application? Chowdary __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #3411] Fixed possible null pointers if malloc fails
On Tue, Jun 24, 2014 at 01:05:36PM +0200, Kurt Cancemi via RT wrote: Hello, The attached patch fixes possible null pointers if malloc fails. This was reported by qualitesys (http://marc.info/?l=openssl-devm=140243635405343), and I created the fix (no repeat of what happened last time). I think that #3198 fixes all those issues as well, and a whole bunch others. Kurt __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: OpenSSL-1.0.0m on Fedora Core 16
In my experience, the best way to build your own rpm is to install the old version's src rpm from your Linux distribution, copy the new source tar file into the rpmbuild SOURCES directory and edit the spec file to use it. Also change the package version numbers in the spec file and review any patches. __Martin On Mon, 23 Jun 2014 17:24:47 +, Bernal, Daniel L said: No. What I am saying is that once I created an RPM from the 1.0.0j source package from openssl.org (which includes a .spec file) it doesn't match the list of files that are currently installed on the FC16 system. My concern here is that the list of files is different and installed in different places. This may be something special/peculiar that someone did on FC16. My ultimate goal is to update the currently installed openssl (1.0.0j) on FC16 to 1.0.0m without breaking anything that depends on it. I will try simply removing openssl-1.0.0j-1.i686.rpm that is installed and install the openssl-1.0.0m-1.i686.rpm package version. Following is a detail of the differences that I am describing: Currently installed file list from FC16 openssl-1.0.0j-1.i686.rpm is the following: /etc/pki/CA /etc/pki/CA/certs /etc/pki/CA/crl /etc/pki/CA/newcerts /etc/pki/CA/private /etc/pki/tls /etc/pki/tls/certs /etc/pki/tls/certs/Makefile /etc/pki/tls/certs/make-dummy-cert /etc/pki/tls/misc /etc/pki/tls/misc/CA /etc/pki/tls/misc/c_hash /etc/pki/tls/misc/c_info /etc/pki/tls/misc/c_issuer /etc/pki/tls/misc/c_name /etc/pki/tls/openssl.cnf /etc/pki/tls/private /lib/.libcrypto.so.1.0.0j.hmac /lib/.libcrypto.so.10.hmac /lib/libcrypto.so.1.0.0j /lib/libcrypto.so.10 /usr/bin/openssl /usr/lib/.libssl.so.1.0.0j.hmac /usr/lib/.libssl.so.10.hmac /usr/lib/libssl.so.1.0.0j /usr/lib/libssl.so.10 /usr/lib/openssl /usr/lib/openssl/engines /usr/lib/openssl/engines/lib4758cca.so /usr/lib/openssl/engines/libaep.so /usr/lib/openssl/engines/libatalla.so /usr/lib/openssl/engines/libcapi.so /usr/lib/openssl/engines/libchil.so /usr/lib/openssl/engines/libcswift.so /usr/lib/openssl/engines/libgmp.so /usr/lib/openssl/engines/libnuron.so /usr/lib/openssl/engines/libpadlock.so /usr/lib/openssl/engines/libsureware.so /usr/lib/openssl/engines/libubsec.so /usr/share/doc/openssl-1.0.0j /usr/share/doc/openssl-1.0.0j/CHANGES /usr/share/doc/openssl-1.0.0j/FAQ /usr/share/doc/openssl-1.0.0j/INSTALL /usr/share/doc/openssl-1.0.0j/LICENSE /usr/share/doc/openssl-1.0.0j/NEWS /usr/share/doc/openssl-1.0.0j/README /usr/share/doc/openssl-1.0.0j/README.FIPS /usr/share/doc/openssl-1.0.0j/c-indentation.el /usr/share/doc/openssl-1.0.0j/openssl.txt /usr/share/doc/openssl-1.0.0j/openssl_button.gif /usr/share/doc/openssl-1.0.0j/openssl_button.html /usr/share/doc/openssl-1.0.0j/ssleay.txt /usr/share/man/man1/asn1parse.1ssl.gz . . . removed list of man pages to make list manageable for this email /usr/share/man/man7/des_modes.7ssl.gz File list in newly built openssl-1.0.0j-1.i686.rpm from source package (FC16 openssl-1.0.0j.tar.gz) off the openssl.org site. I used the openssl-1.0.0j.spec file provided in the tar file. The openssl-1.0.0m-1.i686.rpm I build has almost identical file list. /usr/bin/c_rehash /usr/bin/openssl /usr/bin/ssleay /usr/lib/libcrypto.so /usr/lib/libcrypto.so.1.0.0 /usr/lib/libssl.so /usr/lib/libssl.so.1.0.0 /usr/man/man1/CA.pl.1ssl.gz . . . removed list of man pages to make list manageable for this email /usr/man/man7/des_modes.7ssl.gz /usr/share/doc/openssl-1.0.0j /usr/share/doc/openssl-1.0.0j/CHANGES /usr/share/doc/openssl-1.0.0j/CHANGES.SSLeay /usr/share/doc/openssl-1.0.0j/LICENSE /usr/share/doc/openssl-1.0.0j/NEWS /usr/share/doc/openssl-1.0.0j/README /var/ssl/certs /var/ssl/misc /var/ssl/misc/CA.pl /var/ssl/misc/CA.sh /var/ssl/misc/c_hash /var/ssl/misc/c_info /var/ssl/misc/c_issuer /var/ssl/misc/c_name /var/ssl/misc/tsget /var/ssl/openssl.cnf /var/ssl/private __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Windows mingw status for snapshot-20140624
Hello For your info on a windows / mingw configuration openssl-1.0.1-stable-SNAP-20140624 make ok make test ok openssl-1.0.2-stable-SNAP-20140624 make ok make test ok openssl-SNAP-20140624 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); in apps/s_socket.c in function 'init_client_unix', storage size of 'them' isn't known not configured as windows it seems Didier __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
