Hello there,
Can pike 7.6 be bumped version ? Because Bill have fixed some SSL problems that can help us @Caudium Group to identifiate the good pike to run with Caudium 1.3 ?
7.6.11 is from 01/07/2004... So it can be good to have 7.6.13 from August ?
Thanks, /Xavier
-- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects
Why skip a version?
/ Marcus Agehall (nu med semester)
Previous text:
2004-08-05 12:17: Subject: pike 7.6 bump version ?
Hello there,
Can pike 7.6 be bumped version ? Because Bill have fixed some SSL problems that can help us @Caudium Group to identifiate the good pike to run with Caudium 1.3 ?
7.6.11 is from 01/07/2004... So it can be good to have 7.6.13 from August ?
Thanks, /Xavier
-- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects
/ Brevbäraren
Le 5 août 04, à 12:30, Marcus Agehall (nu med semester) @ Pike (-) developers forum a écrit :
Why skip a version?
Because 7.6.12 is known stable and 7.6.13 is the new working cvs tree :p
/Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects
That way, you get one version number in-between which is frozen in time, whereas a checked-out version that claims to be .11 can be anything from January(?) 2004 to August, and .13 could be anything from August 2004 to, say, March 2006, or whenever we bumb versions the next time. .12 will be from 18:35:11, August 5, 2004 UTC (or similar). Which is often a good thing.
/ Johan Sundström (Achtung Liebe!)
Previous text:
2004-08-05 12:25: Subject: pike 7.6 bump version ?
Why skip a version?
/ Marcus Agehall (nu med semester)
*Duh* -I knew that. Think I left my brain at home this morning...
/ Marcus Agehall (nu med semester)
Previous text:
2004-08-05 12:32: Subject: pike 7.6 bump version ?
That way, you get one version number in-between which is frozen in time, whereas a checked-out version that claims to be .11 can be anything from January(?) 2004 to August, and .13 could be anything from August 2004 to, say, March 2006, or whenever we bumb versions the next time. .12 will be from 18:35:11, August 5, 2004 UTC (or similar). Which is often a good thing.
/ Johan Sundström (Achtung Liebe!)
That is always very welcome -- as soon as something even the slightest bit substantial has been fixed it is a Good Thing to bump revisions. There even is a make target in the makefile that anyone who has commit privileges in cvs can run. Please go ahead. :-)
/ Johan Sundström (Achtung Liebe!)
Previous text:
2004-08-05 12:17: Subject: pike 7.6 bump version ?
Hello there,
Can pike 7.6 be bumped version ? Because Bill have fixed some SSL problems that can help us @Caudium Group to identifiate the good pike to run with Caudium 1.3 ?
7.6.11 is from 01/07/2004... So it can be good to have 7.6.13 from August ?
Thanks, /Xavier
-- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects
/ Brevbäraren
I'm still having problems using the pike ssl server component with any client application based on openssl. I've replicated the behavior with wget and the openssl s_client program. Something in the handshake fails, and I think I've got it narrowed down, but I'm not familiar enough with the code or the ssl spec to fix it. It looks like openssl is failing on a data read during the handshake.
If there are any ssl gurus out there that can help me out with this, let me know... openssl is probably the most popular ssl toolkit, and we probably ought to have interoperability with it.
Bill
/ hww3
Previous text:
2004-08-05 12:17: Subject: pike 7.6 bump version ?
Hello there,
Can pike 7.6 be bumped version ? Because Bill have fixed some SSL problems that can help us @Caudium Group to identifiate the good pike to run with Caudium 1.3 ?
7.6.11 is from 01/07/2004... So it can be good to have 7.6.13 from August ?
Thanks, /Xavier
-- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects
/ Brevbäraren
Grubba and I fixed a padding bug in the handshake some weeks ago. It sounds very much like the same one.
/ Martin Stjernholm, Roxen IS
Previous text:
2004-08-05 15:29: Subject: ssl problems
I'm still having problems using the pike ssl server component with any client application based on openssl. I've replicated the behavior with wget and the openssl s_client program. Something in the handshake fails, and I think I've got it narrowed down, but I'm not familiar enough with the code or the ssl spec to fix it. It looks like openssl is failing on a data read during the handshake.
If there are any ssl gurus out there that can help me out with this, let me know... openssl is probably the most popular ssl toolkit, and we probably ought to have interoperability with it.
Bill
/ hww3
pike-devel@lists.lysator.liu.se
-
hww3 ＠ Pike developers forum -
Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum
-
Marcus Agehall (nu med semester) ＠ Pike (-) developers forum
-
Martin Stjernholm, Roxen IS ＠ Pike developers forum
-
Xavier Beaudouin