[Esapi-user] It's SOUP!!!

Kevin W. Wall kevin.w.wall at gmail.com
Fri Feb 4 02:34:28 EST 2011


OK boys and girls, geeks and nerds, hackers, crackers, and anyone
still patient enough to read my emails...  I'll make this short...
really.

I've finished committing a bejillion things and closed out about
5 or so Google Issues.  The biggest changes were as a result of
the crypto review process done by the NSA as well as Jeff Walton.
(Jeff, would appreciate if you could take a quick look at the
new KeyDerivationFunction class. Thanks!)

Anyhow, as I've discussed with Jim, Chris, Jeff, and Arshan,
the WAF JUnit tests (and possibly some others related to
access control) are failing (well, giving 'errors' actually).
When I run all the tests, I am now getting something like 66
'errors'.  I never touched the WAF code so not sure what is
going on, other than as I mentioned in previous off-list
emails that I did blow away my $HOME/.esapi directory which
had a lot of WAF and access control files populated in it.
It was shortly after I blew that directory away that I started
noticing these failures in the JUnit tests.  But Jim and Chris
said to commit the code anyhow and they would take a look at it.
For those of you who are ambitious, you might try retrieving and
building from the SVN trunk and see if you can reproduce it. It
could just be my environment.

For now, I'm off to bed. Will check back in latter tomorrow.
Later,
-kevin
--
Kevin W. Wall
"The most likely way for the world to be destroyed, most experts agree,
is by accident. That's where we come in; we're computer professionals.
We cause accidents."        -- Nathaniel Borenstein, co-creator of MIME



More information about the Esapi-user mailing list