Re: ssl breaks roundcube ?

2014-08-22 Thread ml
Hi sorry nevermind, fixed. It was a lighttpd setting. Thanks and have a nice week-end, RuggedInbox team On 2014-08-23 00:32, m...@ruggedinbox.com wrote: Hi sorry for cross sending, we already sent this email to roundcube's mailing list but got no answer. We recently improved our https configu

ssl breaks roundcube ?

2014-08-22 Thread ml
Hi sorry for cross sending, we already sent this email to roundcube's mailing list but got no answer. We recently improved our https configuration on lighttpd: https://www.ssllabs.com/ssltest/analyze.html?d=ruggedinbox.com but something seems to have broken roundcube .. can't properly attach f

Re: Best way to append to trusted CA bundle (RHEL)

2013-01-02 Thread ml
this issue and tango fix it are welcome please provide is issue Le 2013-01-01 16:32, Ray Van Dolson a écrit : I'm trying to extend the list of certifictaes (the default CA bundle) OpenSSL and OpenSSL-aware apps trust to include out Enterprise root cert. This is on a RHEL 5.x machine (0.9.8e p

Re: how

2012-10-28 Thread ml
I propose an idea: create a set of trojan that communicates via a given protocol and you get human brains linked by invisible son who are thought Le 2012-10-28 16:27, 詹晨辉 a écrit : how to stop? 发自 Windows 邮件 -- gpg --keyserver pgp.mit.edu --recv-key C2626742 http://about.me/fakessh ___

RE: win32 exe linked with -lssl -lcrypt

2012-10-14 Thread ml
Le dimanche 14 octobre 2012 à 18:10 -0400, Dave Thompson a écrit : > > From: owner-openssl-us...@openssl.org On Behalf Of ml > > Sent: Sunday, 14 October, 2012 17:54 > > > i am a little question concerning the presence of libssl.dll > > libcrypt.dll into the

win32 exe linked with -lssl -lcrypt

2012-10-14 Thread ml
hello sir and doctor i am a little question concerning the presence of libssl.dll libcrypt.dll into the win32 standard system or OS into linux this lib are very standard its the same when are the poor win32 OS is ready -- gpg --keyserver pgp.mit.edu --recv-key C2626742 http://about.me/fake

Re: Creating a SSH Key pair - public and private for my Windows 2008 server app so it can communicate with a partner sftp site

2012-09-02 Thread ML Harmon
he traditional > and/or RFC format, which could be created with about a page > of C or somewhat less perl; I recall someone posted code for > that in the list a few years ago, if you want to search for it. > > > Charles > > From: owner-openssl-us...@openssl.org > > [mailto:

Re: Creating a SSH Key pair - public and private for my Windows 2008 server app so it can communicate with a partner sftp site

2012-08-31 Thread ML Harmon
Charles Mills wrote: > You can do this with the openssl.exe utility. > > I am less than an expert but the doc is here: > http://www.openssl.org/docs/apps/openssl.html > > Take a look at openssl.exe req -newkey > > Charles > From: owner-openssl-us...@openssl.org > [mailt

Creating a SSH Key pair - public and private for my Windows 2008 server app so it can communicate with a partner sftp site

2012-08-31 Thread ML Harmon
I have a Windows 2008 server that runs an application I use to transfer files to my business partner's site via sftp. I need to generate a SSH key pair with openssl and then send my partner the public key while I keep the private key. I don't know how to do this with openssl, can someone help me?

simply connection sslv2 to v3 in c

2012-06-20 Thread ml
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 dear honorable doctor member and all Fu C when using ssl V2 it is possible to run code in a few lines I quote #define CHK_NULL(x) do { if ((x)==NULL) exit (1); } while(0) #define CHK_ERR(err,s) if ((err)==-1) { perror(s); exit(

crash on centos 5

2012-06-05 Thread ml
hello doctor hello honorable I work on a small project in c. this my code https://github.com/fakessh/openprojectssl/blob/master/smtp_openssl.c I am confronted with problems of execution on different machines on centos 6 no problem on centos 5 crash Here the trace *** glibc detected *** ./smtp_

RE: simply openssl encode c function

2012-05-29 Thread ml
Le lundi 28 mai 2012 à 17:25 -0400, Dave Thompson a écrit : > > From: owner-openssl-us...@openssl.org On Behalf Of ml > > Sent: Saturday, 26 May, 2012 16:18 > > > I try to realize as base64 encoding > > char *base64(char *input, int length) > > { > >

simply openssl encode c function

2012-05-26 Thread ml
hello honorable doctor all members ".." C Fu geeks and lady I try to use the functions correctly made ​​in native base64 openssl i managed a simple client mail with openssl base64 encoding I use the test client https://github.com/fakessh/openprojectssl/blob/master/smtp_openssl.c I try to realiz

encode base 64 in simply smtp client

2012-05-01 Thread ml
hello hello honorable Member Doctor i work on small projet https://github.com/fakessh/openprojectssl/blob/master/smtp.c https://github.com/fakessh/openprojectssl/blob/master/smtp.h i realise encode base 64 like that //realizing base64 void base64(char *dbuf, char *buf128, int len) { str

SSL cert chain validation & timestamp issues

2010-12-20 Thread travis+ml-openssl
So a friend ran into this lately; libnss, at least on Linux, checks that the signing cert (chain) is valid at the time of signature - as opposed to present time. (It may check present time as well - not sure on that) This makes for problems if you renew the cert, since the new cert will have a c

Re: Wider fallout from Debian issue?

2008-05-30 Thread travis+ml-openssl
On Wed, May 28, 2008 at 10:55:18PM -0700, David Schwartz wrote: > Okay, I guess I give up. I now realize that I had no idea what > you meant in your past few comments. What relevance do you think > this notion of weak keys has to do with this issue, since you > were the one who brought it up? > >

Re: Wider fallout from Debian issue?

2008-05-30 Thread travis+ml-openssl
On Thu, May 29, 2008 at 10:14:12AM -0400, Victor Duchovni wrote: > And then knowing that attackers never choose these keys, users start > using these keys because attakers avoid them, and then attackers start > checking these first again, ... This way lies madness. Fix your premise > and don't chan

Re: Wider fallout from Debian issue?

2008-05-30 Thread travis+ml-openssl
On Wed, May 28, 2008 at 08:01:11PM +0200, Ger Hobbelt wrote: > Anything (such as passwords) which has been used on an *actual* > 'compromized box' (be it one of 'those Debian' releases or otherwise) > to _generate_ keys plus any keys _produced_ on such a compromised box > must be eradicated and are

No NID for SHA2 (was Re: unable to verify PKCS#7 objects signed with BC(CMS))

2008-05-29 Thread travis+ml-users
On Tue, May 27, 2008 at 03:23:27PM -0500, [EMAIL PROTECTED] wrote: > So a developer at my company is having a problem. > > When our business partner signs a data object using Bouncy Castle > (PKCS#7 CMS), outputs PEM, and we use OpenSSL and read it in, that > works fine, but when we try to get the

unable to verify PKCS#7 objects signed with BC(CMS)

2008-05-27 Thread travis+ml-users
So a developer at my company is having a problem. When our business partner signs a data object using Bouncy Castle (PKCS#7 CMS), outputs PEM, and we use OpenSSL and read it in, that works fine, but when we try to get the data out of it, we're getting a null string. My hunch is that PKCS7_dataDec

testing upgrade from 0.9.7e to 0.9.8g

2008-03-06 Thread travis+ml-openssl
So we're testing out an upgrade from OpenSSL 0.9.7e to 0.9.8g, and we're mostly using the SSL network connection functionality, not the crypto lib. I am supposed to help with a test plan to make sure our stuff works properly, but I'm not sure what to test. I imagine that it has to be backward com

interop between OpenSSL PKCS#7 (v1.5) and BC (CMS)

2008-03-06 Thread travis+ml-openssl
So I've got to interchange data with a Java-based environment. I believe their choice of libraries is with Bouncy Castle, which IIUC implements a newer version of PKCS#7 called CMS. We only have OpenSSL, which uses PKCS#7 v1.5.. Does anyone have experience with these kinds of situations? It has

Re: pem.h type inconsistencies in 0.9.8g

2008-01-17 Thread travis+ml-openssl
On Thu, Jan 17, 2008 at 04:05:07PM -0600, [EMAIL PROTECTED] wrote: > So I guess I'll define a similar acro in my code now, but it'd be nice > if OpenSSL fixed it in the distribution so that I didn't have to work > around it... Ended up doing this: #define READ_SSL_SESSION(fp,x,cb,u) (SSL_SESSIO

Re: pem.h type inconsistencies in 0.9.8g

2008-01-17 Thread travis+ml-openssl
On Wed, Jan 16, 2008 at 07:29:45PM -0500, Victor Duchovni wrote: > No actual problem, in ANSI C pointers can be freely converted between > (type *) and (void *) and back. I'd call it an actual problem when a compilation of my C++ code bombs out because the OpenSSL header files don't compile in my

pem.h type inconsistencies in 0.9.8g

2008-01-16 Thread travis+ml-openssl
So this is from 0.9.8g's pem.h: #define PEM_read_SSL_SESSION(fp,x,cb,u) (SSL_SESSION *)PEM_ASN1_read( \ (char *(*)())d2i_SSL_SESSION,PEM_STRING_SSL_SESSION,fp,(char **)x,cb,u) And so is this: void * PEM_ASN1_read(d2i_of_void *d2i, const char *name, FILE *fp, void **x, pem_password_cb *cb, voi

problem with PEM_read_SSL_SESSION when upgrading from 0.9.7 to 0.9.8g

2008-01-16 Thread travis+ml-openssl
Hi all! I've recently been put in charge of SSL, and I'm working my way through the O'Reilly book. However, I'm a bit stumped as to this problem. I tried to upgrade our build system to use OpenSSL 0.9.8g, and thought I succeeded. However, the code is blowing up. The code is for caching sessi