• Show log

    Commit

  • Hash : eddfbc38
    Author : Nick Wellnhofer
    Date : 2020-01-22T22:03:45

    Don't load external entity from xmlSAX2GetEntity
    
    Despite the comment, I can't see a reason why external entities must be
    loaded in the SAX handler. For external entities, the handler is
    typically first invoked via xmlParseReference which will later load the
    entity on its own if it wasn't loaded yet.
    
    The old code also lead to duplicated SAX events which makes it
    basically impossible to reuse xmlSAX2GetEntity for a custom SAX parser.
    See the change to the expected test output.
    
    Note that xmlSAX2GetEntity was loading the entity via
    xmlParseCtxtExternalEntity while xmlParseReference uses
    xmlParseExternalEntityPrivate. In the previous commit, the two
    functions were merged, trying to compensate for some slight differences
    between the two mostly identical implementations.
    
    But the more urgent reason for this change is that xmlParseReference
    has the facility to abort early when recursive entities are detected,
    avoiding what could practically amount to an infinite loop.
    
    If you want to backport this change, note that the previous three
    commits are required as well:
    
    f9ea1a24 Fix copying of entities in xmlParseReference
    5c7e0a9a Copy some XMLReader option flags to parser context
    1a3e584a Merge code paths loading external entities
    
    Found by OSS-Fuzz.
    

  • README

  •                   XML toolkit from the GNOME project
    
    Full documentation is available on-line at
        http://xmlsoft.org/
    
    This code is released under the MIT Licence see the Copyright file.
    
    To build on an Unixised setup:
       ./configure ; make ; make install
       if the ./configure file does not exist, run ./autogen.sh instead.
    To build on Windows:
       see instructions on win32/Readme.txt
    
    To assert build quality:
       on an Unixised setup:
          run make tests
       otherwise:
           There is 3 standalone tools runtest.c runsuite.c testapi.c, which
           should compile as part of the build or as any application would.
           Launch them from this directory to get results, runtest checks 
           the proper functionning of libxml2 main APIs while testapi does
           a full coverage check. Report failures to the list.
    
    To report bugs, follow the instructions at: 
      http://xmlsoft.org/bugs.html
    
    A mailing-list xml@gnome.org is available, to subscribe:
        http://mail.gnome.org/mailman/listinfo/xml
    
    The list archive is at:
        http://mail.gnome.org/archives/xml/
    
    All technical answers asked privately will be automatically answered on
    the list and archived for public access unless privacy is explicitly
    required and justified.
    
    Daniel Veillard
    
    $Id$