php - Encrypted and signed MIME messages using RFC 1847 -

I need a client-server encryption solution for Web Transfer (i.e. signed and encrypted client-side, and verified and decrypted server)

I am using HTTP, but SSL is not available due to shared hosting restrictions (my server is a shared host environment). Given the alternate solutions, I have decided to use OpenGGP. One of the reasons is that it is supported in PHP through various peers and PECL modules (PHP is the language I use for both my client script and my server script, though Pearl is also available as a last resort).

Now I am trying to determine the best way to transmit data. I have come completely, which signals encrypted and multipart MIME messages. This protocol has been specially enhanced in PGP. (I think these protocols are related to S / MIME encrypted email protocols).

My question is this: is there any reason to follow these standards? As far as the protocol goes, they look like a smart solution, but is there a customer who actually uses this protocol? For example, if I have made a multipart / encrypted request for Apache web server, would there be an easy way to retrieve data? Using my php script, my test had thought that PHP is trying to understand them ($ _POST data seems to be 'multipart / form-data' from MIME-type data).

As my host will open chairs me, I would be to use the PHP socket programming API 'Multipart / Encrypted' and 'Multipart / Signed' HTTP requests for writing PHP scripts to work in form, but it looks like overkill.

Any suggestions?

For more information about my problem, please see.

You are right - these protocols are related to encrypted mail protocols, which are slightly in your case The bit over is over and you have to use the Wolud OpenSSL php extension. Go with OpenPGP

Since your customer will be written in PHP - Consider the following scenarios:

Scenario 1: Create simple SOAP webservice

Server and client methods

- (my public Key is xxxx) -

• Customer -> HTTP receive (send me your public key) -> server
• server
• The client -> HTTP POST (sends the encrypted message) -> the server
• the server
• the client & lt; - Encoded answer for client & lt; - Server