[Python-bugs-list] [ python-Bugs-215026 ] SSL features undocumented

[noreply@sourceforge.net]

Bugs item #215026, was updated on 2000-09-21 15:29
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=215026&group_id=5470

Category: Documentation
Group: None
Status: Open
Resolution: Later
Priority: 4
Submitted By: Martin v. Löwis (loewis)
>Assigned to: Mark Hammond (mhammond)
Summary: SSL features undocumented

Initial Comment:
The socket.ssl function, and the SSL objects, are not documented.

----------------------------------------------------------------------

>Comment By: Tim Peters (tim_one)
Date: 2001-04-19 15:01

Message:
Logged In: YES 
user_id=31435

Assigned to MarkH on the off chance he runs SSL on 
Windows.  Mark, if you don't either, then nobody who runs 
on Windows cares about this enough to bother, so just 
reassign it to Fred for the doc-issue part of it.

----------------------------------------------------------------------

Comment By: Moshe Zadka (moshez)
Date: 2001-04-09 07:00

Message:
Logged In: YES 
user_id=11645

Test case is trivial:

>>> a = urllib2.urlopen('https://sourceforge.net')
>>> a.read(10)

And see that something comes out.

I can't help any more with that, I haven't seen a windows
machine for longer then Tim hasn't seen a socket...
Assigning back to tim -- if you can't solve it, someone more
qualified them me will have to solve it.

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2001-03-18 10:56

Message:
Logged In: YES 
user_id=31435

Sorry, Fred, I not only know nothing about SSL, I've never 
even used a socket!  I don't have a clue.  Maybe after the 
docs are written, I'll know how to test it <wink>.

Assigning back to Moshe, in the hope that he can at least 
attach a teensy test case I can run to let me know whether 
or not his suggestion works on Windows.  But someone will 
also have to tell me how to *compile* with SSL support on 
Windows -- e.g., I sure don't have any of the #include 
files it's looking for when USE_SSL is #define'd.

----------------------------------------------------------------------

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-03-18 08:28

Message:
Logged In: YES 
user_id=3066

Tim:  Can you look at Moshe's suggestion for the SSL on Windows?  Please assign back to me for the documentation issue afterwards.  Thanks!

----------------------------------------------------------------------

Comment By: Moshe Zadka (moshez)
Date: 2001-03-18 02:34

Message:
Logged In: YES 
user_id=11645

Fred, if any of the guys in PythonLabs has some spare times
and a windows machine, then inside the RAND_status() line,
you should put right after the USE_EGD #endif something like

#ifdef <whatever says it's windows>
RAND_screen()
#endif

I don't want to make this a formal patch submission because
I don't have any windows machine to test it on...

(And if we make an ssl module, it should just have a
RAND_* functions wrapped up and have all the smarts in
socket.py/ssl.py/<whatever>.

I don't have cycles to work on this, but this seemed like
a good place to braindump

----------------------------------------------------------------------

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2000-10-12 19:41

Message:
I should note that the SSL support in the socket module was discussed briefly at a PythonLabs meeting a few weeks ago in the context of a bug report complaining that the SSL code here wasn't portable to Windows.

We decided that SSL support probably belonged in a separate module in the first place, so all this might change in some future release.  Especially if anyone would like to fund some work on getting SSL support working across platforms.

----------------------------------------------------------------------

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2000-09-21 20:46

Message:
Low priority for 2.0, but reasonable patches will be considered.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=215026&group_id=5470