git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Intricacies of submodules

From
Avery Pennarun <apenwarr@gmail.com>
Date
Apr 18, 2008, 18:30 UTC
Message-ID
<32541b130804181130s21e6ea5bm38ea0b35cd009d3e@mail.gmail.com>
In-Reply-To
<32541b130804181128j57d76edcsbbd5fb8d4c782ae7@mail.gmail.com>
On 4/17/08, Junio C Hamano <gitster@pobox.com> wrote:
Show 8 quoted lines
> Linus Torvalds <torvalds@linux-foundation.org> writes:
>  > So if we do end up doing a "tracked config file", I'd personally very much
>  > prefer it be limited in some way. For example, we obviously track the
>  > .gitignore and .gitattributes files, but they are much more limited in
>  > their effects. Maybe we could have a "limited config file" that allows for
>  > *some* config options to be set?
>
> Yes, that's all what I have been trying to say ;-)

How about this: we know that *most* options are harmless, at least from a security point of view. AFAIK it's really just the ones where you specify shell commands that are unsafe.

Why not have a list of "safe" config options in git, and when reading .gitconfig, error out if any of the options in that file are unsafe. (Alternatively: silently ignore the unsafe ones, or warn and then ignore the unsafe ones.) A more advanced variation of the same would be to have .git/config options that list specific exceptions to the safe list, so if .gitconfig causes an error, you can *explicitly* git config set to let .gitconfig override them.

Another possibility would be to have an "unsafe" list instead of a "safe" list, but that sounds rather error-prone to me.

Have fun,
Avery
Previous: Avery Pennarun
Message 48 of 48 in “Migrating svn to git with heavy use of externals”
  1. D. Stuart FreemanMar 31, 2008
  2. D. Stuart FreemanApr 8, 2008
  3. Avery PennarunApr 8, 2008
  4. D. Stuart FreemanApr 8, 2008
  5. Avery PennarunApr 8, 2008
  6. D. Stuart FreemanApr 8, 2008
  7. Roman ShaposhnikApr 9, 2008
  8. Avery PennarunApr 9, 2008
  9. Roman ShaposhnikApr 9, 2008
  10. Avery PennarunApr 9, 2008
  11. Junio C HamanoApr 9, 2008
  12. Intricacies of submodules [was: Migrating svn to git with heavy use of externals]Roman Shaposhnik, Apr 10, 2008
  13. Junio C HamanoApr 10, 2008
  14. Roman ShaposhnikApr 10, 2008
  15. Junio C HamanoApr 11, 2008
  16. Ping YinApr 11, 2008
  17. Junio C HamanoApr 11, 2008
  18. Roman ShaposhnikApr 12, 2008
  19. Junio C HamanoApr 12, 2008
  20. Roman ShaposhnikApr 14, 2008
  21. Junio C HamanoApr 15, 2008
  22. Ping YinApr 15, 2008
  23. Roman V. ShaposhnikApr 16, 2008
  24. Jeremy Maitin-ShepardApr 17, 2008
  25. Linus TorvaldsApr 17, 2008
  26. Junio C HamanoApr 17, 2008
  27. Roman V. ShaposhnikApr 17, 2008
  28. Martin LanghoffApr 17, 2008
  29. Junio C HamanoApr 17, 2008
  30. Sverre RabbelierApr 17, 2008
  31. Martin LanghoffApr 17, 2008
  32. Sverre RabbelierApr 17, 2008
  33. Martin LanghoffApr 17, 2008
  34. Ping YinApr 18, 2008
  35. Dmitry PotapovApr 17, 2008
  36. Linus TorvaldsApr 17, 2008
  37. Ping YinApr 18, 2008
  38. Jakub NarebskiApr 18, 2008
  39. Ping YinApr 12, 2008
  40. Roman ShaposhnikApr 14, 2008
  41. Ping YinApr 12, 2008
  42. Junio C HamanoApr 12, 2008
  43. Ping YinApr 12, 2008
  44. Ping YinApr 10, 2008
  45. Roman ShaposhnikApr 10, 2008
  46. Intricacies of submodules [was: Migrating svn to git with heavy use of externals]Roman Shaposhnik, Apr 9, 2008
  47. Avery PennarunApr 9, 2008
  48. Avery PennarunApr 18, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.