6 Commits

Author	SHA1	Message	Date
Daniel Stenberg	6832c1d4b2	checksrc: move open braces to comply with function declaration style	2016-11-24 23:58:22 +01:00
Daniel Stenberg	d4d87d7ead	unit1604: fix snprintf ... follow-up to 0326b06 sizeof(pointer) is no good for the buffer size! Reported-by: Viktor Szakats	2016-04-03 10:47:13 +02:00
Steve Holme	0326b06770	unittests: Fixed compilation warnings ... warning: implicit declaration of function 'sprintf_was_used' [-Wimplicit-function-declaration] Follow up to the modications made to tests/libtest in commit 55452ebdff as we prefer not to use sprintf() now.	2016-04-03 00:02:19 +01:00
Jay Satiro	4fc80f3e75	tool_doswin: Support for literal path prefix \\?\ ... For example something like --output \\?\C:\foo	2016-02-09 03:28:58 -05:00
Jay Satiro	a6208704e7	unit1604: Fix unit setup return code	2016-02-05 13:37:39 -05:00
Jay Satiro	4520534e6d	tool_doswin: Improve sanitization processing ... - Add unit test 1604 to test the sanitize_file_name function. - Use -DCURL_STATICLIB when building libcurltool for unit testing. - Better detection of reserved DOS device names. - New flags to modify sanitize behavior: SANITIZE_ALLOW_COLONS: Allow colons SANITIZE_ALLOW_PATH: Allow path separators and colons SANITIZE_ALLOW_RESERVED: Allow reserved device names SANITIZE_ALLOW_TRUNCATE: Allow truncating a long filename - Restore sanitization of banned characters from user-specified outfile. Prior to this commit sanitization of a user-specified outfile was temporarily disabled in 2b6dadc because there was no way to allow path separators and colons through while replacing other banned characters. Now in such a case we call the sanitize function with SANITIZE_ALLOW_PATH which allows path separators and colons to pass through. Closes https://github.com/curl/curl/issues/624 Reported-by: Octavio Schroeder	2016-02-05 01:44:27 -05:00