RE: [Full-Disclosure] M$ - so what should they do?

From: Stuart Fox (DSL AK) (StuartF_at_datacom.co.nz)
Date: 06/22/04

  • Next message: Valdis.Kletnieks_at_vt.edu: "Re: [Full-Disclosure] M$ - so what should they do?" 
    To: Eric Paynter <eric@arcticbears.com>, full-disclosure@lists.netsys.com
Date: Tue, 22 Jun 2004 13:14:14 +1200

     

    >
    >
    > Having all the configs as text files in /etc works fine for
    > Unix-like systems. You can use any editor to look at the
    > config - no need for some proprietary editor (regedit).
    > Automating config changes is as easy as writing a simple
    > shell script. Each config is named after its application, so
    > it's easy to know which is which, and if you need to restore
    > an application, just install the app then copy your backup
    > config file into place. As a matter of fact, an entire system
    > can be restored by re-installing the apps and only restoring
    > /etc (configs) and /home (user
    > data) from backup. Try that on Windows. Have you ever had a
    > successful Windows restore without a full system backup or
    > without re-configuring everything from scratch? It is
    > extremely difficult. Why? Because of the registry...
    >
    > The "config file mess" is an excuse made up by MS to sell the
    > registry concept. The registry does not make it easier to
    > manage application configuration. Instead, it makes it
    > considerably more complex.
    >
    > The real reason for the registry is to make it difficult to
    > copy an application from one machine to another. In other
    > words, it's a copy proctection scheme. Remember in the days
    > of Win 3.1, you could do that? It all broke in Win95 with the
    > registry.

    You've got some valid points but there is one thing that you've overlooked -
    auditing. One of the(few) advantages that the registry does have is that
    you can configure auditing on individual keys, so that if you want to you
    can track who made changes and when. With text files, you simply don't have
    that option (of course you can audit changes to the entire file). Having
    said that, I've never actually met anyone who uses the registry auditing,
    but I'm sure they're out there.

    Some of your points are also a bit dubious - registry mods are mostly
    scriptable (except binary data - one of my big gripes with the registry),
    and I'm not sure that it makes application configuration any more or less
    complex - they each have their advantages and disadvantages. As for copying
    applications, the issues are a bit deeper than the registry - if it was just
    the registry it would be easy enough to export & import the relevant keys
    (they are well structured). It tends to be more related to issues such as
    dll's needing to be registered etc.

    _______________________________________________
    Full-Disclosure - We believe in it.
    Charter: http://lists.netsys.com/full-disclosure-charter.html

  • Next message: Valdis.Kletnieks_at_vt.edu: "Re: [Full-Disclosure] M$ - so what should they do?"

    Relevant Pages

    • RE: [Full-Disclosure] M$ - so what should they do?
      ... proprietary editor. ... file system API to open and display the config files. ... can you use any editor that uses the registry API to open and display the ...
      (Full-Disclosure)
    • Re: STOP 0x74
      ... How to recover from a corrupted registry that prevents Windows XP from ... I looked at the hives in config and the restore point they were all ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: How to use ADO fast?
      ... I used to do the Registry thing but a lot of our clients don't ... config files. ... >> Cor, hardcoding connection string is silly by any mean, trust us. ...
      (microsoft.public.dotnet.framework.adonet)
    • Re: [Python-Dev] ConfigParser shootout, preliminary entry
      ... > Has anyone discussed using the csv module as the basic file interface for config data? ... > registry entry with the name of a real ini file can divert apparent operations on ... > the file to operations on the registry (for windows apps using the windows API). ... The registry is a terrible way to store config information IMHO. ...
      (comp.lang.python)
    • Re: Configuration variables
      ... not everyone is chomping at the bit to let you hit their registry. ... Config files are great and easy to use, but currently they don't let you ... If you have a ton of people all of whom store custom settings, ...
      (microsoft.public.dotnet.general)