Anyone using a backslash as a path component separator should be taken offline permanently.
'char** argv' will pass, but it's sloppy, lame, and not 100% syntactically accurate.
There's an illegal character on line 2.
Where is 'value' declared? And '= =' is not a true operator.
And so forth.
Then again, this was probably made for the diversity crowd.
The politics of no expectations.
# List of acceptable shells for chpass(1).
# Ftpd will not allow users to connect who are not using
# one of these shells.
/bin/bash
/bin/csh
/bin/ksh
/bin/sh
/bin/tcsh
/bin/zsh
The time's long gone that a backslashing, eminently and eternally vulnerable Windows made any sense. We don't want to hear how good you are at patching vulnerabilities - you've certainly had more practice than anyone else in the industry. If Upton Sinclair were alive today, he'd have another topic for his most famous book.
'What a crazy year 2019 has been for the Windows command line!' - Kayla Cinnamon
About Rixstep
Stockholm/London-based Rixstep are a constellation of programmers and support staff from Radsoft Laboratories who tired of Windows vulnerabilities, Linux driver issues, and cursing x86 hardware all day long. Rixstep have many years of experience behind their efforts, with teaching and consulting credentials from the likes of British Aerospace, General Electric, Lockheed Martin, Lloyds TSB, SAAB Defence Systems, British Broadcasting Corporation, Barclays Bank, IBM, Microsoft, and Sony/Ericsson.
Rixstep and Radsoft products are or have been in use by Sweden's Royal Mail, Sony/Ericsson, the US Department of Defense, the offices of the US Supreme Court, the Government of Western Australia, the German Federal Police, Verizon Wireless, Los Alamos National Laboratory, Microsoft Corporation, the New York Times, Apple Inc, Oxford University, and hundreds of research institutes around the globe. See here.