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

Add checks if the file or dir names are sane. #233

Closed
wants to merge 1 commit into from

Conversation

sgolovan
Copy link
Contributor

@sgolovan sgolovan commented Feb 9, 2014

lib/inets/src/ftp/ftp.erl: Check the filenames, usernames, passwords etc...
for and in them and return error if these offending chars
are found. See http://erlang.org/pipermail/erlang-bugs/2014-January/003998.html
for details.
lib/inets/test/ftp_suite_lib.erl: Added checks for in file and directory
names.

…etc.

    for <CR> and <LF> in them and return error if these offending chars
    are found. See http://erlang.org/pipermail/erlang-bugs/2014-January/003998.html
    for details.
lib/inets/test/ftp_suite_lib.erl: Added checks for <CR><LF> in file and directory
    names.
@OTP-Maintainer
Copy link

Patch has passed first testings and has been assigned to be reviewed

@nox
Copy link
Contributor

nox commented Feb 14, 2014

@sgolovan The commit title is a tad too long. Also, shouldn't the functions crash on illegal input? It looks weird to me to return euser when the command wasn't even send to the remote server.

@sgolovan
Copy link
Contributor Author

Well, I didn't find any mention of crashing in ftp man page, so I tried not to introduce any. euser seems to be appropriate error condition since the FTP RFC doesn't allow \r\n in user names, so there can't be such a user. Though it's not too difficult to change all returns to throws (I'm just not sure what to throw out).

@proxyles
Copy link
Contributor

Graduated

@proxyles proxyles closed this Feb 24, 2014
uabboli pushed a commit to uabboli/otp that referenced this pull request Dec 1, 2020
This commit fixes erlang#221 and updates the way the targeted implementation
shrinks its instances. PropEr now tries to find the best shrinker
between the original generator and the neighborhood function.

Users can now also specify ?SHRINK macros in the neighborhood
function, which will take precedence.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants