1. 11 Jul, 2010 1 commit
  2. 21 Apr, 2010 1 commit
  3. 14 Feb, 2010 1 commit
  4. 07 Feb, 2010 1 commit
  5. 04 Feb, 2010 1 commit
  6. 23 Jan, 2010 1 commit
  7. 21 Dec, 2009 1 commit
  8. 26 Aug, 2009 1 commit
  9. 25 Aug, 2009 1 commit
  10. 24 Aug, 2009 4 commits
  11. 31 May, 2009 1 commit
  12. 09 Dec, 2008 2 commits
  13. 06 Sep, 2008 1 commit
  14. 29 Aug, 2008 1 commit
    • Laurent Aimar's avatar
      Improved config_chain parsing by using escape for \ " and ' (close #1952) · ce1a1d96
      Laurent Aimar authored
      It also add checks against failed malloc.
      
      The option value should be escaped by \ for the mentionned characters and
      only for them (and only one time).
      
      For example
       dst="test \"ok\".mp3"
      will assign the value
       test "ok".mp3
      to the option dst.
      
      The following one
       dst="c:\test\\'bla'bla.txt"
      will assign the value
       c:\test\'bla'bla.txt
      
      You can use the functions
      - config_StringEscape (allocates memory)
      - config_StringUnescape (does not allocate memory).
      ce1a1d96
  15. 13 Aug, 2008 1 commit
  16. 11 Aug, 2008 1 commit
  17. 14 Jun, 2008 1 commit
  18. 06 Jun, 2008 1 commit
  19. 22 May, 2008 1 commit
  20. 08 May, 2008 1 commit
  21. 05 May, 2008 3 commits
  22. 14 Apr, 2008 1 commit
  23. 08 Mar, 2008 1 commit
  24. 03 Mar, 2008 1 commit
  25. 24 Jan, 2008 2 commits
  26. 16 Jan, 2008 3 commits
    • Damien Fouilleul's avatar
      vlc security: As i've seen very little improvement on that front, i've decided... · 658b4f83
      Damien Fouilleul authored
      vlc security: As i've seen very little improvement on that front, i've decided to check in my take on handling the problem of managing harmful options. I'm pretty sure this is going to be very controversial, but I think my approach is quite simple and yet very effective Anyway, my approach makes the following assumptions:
      
      - most vlc options are considered safe, only a handful are particularily unsafe and need be declared as such in their definition (they mostly deal with writing to an output file or URL)
      - unsafe options are only considered potentially harmful when used as an input option, ie. the ':option' format. Configuration options are always considered safe 'i.e --option' 
      - unsafe options are associated with a global security policy, which dictates how these are handled. At the moment, The policy can be either block, allow or prompt, and is set using the '--security-policy' option (which itself is considered unsafe ;)
      
      the policy can be set by the user at the command line or in the preferences, it curently defaults to prompt, which is the desirable state for deskop use. However, it can be overriden depending on context, for example, the activex and mozilla will force the security-policy to block regardless of preference settins.
      
      the code is a bit rough at the moment, but i will optimize/clean it up if the dev community this approach is worth keeping.
      
      try the following example, and you'll see quickly what i mean:
      
      ./vlc -vvv <a mrl> :sout=#transcode{vcodec=mp1v,vb=1024,acodec=mpga,ab=192}:standard{mux=ts,dst=vlc-output.ts,access=file}"
      
      Enjoy,
         Damien
      
      
      658b4f83
    • Rémi Denis-Courmont's avatar
    • Rafaël Carré's avatar
      input options whitelisting: 1st step · 9e5ebb07
      Rafaël Carré authored
      9e5ebb07
  27. 26 Dec, 2007 1 commit
  28. 21 Dec, 2007 1 commit
  29. 17 Dec, 2007 3 commits