News for hackers. Stuff that matters.
Re:Zip Bomb by TazeTSchnitzel on Friday October 05, 2012 @11:24AM (#4617252)
One of many examples of why Windows's arbitrary path length restriction is ridiculous.
Re:Zip Bomb by duskwuff on Friday October 05, 2012 @12:24PM (#4617509)
Most UNIX systems have a PATH_MAX. It's not just Windows.
Re:Zip Bomb by krakensden on Friday October 05, 2012 @08:23PM (#4619296)
PATH_MAX is defined but meaningless on both Linux and OS X.
Re:Zip Bomb by comex on Friday October 05, 2012 @09:43PM (#4619476)
Unfortunately, this is not true. The OS X kernel can't deal with paths longer than MAXPATHLEN, which is defined as 1024.
Re:Zip Bomb by TazeTSchnitzel on Friday October 05, 2012 @03:27PM (#4618288)
Perhaps, but Windows's is a bit too low.
Re:Zip Bomb by hoov on Friday October 05, 2012 @04:45PM (#4618607)
While MAX_PATH is 260, most of the Unicode variants of the API functions allow for paths of 32,767 characters [1]. That seems like a decent length.

[1] http://msdn.microsoft.com/en-us/library/windows/desktop/aa36...

Re:Zip Bomb by gburt on Friday October 05, 2012 @06:38PM (#4618989)
So there's a constant for path length that only applies sometimes...
Re:Zip Bomb by flatline on Friday October 05, 2012 @11:08PM (#4619626)
This is also the case on Unix. According to Advanced Programming in the Unix Environment, it is true of many of these so-called limits. The POSIX standard defined many values that were too small for modern-day use, such as _POSIX_PATH_MAX set to 255. The non-posix values are not all defined in limits.h, and must be queried at runtime. Even then, some are indeterminate. But at least you're not relegated to 255 characters;)
Re:Zip Bomb by TazeTSchnitzel on Friday October 05, 2012 @04:53PM (#4618638)
Oh, that's somewhat reassuring. I'll surely benefit from it in 10 years time. :/
Re:Zip Bomb by hoov on Saturday October 06, 2012 @03:00PM (#4621344)
I'm not sure that I know what you mean. These functions aren't obscure and have been around for quite a while. For example: CreateFileW [1]. It's just good hygiene to use the Unicode variants and normalize to UNC where appropriate. This has been the case for years.

[1] http://msdn.microsoft.com/en-us/library/windows/desktop/aa36...

Re:Zip Bomb by TazeTSchnitzel on Saturday October 06, 2012 @03:02PM (#4621355)
I mean that to maintain compatibility with legacy stuff I expect I won't be able to take advantage of it for quite a while.
Re:Zip Bomb by im3w1l on Friday October 05, 2012 @03:04PM (#4618198)
The write limit should be lower than the read limit.