Comments by "TheEvilCottonBall" (@alexandermaximilianoetken7265) on "Mental Outlaw" channel.

  1. By the way even Windows APIs find it too difficult to encode separate args into a command-line string. You can get the arguments out of the command line string by calling CommandLineToArgv but the windows APIs provide no encoder (i. e. there is no ArgvToCommandLine). Rust got the implementation of this encoder wrong. (ya see folks, microsoft wisely did not even try)
    58
  2. Device encryption does not even show up in my settings. spooky.
    2
  3. > More verbose and detailed Event Viewer logs. Yeah make a large language model add more gobbledygook too make it more verbose.
    2
  4. 3:17 Windows has never made a good search. The windows XP search mutt was often slow and often did not always find it even when it is there.
    2
  5. Post your BitLocker Keys down below, so you can be look them up on Youtube when you need them.
    1
  6. > Here's the thing: cmd.exe has a completely different decoder Well you mean that cmd does not use CommandLineToArgvW. well, CommandlineToArgv would split `hello" & mspaint.exe` into `hello` and `& mspaint.exe`, so probably yes. > it's just it's not the only encoding they need to care about. Well windows has weird rules about argument quoting. I read an article "A Better Way To Understand Quoting and Escaping of Windows Command Line Arguments" once but it now only available on the archive that explains it. > All those vulnerable runtimes Well most of the programs that are using these decoders are not shells, so they will not run arbitrary commands. If you already have access to the commandline flags, then you can often pretty much everything the program can do, there is no need to trick the argument parser.
    1
  7.  @dm-vh3xj  Well I was talking about the standard rules. Of course you can parse the way you want.
    1