Date: 09/07/00
- Next message: frey <email protected>: "[PHP-DEV] PHP 4.0 Bug #6614: configure does not recognize sys/socket.h"
- Previous message: lordscarlet <email protected>: "[PHP-DEV] PHP 4.0 Bug #6613: lacking description of sybase_connect (charset paramater)"
- In reply to: Wez Furlong: "RE: [PHP-DEV] Re: networking.c and fopen wrappers etc. (was RE: [ PHP-DEV] some IPv6 code added, compile problems anyone?)"
- Next in thread: Wez Furlong: "RE: [PHP-DEV] Re: networking.c and fopen wrappers etc. (was RE: [ PHP-DEV] some IPv6 code added, compile problems anyone?)"
- Reply: Wez Furlong: "RE: [PHP-DEV] Re: networking.c and fopen wrappers etc. (was RE: [ PHP-DEV] some IPv6 code added, compile problems anyone?)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Sep 07, 2000 at 09:18:24PM +0100, Wez Furlong wrote:
> It depends on how user-friendly we want to make the php interface. I have a
> feeling that we need to hook in before the actual SSL_connect call to be
> able to choose a client cert.
In PHP you could do something like this I think:
ssl_init(cert parameteres); // set client cert etc. used for all SSL
// stuff until next ssl_init call?
$fp = fopen("https://......", ...);
fpassthru($fp) // or whatever
What do you think of leaving fsockopen as is, and rather do
ssl_init(.....)
$fp = fsockopen(....)
ssl_connect($fp)
Are there situations where you might want to communicate for a while
without SSL before turning it on? If so, this would work well I think.
There are some options here, just trying to list the possibilites,
not sure what's best.
> Also, the code in the patch only works for SSL client connections, so a
> little more work is required to get things in server mode. We could
> generalize and go for the generic client/server mode I saw mentioned in the
> header files.
Yes, I'm not sure if server mode is that important, but it's good to
keep it in mind when designing the API, the most important is the API
that the PHP users see, and it can't be changed much later.
> int php_hostconnect_ssl(char * host, ushort port, int timeout, phpssl_proto
> proto, char * certfile)
Yes, something like that would be fine.
> I'm going to read up a bit more on OpenSSL, to make sure I know what I am
> talking about...
You know more than me anyway (:
It would be good if other people would comment on this as well.
Stig
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: frey <email protected>: "[PHP-DEV] PHP 4.0 Bug #6614: configure does not recognize sys/socket.h"
- Previous message: lordscarlet <email protected>: "[PHP-DEV] PHP 4.0 Bug #6613: lacking description of sybase_connect (charset paramater)"
- In reply to: Wez Furlong: "RE: [PHP-DEV] Re: networking.c and fopen wrappers etc. (was RE: [ PHP-DEV] some IPv6 code added, compile problems anyone?)"
- Next in thread: Wez Furlong: "RE: [PHP-DEV] Re: networking.c and fopen wrappers etc. (was RE: [ PHP-DEV] some IPv6 code added, compile problems anyone?)"
- Reply: Wez Furlong: "RE: [PHP-DEV] Re: networking.c and fopen wrappers etc. (was RE: [ PHP-DEV] some IPv6 code added, compile problems anyone?)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

