Hi Blake,
I've only just found some time to skim php-dev, so sorry for the late
reply...
4.2 (or 4.3 if I run out of time) will have SSL sockets, for SSL clients
only, perhaps servers (I will need someone to test this aspect, as I won't
have the time for a while).
--Wez.
On 29/11/01, Blake
Thanks,
For now, I think I'll just go with an SSH tunnel.
On Tue, 2001-12-04 at 13:03, Wez Furlong wrote:
Hi Blake,
I've only just found some time to skim php-dev, so sorry for the late
reply...
4.2 (or 4.3 if I run out of time) will have SSL sockets, for SSL clients
only, perhaps
We are developing an application which needs to communicate via SSL
sockets. I can't find any documentation, examples, or functions that
look like they support this. Is there any support for it? Is SSH or
stunnel/sslwrap my best option?
--
Blake Barnett (bdb) [EMAIL PROTECTED]
Sr. Unix
it..
Thanks
Ben
- Original Message -
From: Blake Barnett [EMAIL PROTECTED]
To: Benjamin Barringer [EMAIL PROTECTED]
Sent: Thursday, November 29, 2001 2:27 PM
Subject: Re: [PHP-DEV] SSL Sockets in 4.1.0?
How does this relate to sockets? Am I missing something?
On Thu, 2001-11-29
On 2001-03-01 05:14:18, Andi Gutmans [EMAIL PROTECTED] wrote:
This sounds pretty good. I'll try and look at the code this weekend. Some
of the code is really ugly especially the legacy code.
When you say there are places which need a FILE * do you mean they just
need to check the id and
Sorry - I've been having problems with my mail client;
I have resent the message with sensible line breaks.
On 2001-02-27 06:53:05, Stig Venaas wrote:
But with for instance IPv6, you won't know what socket you need until
you're done with the resolving. That's why hostconnect() is like it
is.
On Wed, Feb 28, 2001 at 05:12:55PM +, Wez Furlong wrote:
I think what we need depends on how far we are willing to go to make
the codebase nicer. Andi Gutmans suggested that it would be nice
to nuke all the checks for sockets in the code; depending on how far
we go towards that ideal, we
This sounds pretty good. I'll try and look at the code this weekend. Some
of the code is really ugly especially the legacy code.
When you say there are places which need a FILE * do you mean they just
need to check the id and check that it's a FILE * or do they convert
descriptors to FILE *
Too early in the morning. I just remembered fdopen() :)
Andi
At 07:14 AM 3/1/2001 +0200, Andi Gutmans wrote:
This sounds pretty good. I'll try and look at the code this weekend. Some
of the code is really ugly especially the legacy code.
When you say there are places which need a FILE * do you
On Thu, Mar 01, 2001 at 07:14:18AM +0200, Andi Gutmans wrote:
This sounds pretty good. I'll try and look at the code this weekend. Some
of the code is really ugly especially the legacy code.
Yes, I like it too, and it is something I've been halfway thinking of
myself because of IPv6. Some of
Do you have time to map where in PHP we are currently using socket code?
I think according to how many places and how we are using it, it'll help us
decide how much redesigning we can do. Also keep Win32 in mind while
thinking of this.
I didn't have much time but I did read through your RFC
On 2001-02-27 06:53:05, Stig Venaas wrote:
But with for instance IPv6, you won't know what socket you need until
you're done with the resolving. That's why hostconnect() is like it
is. It even needs to connect before it knows what socket to use. That
I must have missed hostconnect(). I
On 2001-02-27 20:07:09, Andi Gutmans wrote:
Do you have time to map where in PHP we are currently using socket code?
I think according to how many places and how we are using it, it'll help us
decide how much redesigning we can do. Also keep Win32 in mind while
thinking of this.
As is the
On Mon, Feb 26, 2001 at 01:31:05AM -, Wez Furlong wrote:
I've been reviewing my relatively crude patch from September last year that
provided transparent SSL socket access to PHP via the php functions
fsockopen, fread etc. etc.
Great, I was wondering what happened, was considering doing
On 2001-02-26 08:21:23, Stig Venaas [EMAIL PROTECTED] wrote:
Sounds good to me. It's also impossible in a portable way to know if a
socket is AF_INET, AF_INET6 or AF_LOCAL, so for socket() function etc.
I've been thinking of doing something like this to store what domain
a socket is in
On Mon, Feb 26, 2001 at 11:39:51PM +, Wez Furlong wrote:
When opening a socket there are 3 stages (and thus operations on the socket):
1. Create a socketd of appropriate domain/type/family (socket(2))
2. resolve the address to connect to (domain specific)
3. make the connection
I've been reviewing my relatively crude patch from September last year that
provided transparent SSL socket access to PHP via the php functions
fsockopen, fread etc. etc.
It would be very simple to integrate this into the current PHP code base,
but to do so I think we would need to make some
On Thu, 8 Feb 2001, Stig Venaas wrote:
I've made the OpenSSL extension which currently doesn't do SSL
connections, so you may not be talking of me, my name's Stig but
not Bakken, just wondering if you were thinking of this, or if
Stig Bakken actually did work on this.
I read in the logs
"John" == John Donagher [EMAIL PROTECTED] writes:
John If you mean the ability to have PHP talk with an HTTPS server,
John it already exists in the form of the CURL extension.
It has been stated on the list that curl can only grab to a file, not
to php variable. Is that (still?) the case?
On 4 Feb 2001, James H. Cloos Jr. wrote:
"John" == John Donagher [EMAIL PROTECTED] writes:
John If you mean the ability to have PHP talk with an HTTPS server,
John it already exists in the form of the CURL extension.
It has been stated on the list that curl can only grab to a file, not
20 matches
Mail list logo
