interesting article about long_path problems. and OllyDbg is mentioned there.

http://www.offensivecomputing.net/?q=node/1649

http://www.icewall.pl/download/longpaths.pdf

...those things that read 'buffer overflow' in AV are scaring, really scaring... nice read, thanks!


...and yes, we do *rarely* remember when coding that windows allows UNC naming, thus bringing us to 32k chars...

interesting thing, those BO can only happen because those developers used unsafe memory/string functions, and didnt even enforce a terminator at end... eheh, funny being done by them.

now i did test Ollydbg v2.00.01
it not accepts longer filename neither via DragDrop or OpenFile