Feature #8126: OpenSSL::SSL::SSLSocket does not define #recv and #send messages

• Status: Assigned
• Assignee: rhenium (Kazuki Yamaguchi)
• Target version: -

[postmodern (Hal Brodigan)]

OpenSSL::SSL::SSLSocket does not define #recv/#send methods and is not compatible with TCPSocket.

[postmodern (Hal Brodigan)]

Here is a list of methods which are defined by TCPSocket, but not SSLSocket:

• recvfrom
• shutdown
• getsockname
• getpeername
• local_address
• remote_address
• recv
• recv_nonblock
• do_not_reverse_lookup
• sendmsg
• sendmsg_nonblock
• recvmsg
• recvmsg_nonblock
• connect_address

[zzak (zzak _)]

Do you have a use-case for these methods? Or do you just want them added for consistency?

[MartinBosslet (Martin Bosslet)]

I agree that it would be better design if SSLSocket responded to the same interface that TCPSocket responds to. However, that's quite a bunch of methods, it would take quite a while to implement them all... Are there any methods in particular that you are missing the most from that list?

[lisukorin (Rafał Lisowski)]

I don't know how @postmodern but I miss the getpeername the most.

[zzak (zzak _)]

• Assignee changed from MartinBosslet (Martin Bosslet) to 7150

[naruse (Yui NARUSE)]

• Has duplicate Feature #12077: Consolidate SSLSocket interface with TCPSocket added

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Assigned
• Assignee changed from 7150 to rhenium (Kazuki Yamaguchi)

[jeremyevans0 (Jeremy Evans)]

• Tracker changed from Bug to Feature
• ruby -v deleted (ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-linux])