> > I think we need a CVE # for this, and we might want to release 2.2.2 - > what do others think? > Use CVE-2007-4999 for this flaw. Thanks. -- JB