Re: Copy of an x509_store variable

> I want to copy an x509_store variable in another one which have the same > type (x509_store). > is there a method like (memcpy in c++) which can copy from x509_store to > x509_store? Or, how we can define the size of the struct x509_store to use > > the function memcpy(x509_stor * x, x509_store *

MOVILIZACION 17/09-15HS: ARDE LA CIUDAD contra Macri

ASOCIACIÓN DE PROFESIONALES CENTRO DE SALUD MENTAL Nº 3 'Dr. ARTURO AMEGHINO' Personería Jurídica N° de Resolución 1004 Fundada en 1983 ADHERIMOS Y CONVOCAMOS A LA MOVILIZACION ARDE LA CIUDAD CONTRA MACRI. *ARDE LA CIUDAD* · Viola la Independencia del Poder Judicial ·

Certificates and cert checking

I'm having trouble adding certificate checking to my app. I created a certificate file for the server, and have a copy of the crt file in the client, load it with SSL_CTX_load_verify_locations with a directory which returns true, but if I call SSL_CTX_set_verify with SSL_VERIFY_PEER on my context,

Building with OSSL

Also, I need to build with OpenSSL, but from source. The thing is that compiling the source throws about a bazillion "undefined reference" linking errors. The one I'm running into right now is this: /home/soundwave/projects/larvita2/trunk/fileio/openssl/ssl/ssl_algs.c:72: undefined reference to `E

My first stumbles with OpenSSL [was: SSL overhead]

All who have answered: Thanks a lot. Yes, I understood that the poll() should read to a buffer last night, in the shower. You know how that works ;). But I also understood that I had misunderstood the way the "poll" and "read" methods were being used, and "read" will be called no matter what "poll

Re: SSL overhead

does one of the flags in the BIO object say anything about the blocking nature of the BIO? For example, does SSL_connect return automatically or not depending on the BIO flags, or on the BIO_write and read return values? T -- |_|0|_| |_|_|0| |0|0|0| (\__/) (='.'=)This is Bunny. Copy and paste b

Re: SSL overhead

One more question: I'm working on an ansynchronous framework, and there's a "poll" method that gets called in each iteration. In our sockets, this method's supposed to do whatever needs doing, and return how many bytes are waiting to be read from the socket, so the return value should be the value

Re: SSL overhead

> It would seem that the socket BIO handles the socket abstraction, but > it does not handle calls to BIO_S_CONNECT. Actually, a grep for > BIO_S_CONNECT returns only bss_conn.. why is this? shouldn't sockets > have a call to connect too? sorry, I forgot that you create the BIO_socket with the

Re: SSL overhead

Stephen: > > Most of them you don't need to worry about. I'd suggest looking at the fd > > BIO > > and copy some of the functionality from that. I also need to know which of the BIO_CTRL_* params do I have to implement in my _ctrl function. Is there a reason why you said to look at the fd BIO

Re: SSL overhead

> Most of them you don't need to worry about. I'd suggest looking at the fd BIO > and copy some of the functionality from that. OK, I will. I just wondered because mem_new (the new method of BIO_s_mem) sets shutdown = 1 ; init = 1; num = -1 and rtcp does init = 1 ; num = 0 ; flags = 0 ; so I'd l

Re: SSL overhead

Is there any reference of what do the different members of the BIO objects mean? method, ptr, next_bio and prev_bio are pretty obvious, but the rest, I don't know, and I haven't been able to find any details out there.. I'll keep googling, but if anyone knows of a good detail out there, please poin

Re: SSL overhead

OK, I think I'll implement my own BIO. My C is good, although not brilliant, but I can do it. What stopped me from trying that approach in the first place was that the BIO* functions are so many and that I don't know which ones do I actually *need* to reimplement (that is, which ones is the eng

Re: SSL overhead

> general concepts. From reading examples I figure that only the > BIO_f_ssl does encryption-decryption when written into? so what should Or doing SSL_write into a SSL object with a BIO_s_mem object as the write-bio will write the encrypted data into it? T -- |_|0|_| |_|_|0| |0|0|0| (\__/) (

Re: SSL overhead

I'm getting started with ssl, and there's a lot of things I don't get about the library, small, and quite a lot of them Isn't there an IRC channel, or some kind of faster communication way than this? The documentation's poor at best, and I don't completely get the general concepts. From reading e

SSL overhead

We have our own TCP implementation, and we're thinking of using a BIO_s_mem to add an SSL layer to it. The plan is: read the socket, put the encrypted data into the ssl object's BIO, and then do a read from it. Likewise, produce the data, feed it into OpenSSL, and then take the data from the BIO an

getting started

Hi.. Kyle: thanks for your answer. I've been looking into it, and if OpenSSL works as I think it does, then it should be easy to put a BIO_s_mem between my TCP implementation's socket and OpenSSL. Now I'd just need to program USING OpenSSL... the internet's driving me crazy, there seems to be no c

porting

We have a multi-platform (Linux-Windows-Mac-PSP-Wii-NDS-PS2 as per right now) game engine, and wanted to add SSL to the networking layer. I'd like to know what do we need to do in order for OpenSSL to use our TCP implementation, or where to look for. I'm struggling through the documentation and ex