News for hackers. Stuff that matters.
Re:MS Teams channels cannot contain MS-DOS device names by ChrisSD on Thursday August 10, 2023 @11:53AM (#37077769)
On Unix perhaps. Windows forced IT folks to deal with the issue by having folders like "Program Files". Even the user's folder used to be in "Documents and Settings" (but they backed down from that eventually and now it's just "Users").
Re:MS Teams channels cannot contain MS-DOS device names by WirelessGigabit on Thursday August 10, 2023 @12:41PM (#37078434)
To this date one needs to be careful with executing applications and spaces in the path.

For example:

    D:\test>dir
    ...
    08/10/2023  09:29 AM    <DIR>          .
    08/10/2023  09:30 AM    <DIR>          Foo Bar
    08/10/2023  09:35 AM                79 Foo.bat
    ...

    D:\test>dir "Foo Bar"
    ...
    08/10/2023  09:30 AM    <DIR>          .
    08/10/2023  09:29 AM    <DIR>          ..
    08/10/2023  09:35 AM                79 Foo.bat
    ...
        
    D:\test>type Foo.bat
    @echo off
    echo Executable: %0
    echo Path to executable: %~dp0
    echo Params: %*

    D:\test>type "Foo Bar\Foo.bat"
    @echo off
    echo Executable: %0
    echo Path to executable: %~dp0
    echo Params: %*

    D:\test>Foo.bat hello
    Executable: Foo.bat
    Path to executable: D:\test\
    Params: hello
    
    D:\test>Foo Bar\Foo.bat hello
    Executable: Foo
    Path to executable: D:\test\
    Params: Bar\Foo.bat hello
    
    D:\test>"Foo Bar\Foo.bat" hello
    Executable: "Foo Bar\Foo.bat"
    Path to executable: D:\test\Foo Bar\
    Params: hello

    D:\test>
Mess up the quotes and you're executing something one level up.
Re:MS Teams channels cannot contain MS-DOS device names by keepamovin on Friday August 11, 2023 @06:48AM (#37087200)
Nice example!
Re:MS Teams channels cannot contain MS-DOS device names by ChrisSD on Friday August 11, 2023 @07:52AM (#37087629)
Right, but my point is that "Program Files" &co were so common that it forced IT people (and everybody else) to handle this correctly. Executing something one level up is not the kind of bug that's going to be unnoticed when it'll be hit so often.

(btw most IT folks prefer powershell, if only because all the management tools are powershell modules)

Re:MS Teams channels cannot contain MS-DOS device names by justsomehnguy on Thursday August 10, 2023 @12:37PM (#37078374)
> but they backed down from that eventually

Only because they were started to hit MAX_PATH there:

    C:\Users\Johnathan Aparecido da Silva\AppData\Local\ASUS\ASUS System Control Interface\AsusSoftwareManager
    C:\Documents and Settings\Johnathan Aparecido da Silva\AppData\Local\ASUS\ASUS System Control Interface\AsusSoftwareManager
Re:MS Teams channels cannot contain MS-DOS device names by nomel on Friday August 11, 2023 @01:26PM (#37091294)
The `subst` command provides an easy way around that. Link the last folder somewhere closer to the root, to make longe-than-255 paths accessible. Then, when you're done, remove the link and your files are protected from pesky things like virus/malware scanners.

I used it to hide my old virus/malware collection, made from what my computer was infected with through the years.

Re:MS Teams channels cannot contain MS-DOS device names by xp84 on Thursday August 10, 2023 @02:43PM (#37080073)
This was actually genius, though it was/is so annoying typing these verbose paths
Re:MS Teams channels cannot contain MS-DOS device names by keepamovin on Friday August 11, 2023 @06:48AM (#37087202)
Agree. Those short abbreviations have a kind of crunchy sonic quality when you say them that’s satisfying.