From noreply at sourceforge.net  Tue May  1 01:11:20 2012
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 30 Apr 2012 16:11:20 -0700
Subject: [Expat-bugs] [ expat-Bugs-3522658 ] GetAttributeInfo missing from
	def file
Message-ID: <3VhM226Fh8zMj1@mail.python.org>

Bugs item #3522658, was opened at 2012-04-30 16:11
Message generated for change (Tracker Item Submitted) made by skelband
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3522658&group_id=10127

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build control
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Ralph Little (skelband)
Assigned to: Greg Stein (gstein)
Summary:  GetAttributeInfo missing from def file

Initial Comment:
The new GetAttributeInfo() function is missing from the libexpat.def file for inclusion as an export in the generated libexpat.dll
Please add the following to the end of the file lib/libexpat.def:

; added with version 2.1.0
  XML_GetAttributeInfo

Thanks!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3522658&group_id=10127

From noreply at sourceforge.net  Tue May  1 01:14:03 2012
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 30 Apr 2012 16:14:03 -0700
Subject: [Expat-bugs] [ expat-Bugs-3522658 ] GetAttributeInfo missing from
	def file
Message-ID: <3VhM594w9yzMlP@mail.python.org>

Bugs item #3522658, was opened at 2012-04-30 16:11
Message generated for change (Comment added) made by skelband
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3522658&group_id=10127

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build control
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Ralph Little (skelband)
Assigned to: Greg Stein (gstein)
Summary:  GetAttributeInfo missing from def file

Initial Comment:
The new GetAttributeInfo() function is missing from the libexpat.def file for inclusion as an export in the generated libexpat.dll
Please add the following to the end of the file lib/libexpat.def:

; added with version 2.1.0
  XML_GetAttributeInfo

Thanks!

----------------------------------------------------------------------

>Comment By: Ralph Little (skelband)
Date: 2012-04-30 16:14

Message:
Better yet, I missed the ordinal:

; added with version 2.1.0
  XML_GetAttributeInfo @66


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3522658&group_id=10127

From noreply at sourceforge.net  Sun May  6 02:10:47 2012
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 05 May 2012 17:10:47 -0700
Subject: [Expat-bugs] [ expat-Bugs-3522658 ] GetAttributeInfo missing from
	def file
Message-ID: <3VlS6M3KljzMjg@mail.python.org>

Bugs item #3522658, was opened at 2012-04-30 16:11
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3522658&group_id=10127

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build control
Group: None
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Ralph Little (skelband)
>Assigned to: Karl Waclawek (kwaclaw)
Summary:  GetAttributeInfo missing from def file

Initial Comment:
The new GetAttributeInfo() function is missing from the libexpat.def file for inclusion as an export in the generated libexpat.dll
Please add the following to the end of the file lib/libexpat.def:

; added with version 2.1.0
  XML_GetAttributeInfo

Thanks!

----------------------------------------------------------------------

>Comment By: Karl Waclawek (kwaclaw)
Date: 2012-05-05 17:10

Message:
Yes, that is an omission. However, I can only add it as commented out, as
this would break the default build which excludes this function. I also
forgot to add XML_SetHashSalt. These issues are fixed in libexpat(w).dev
rev. 1.10.

----------------------------------------------------------------------

Comment By: Ralph Little (skelband)
Date: 2012-04-30 16:14

Message:
Better yet, I missed the ordinal:

; added with version 2.1.0
  XML_GetAttributeInfo @66


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3522658&group_id=10127

From noreply at sourceforge.net  Tue May  8 15:56:43 2012
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 08 May 2012 06:56:43 -0700
Subject: [Expat-bugs] [ expat-Bugs-3524730 ] potential null pointer
	dereference
Message-ID: <3Vn2LV3WjszN1T@mail.python.org>

Bugs item #3524730, was opened at 2012-05-08 06:56
Message generated for change (Tracker Item Submitted) made by tomaszmi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3524730&group_id=10127

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Test Required
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: tomaszmi (tomaszmi)
Assigned to: Nobody/Anonymous (nobody)
Summary: potential null pointer dereference

Initial Comment:
Expat version 2.1.0

There may be a potential null pointer dereference in the xmlparse.c file, line 2914. The lookup function may return NULL and this case is not checked before the line #2914. I'm not familiar with expat details, however in general if such case is not possible, it would be good to make sure the program will be terminated/aborted, for instance using assert:
assert(id);

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3524730&group_id=10127

From noreply at sourceforge.net  Tue May  8 16:51:32 2012
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 08 May 2012 07:51:32 -0700
Subject: [Expat-bugs] [ expat-Bugs-3524730 ] potential null pointer
	dereference
Message-ID: <3Vn3Yl5nR0zLss@mail.python.org>

Bugs item #3524730, was opened at 2012-05-08 06:56
Message generated for change (Comment added) made by tomaszmi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3524730&group_id=10127

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Test Required
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: tomaszmi (tomaszmi)
Assigned to: Nobody/Anonymous (nobody)
Summary: potential null pointer dereference

Initial Comment:
Expat version 2.1.0

There may be a potential null pointer dereference in the xmlparse.c file, line 2914. The lookup function may return NULL and this case is not checked before the line #2914. I'm not familiar with expat details, however in general if such case is not possible, it would be good to make sure the program will be terminated/aborted, for instance using assert:
assert(id);

----------------------------------------------------------------------

>Comment By: tomaszmi (tomaszmi)
Date: 2012-05-08 07:51

Message:
The similar issue is in the xmlparse.c, line #5478. The id->prefix may be
set to null however in the next line the pointer is dereferenced without
any check.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3524730&group_id=10127

From noreply at sourceforge.net  Mon May 14 17:58:37 2012
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 14 May 2012 08:58:37 -0700
Subject: [Expat-bugs] [ expat-Bugs-3526620 ] undocumented XML_SetHashSalt(p,
	0) semantics
Message-ID: <3VrmmN3wLLzNJN@mail.python.org>

Bugs item #3526620, was opened at 2012-05-14 08:58
Message generated for change (Tracker Item Submitted) made by jorton
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3526620&group_id=10127

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joe Orton (jorton)
Assigned to: Nobody/Anonymous (nobody)
Summary: undocumented XML_SetHashSalt(p, 0) semantics

Initial Comment:
Per e-mail discussion:

Tomas Hoger noticed that the semantics of XML_SetHashSalt are surprising
when 0 is passed.  That value does not force a fixed hash salt, as might be
expected from reading the API description, but instead implies use of a
random hash salt, per startParsing():

    if (hash_secret_salt == 0)
      hash_secret_salt = generate_hash_secret_salt();

Which is the desired semantics?  It would be simple to fix either the header
or the implementation.  pyexpat is apparently using XML_SetHashSalt(parser,
0) hoping for a fixed hash salt.

Affects Version: expat 2.1.0

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3526620&group_id=10127

From noreply at sourceforge.net  Tue May 15 02:31:36 2012
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 14 May 2012 17:31:36 -0700
Subject: [Expat-bugs] [ expat-Bugs-3526620 ] undocumented XML_SetHashSalt(p,
	0) semantics
Message-ID: <3Vs08C1thWzNH7@mail.python.org>

Bugs item #3526620, was opened at 2012-05-14 08:58
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3526620&group_id=10127

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Joe Orton (jorton)
Assigned to: Nobody/Anonymous (nobody)
Summary: undocumented XML_SetHashSalt(p, 0) semantics

Initial Comment:
Per e-mail discussion:

Tomas Hoger noticed that the semantics of XML_SetHashSalt are surprising
when 0 is passed.  That value does not force a fixed hash salt, as might be
expected from reading the API description, but instead implies use of a
random hash salt, per startParsing():

    if (hash_secret_salt == 0)
      hash_secret_salt = generate_hash_secret_salt();

Which is the desired semantics?  It would be simple to fix either the header
or the implementation.  pyexpat is apparently using XML_SetHashSalt(parser,
0) hoping for a fixed hash salt.

Affects Version: expat 2.1.0

----------------------------------------------------------------------

>Comment By: Karl Waclawek (kwaclaw)
Date: 2012-05-14 17:31

Message:
Documentation corrected in reference.html rev. 1.76.
The sentinel value for the hash salt could be changed to a different value
in a later release, if this behavior causes a real issue. However, no code
should depend on the internal workings of the hash function in Expat.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3526620&group_id=10127