Squid security holes - current status?

Hi there

There's a guy in comp.security.firewalls claiming that Squid has buffer
overflows which makes it totally inappropriate to use on a firewall.

What is the current status of security in Squid? Obvious that's a bit of a
stupid question (i.e. answer:"it's secure until someone finds a hole in
it"), but I think if it's run on a firewall where only your local users can
access it (enforced by Squid ACLs AND by router/host ACLs), then it should
be pretty hard to crack. I'm intending to run it in our new firewall
environment chroot'ed and non-root and I'm "sure" it'll be fine :-)

Buffer overflows were a problem back in some 1.x release - but they were
fixed way back - could there be more?

-- 
Cheers
Jason Haar
Unix/Network Specialist, Trimble NZ
Phone: +64 3 3391 377 Fax: +64 3 3391 417