I believe this worked until fairly recently, but it seems broken on
the Jan 22 and Jan 28 amd64 snapshots, I haven't tried any other
architectures yet.
# nmap -n -Pn -sS -p22,80 scanme.nmap.org
This scan should return results immediately, but mostly just hangs
there. It's intermittent -- it
On 2015/01/29 05:00, Kent Fritz wrote:
I believe this worked until fairly recently, but it seems broken on
the Jan 22 and Jan 28 amd64 snapshots, I haven't tried any other
architectures yet.
# nmap -n -Pn -sS -p22,80 scanme.nmap.org
This scan should return results immediately, but mostly
Building from top-of-tree still fails. Backing off bpf.c to 1.113
makes the problem go away.
If there's anything else I can try, just let me know.
Thanks,
Kent.
On Thu, Jan 29, 2015 at 5:30 AM, Stuart Henderson st...@openbsd.org wrote:
On 2015/01/29 05:00, Kent Fritz wrote:
I believe this
On 2014/06/15 07:58, Kent Fritz wrote:
What has this world come to when whining on the mailing list doesn't
get my problem fixed?
Nmap works MUCH better with the attached patch.
Thanks,
Kent.
Yes, it does. Full diff below, OK with you Giovanni? Kent, can you send
it to nmap-dev as well
On 06/16/14 10:21, Stuart Henderson wrote:
On 2014/06/15 07:58, Kent Fritz wrote:
What has this world come to when whining on the mailing list doesn't
get my problem fixed?
Nmap works MUCH better with the attached patch.
Thanks,
Kent.
Yes, it does. Full diff below, OK with you
On Mon, Jun 16, 2014 at 1:21 AM, Stuart Henderson st...@openbsd.org wrote:
Kent, can you send
it to nmap-dev as well please so at least it raises the profile of OpenBSD
there (even if they do seem to ignore OpenBSD-related diffs..)
See:
http://marc.info/?t=14025481551r=1w=2
Kent.
What has this world come to when whining on the mailing list doesn't
get my problem fixed?
Nmap works MUCH better with the attached patch.
Thanks,
Kent.
patch-nmap
Description: Binary data
On 06/03/14 01:06, Kent Fritz wrote:
Here's a very simple scan that shows a fundamental problem:
# nmap -Pn -sS -p22,80 scanme.nmap.org
Starting Nmap 6.46 ( http://nmap.org ) at 2014-06-02 15:41 PDT
Nmap scan report for scanme.nmap.org (74.207.244.221)
Host is up (0.035s latency).
PORT
On Tue, Jun 3, 2014, at 02:09 AM, Giovanni Bechis wrote:
On 06/03/14 01:06, Kent Fritz wrote:
Here's a very simple scan that shows a fundamental problem:
[...]
That answer is wrong, both ports are open and responded to the syn
packets. The above was run on a May 28th AMD snapshot, but I
On Tuesday, June 3, 2014 09:28 CEST, Shawn K. Quinn skqu...@rushpost.com
wrote:
On Tue, Jun 3, 2014, at 02:09 AM, Giovanni Bechis wrote:
On 06/03/14 01:06, Kent Fritz wrote:
Here's a very simple scan that shows a fundamental problem:
[...]
That answer is wrong, both ports are open
Here's a very simple scan that shows a fundamental problem:
# nmap -Pn -sS -p22,80 scanme.nmap.org
Starting Nmap 6.46 ( http://nmap.org ) at 2014-06-02 15:41 PDT
Nmap scan report for scanme.nmap.org (74.207.244.221)
Host is up (0.035s latency).
PORT STATESERVICE
22/tcp open ssh
80/tcp
I checked a few other releases, and this last worked correctly on 4.9
(Nmap 5.21), and was broken on 5.0 (Nmap 5.51).
On Mon, Jun 2, 2014 at 4:06 PM, Kent Fritz fritz.k...@gmail.com wrote:
Here's a very simple scan that shows a fundamental problem:
# nmap -Pn -sS -p22,80 scanme.nmap.org
I've noticed that I'm unable to get nmap to actually do anything on
either 5.3 or 5.4, and I'm wondering if there's some known piece of
magic I need to invoke to make it operate under OpenBSD?
Turning on
maximum verbosity and debug levels, no matter what I ask it to do, all
the initialization
13 matches
Mail list logo
