ur FreeBSD system contains undesired software.
Cheers
Marek
On Wed, May 15, 2024 at 1:01 PM John Howie
mailto:j...@thehowies.com>> wrote:
I use RIP all the time. Removing it would be a pain. What is the justification?
Moving it to ports is an option, but now we have to compile, distribu
I use RIP all the time. Removing it would be a pain. What is the justification?
Moving it to ports is an option, but now we have to compile, distribute, and
install it.
Sent from my iPhone
> On May 15, 2024, at 07:40, Tomek CEDRO wrote:
>
> On Wed, May 15, 2024 at 4:20 PM Scott wrote:
>>>
Hi Yuri,
Is your machine a router or gateway, or have a firewall? Are you trying to
capture all broadcast packets, or just UDP targeted and broadcast packets
to a particular port?
Regards,
John
On 4/8/15, 5:21 PM, Yuri y...@rawbw.com wrote:
On 04/08/2015 05:32, Daniel Corbe wrote:
If nobody
problem lies. There might be something that is shortcutting the
uniqueness of the tuple and just focusing on IP addresses. I would
validate that for you but I am at 35000¹ right now...
Regards,
John
On 4/8/15, 6:42 PM, Yuri y...@rawbw.com wrote:
On 04/08/2015 15:31, John Howie wrote:
Is your
...@rawbw.com wrote:
On 04/08/2015 16:07, John Howie wrote:
Have you tried using a static IP address for the host and VM, and
disabling DHCP? The DHCP client will bind to and use 0.0.0.0 to get an
IP
address. The SO_REUSEADDR rule is that every tuple (proto, src ip, src
port, dst ip, dst prt) must
Hi Steinar,
In short, no, I have no packet traces. Given that the DHCP code in the
FreeBSD boot loader and NFS subsystem does not request those options, but
that ISC-DHCP does provide them, I will go out on a limb and say that it
must be serving them without being asked if they are configured.
Hi Steinar,
I could ask you to 'prove it', too, but I can easily check when I get back from
my current travels :-)
It important to note that even if it does (as I think it does) it is NOT in
violation of the RFC. The RFC simply says that if a client wants something it
should ask for it, and
...@uoguelph.ca wrote:
John Howie wrote:
Hi all,
I apologize for the cross posting of this email, but I believe it
will be
of interest to people across all three groups. Please feel free to
forward
to additional groups if you feel they would benefit.
I have seen a few posts on and off over
Hi all,
I apologize for the cross posting of this email, but I believe it will be
of interest to people across all three groups. Please feel free to forward
to additional groups if you feel they would benefit.
I have seen a few posts on and off over the years about Windows Server
DHCP not
The following reply was made to PR misc/186006; it has been noted by GNATS.
From: John Howie j...@thehowies.com
To: bug-follo...@freebsd.org bug-follo...@freebsd.org, John Howie
j...@thehowies.com
Cc:
Subject: Re: misc/186006: buildworld libc build error
quot;#39;MALLOC_PRODUCTION#39
Quarter:
Keywords:
Date-Required:
Class: sw-bug
Submitter-Id: current-users
Arrival-Date: Wed Jan 22 16:40:00 UTC 2014
Closed-Date:
Last-Modified:
Originator: John Howie
Release:10.0-RELEASE
Organization:
Environment:
FreeBSD freebsd.thehowies.com 9.1-RELEASE-p3
Torbjörn,
... There are just too
many holes in Windows for it to be feasible to plug them all. The focus
ought to be on preventing the code execution in the first place, not on
trying to contain it.
I think it unfair to paint Windows with such a broad brush, especially as most other
OSes
to lead the way? I
can see it now: WARNING: By using Open Source code anyone can modify
the source, replace your binaries, and completely root your system!
John Howie CISSP MCSE
President, Security Toolkit LLC
to
lock/unlock the hard drive.
Regards,
John Howie CISSP MCSE
President, Security Toolkit LLC
.
John Howie
-Original Message-
From: Riad S. Wahby [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 31, 2002 12:19 PM
To: [EMAIL PROTECTED]
Subject: Re: It takes two to tango
Chris Paget [EMAIL PROTECTED] wrote:
Does V still have the right to sue R?
Let's put this a different way
In response to Slav's posting (below):
These are not fundamental technology problems; rather they are problems
with PKI in general, and policies and procedures belonging to the
issuing CA - in this case Verisign. I am not saying that there are no
bugs in MS Certificate Services, or in Verisign's
16 matches
Mail list logo
