Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect OOB data management on FreeBSD #77

Closed
giampaolo opened this issue May 28, 2014 · 6 comments
Closed

Incorrect OOB data management on FreeBSD #77

giampaolo opened this issue May 28, 2014 · 6 comments
Assignees
Labels
bug Component-Library imported imported from old googlecode site and very likely outdated OpSys-BSD

Comments

@giampaolo
Copy link
Owner

From billiej...@gmail.com on September 10, 2008 15:29:18

What steps will reproduce the problem?  
1. Set up a common FTP server.
2. Connect with a client and send a command using OOB (urgent) data (e.g.
ABOR or STAT commands).

A discussion about this issue has been raised on the list: 
http://groups.google.com/group/pyftpdlib/browse_thread/thread/9a54f4f22c0609f0 

What is the expected output?  


What do you see instead?  
The server prints the following message disconnecting the client.

[test]@x:52291 Can't handle OOB data.
[test]@x:52291 Disconnected. 

The reason for that is that when we try to read OOB data on FreeBSD an
EINVAL error is raised.
A read at Unix Network Programming third edition reveals that this is the
expected behavior:

"4. If the process has set the SO_OOBINLINE socket option and then tries
to read the out-of-band data by specifying MSG_OOB, EINVAL is returned."

The patch in attachment modifies ftpserver.py so that SO_OOBINLINE option
is set against the command channel's socket and if reading OOB data from
the socket results in an EINVAL error we just pass on.

Attachment: ftpserver.patch

Original issue: http://code.google.com/p/pyftpdlib/issues/detail?id=77

@giampaolo giampaolo self-assigned this May 28, 2014
@giampaolo
Copy link
Owner Author

From billiej...@gmail.com on September 10, 2008 06:29:48

Summary: Incorrect OOB data management on FreeBSD

@giampaolo
Copy link
Owner Author

From billiej...@gmail.com on September 10, 2008 08:27:06

Fixed in r379 .
Thanks to Equand for the issue report.

Status: Finished

@giampaolo
Copy link
Owner Author

From billiej...@gmail.com on September 14, 2008 15:35:54

Labels: -OpSys-UNIX OpSys-BSD

@giampaolo
Copy link
Owner Author

From billiej...@gmail.com on September 20, 2008 11:15:03

Fixed/Implemented in version 0.5.0 which is released now.

Status: Fixed

@giampaolo
Copy link
Owner Author

From billiej...@gmail.com on October 13, 2008 12:13:14

Labels: Component-Library

@giampaolo
Copy link
Owner Author

From g.rodola on August 11, 2010 15:20:02

Owner: g.rodola

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Component-Library imported imported from old googlecode site and very likely outdated OpSys-BSD
Projects
None yet
Development

No branches or pull requests

1 participant