I'm working on my POP3 and SMTP client for gmail, well really as an feature for my Messenger, but the gmail servers needs SSL connections, and I've been trying to implement it in assembler unsuccesfully. Does anyone has an example of how to use it?, thanks in advance.

yes

• Install this package: http://www.slproweb.com/products/Win32OpenSSL.html
  
• Port the code from MASM to FASM.
  
• Compile to FASM as a MS COFF object
  
• Use MS link.exe or POlink.exe or whatever other shit is able to link MS COFF .obj into .exe
  
• Test with stunnel.exe or similar tool. You can use Link-Net IRC servers to test SSL
  

Alternatively,

• Use dll2inc.exe from my website (check the footer of this message) to make include files for DLLs ssleay32.dll libeay32.dll
  
• Port the code from MASM to FASM.
  
• Compile to FASM as a PE 4.0 file
  
• Test with stunnel.exe or similar tool. You can use Link-Net IRC servers to test SSL
  

Instead of my dll2inc, you can use 2397197 other DLL2INC implementations on this message board (by Vortex, Revenant, etc)

Have fun, amigo!

Thanx comrade, i will use it, i think implementing my own SSL library will be a large project, and will need a lot of time. Thanx. One thing, Shakira isn't from Peru , she is from Colombia, but no problem, I agree Viva Peru!!!. I've add you some time ago to my messenger, but now you don't appear online, well if you want add me

In fact it's Reverend

yes, i know you are Reverend

but i am quite sure there is another dll2inc implementation by Revenant

kidscracker, you can also check source code of "ftpbnc" program here:

http://comrade.ownz.com/sources/ftpbnc/ftpbnc-0.4.zip

Your main concern is to sort through the OpenSSL API, and their manual on openssl.org is not very straightforward (it is just scattered manpages). Basically, you establish a normal socket connection using winsock, and then "layer" SSL on top of it using SSL_connect(socket, ...). Then, once SSL_connect does its handshaking, you will use SSL_send and SSL_recv, as opposed to send/recv. They act just the same, except SSL_send and SSL_recv will handle the encryption for you.

ftpbnc contains code to handle both types of connection (non-SSL and SSL), so you can clearly see the difference in programming both types of connections.

Linking openssl libraries (libeay32 and ssleay32) should be the least of your worries.

well after some years (7 to be exact) i come back a search for something i searched in the past. Thanks comrade, now i think i'll use for new projects

BTW no more student, now an enginner! =D