tree (like
FreeNAS, PC-BSD, etc.) will want to leave some marks as well. Should
we retain only the vendor's release tag or should we have a multiple
entries (for the original FreeBSD version and the vendor) ? Should we
even think about multiple ${vendor}-release files or just bsd-release
?
Hi,
On Sun, Aug 3, 2008 at 9:05 AM, Poul-Henning Kamp <[EMAIL PROTECTED]>wrote:
>
> The FreeBSD project has been attempted blackmailed many times over
> the year, and it havn't worked yet, and it won't ever, if I can
> prevent it.
>
Sorry to suddenly stump into this, but can we get a bit more
file (look for specially crafted URLs
> being requested).
>
> To me, exhausted memory situations are more likely looking like
> application problems (read as: bad code). With just that exhausted
> memory message given, it's guesswork to tell more but you may want to
> check PHP&#
.
Thanks,
Adrian Penisoara
ROFUG / EnterpriseBSD
On Feb 18, 2008 4:14 PM, Mark Andrews <[EMAIL PROTECTED]> wrote:
>
> > Patient: Doctor, it hurts when I do this!
> >
> > Doctor: Don't do that...
>
> Did you actually bother to read his report?
>
> Whi
puty Security Officer
Thanks for the well-written response. I think at least part of it should
make it into the FreeBSD Security Information page (
http://www.freebsd.org/security/ ) since currently there is just a simple
reference towards VuXML for ports security
Hi,
On 8/10/06, Mark Bucciarelli <[EMAIL PROTECTED]> wrote:
There's a scary security alert from yesterday out and no port
update so I judged it to be isp-related. I looked for
ports-security list but didn't see one.
You know, that might be a very good ideea -- e.g. have a security team and
tc/inetd.conf).
Either adjust your firewall to allow such notifications (UDP packets
towards port 512 on subnet 127.0.0.0/8 through lo0 interface) or disable
notification from your mail delivery agent.
Best regards,
Adrian Penisoara
Ady (@freebsd.ady.ro)
On 7/19/06, George Mamalakis <[EMAIL PROTECT
