2017 year-end link clearance

And the customary plug for my series of short videos on One Dev Minute:

(While you're there, why not check out the other One Dev Minute videos?)

Comments (11)
  1. AsmGuru62 says:

    AsciiFlow rules!
    Impressive tool.

  2. Joshua says:

    Ref: Unquoted service paths. “Only administrators can create these files.” Wait what? On my newly installed Windows 10 I discovered I have write permission to C:\ without UAC elevation. I directly tested this from an unprivileged command prompt so it’s not explorer elevating behind my back.

    1. “This configuration error becomes a security issue only if additional misconfiguration of file system permissions allows non-admins to create files in locations that should be protected. In Windows XP and newer, non-admins can create subdirectories in the root directory of the system drive (typically “C:\”) but they cannot create files there. Permissions are set that way specifically to prevent this type of attack.” If you can create files in the root, then somebody messed up the security permissions after Windows was installed.

      1. 640k says:

        An unelevated non-admin can still move a file to the root of the system drive. I.e. what windows tries to prevent as default is totally useless, only an inconvenience, not any protection at all. As usual.

        1. I get “Access denied”. Please share details on how you were able to do this.

    2. Antonio Rodríguez says:

      I have taken the time to test it in Windows XP SP3, Windows 7 SP1 and Windows 10 RTM. In all of them, you can create a directory in the root of the system drive from a non-admin (“unelevated”) account, but when you try to create a file, you get an access denied error.

      I second Raymond. You (or somebody else) must have messed with the file system permissions. Maybe you are using one of those modified “all-in-one-with-drivers” Windows setup disks, which do more harm than benefit, because they also change setup settings to match the creator’s tastes and opinions – settings that Microsoft has established after extensive user, security and compatibility testing. As a software developer, I have found those unofficial install disks to be the root cause of many setup and compatibility problems for my applications.

      1. Joshua says:

        I found some machines of mine have it right. Time to start questioning media as you say.

  3. Ben Voigt says:

    In the asymptotic autoshape complexity paper, it seems like the axis labels for Figure 1 must be reversed in order to reach the same conclusions as the authors. As plotted, it seems that the DFA approach is extraordinarily effective, with only a few dozen autoshapes needed to solve problems larger than the data capacity of the Internet.

  4. Antonio Rodríguez says:

    IIRC, the story about Outlook’s Ctrl+F command has already been told in this blog. I already knew it, and I’m pretty sure I have heard of it from Raymond’s mouth (or keyboard :-P ).

  5. Mark Ransom says:

    Here’s a great one from last year: !!Con 2017: HDR Photography in Microsoft Excel?! by Kevin Chen. Any relation?


  6. Steve D says:

    To me, the Ctrl-X, Ctrl-C, Ctrl-V harks back to WordStar (except they were Ctrl-K+X, Ctrl-K+C, Ctrl-K+V respectively). Also the Turbo Pascal editor used the WordStar editing commands in most cases. Plenty of legacy experience out there by the time Windows became mainstream.

Comments are closed.

Skip to main content