2015-07-13 15:03 GMT+02:00 Austin S Hemmelgarn :
> How about FIN/ACK and FIN/PSH/URG?
Silent:
root@debian64:~# hping3 192.168.0.2 -p 32 -FA
HPING 192.168.0.2 (eth0 192.168.0.2): AF set, 40 headers + 0 data bytes
^C
--- 192.168.0.2 hping statistic ---
3 packets transmitted, 0 packets received, 100
On 2015-07-12 19:13, Matteo Croce wrote:
2015-07-08 15:32 GMT+02:00 Austin S Hemmelgarn :
On 2015-07-06 15:44, Matteo Croce wrote:
Just to name a few that I know of off the top of my head:
1. IP packets with any protocol number not supported by your current kernel
(these return a special ICMP me
2015-07-08 15:32 GMT+02:00 Austin S Hemmelgarn :
> On 2015-07-06 15:44, Matteo Croce wrote:
> Just to name a few that I know of off the top of my head:
> 1. IP packets with any protocol number not supported by your current kernel
> (these return a special ICMP message).
Right, I'll handle them
>
On 2015-07-06 15:44, Matteo Croce wrote:
2015-07-06 12:49 GMT+02:00 :
On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce said:
Add option to disable any reply not related to a listening socket,
like RST/ACK for TCP and ICMP Port-Unreachable for UDP.
Also disables ICMP replies to echo request and
On Tue, 2015-07-07 at 17:27 +0200, Matteo Croce wrote:
> 2015-07-07 10:07 GMT+02:00 Hannes Frederic Sowa <
> han...@stressinduktion.org>:
> >
> >
> > On Mon, Jul 6, 2015, at 21:44, Matteo Croce wrote:
> > > 2015-07-06 12:49 GMT+02:00 :
> > > > On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce sai
2015-07-07 10:07 GMT+02:00 Hannes Frederic Sowa :
>
>
> On Mon, Jul 6, 2015, at 21:44, Matteo Croce wrote:
>> 2015-07-06 12:49 GMT+02:00 :
>> > On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce said:
>> >> Add option to disable any reply not related to a listening socket,
>> >> like RST/ACK for TCP
2015-07-07 9:01 GMT+02:00 Clemens Ladisch :
> valdis.kletni...@vt.edu wrote:
>> On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce said:
>>> Add option to disable any reply not related to a listening socket
>>
>> 2) You *do* realize that this isn't anywhere near sufficient in order
>> to actually mak
On Mon, Jul 6, 2015, at 21:44, Matteo Croce wrote:
> 2015-07-06 12:49 GMT+02:00 :
> > On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce said:
> >> Add option to disable any reply not related to a listening socket,
> >> like RST/ACK for TCP and ICMP Port-Unreachable for UDP.
> >> Also disables ICM
valdis.kletni...@vt.edu wrote:
> On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce said:
>> Add option to disable any reply not related to a listening socket
>
> 2) You *do* realize that this isn't anywhere near sufficient in order
> to actually make your machine "invisible", right? (Hint: What *ot
From: Matteo Croce
Date: Mon, 6 Jul 2015 21:44:06 +0200
> 2015-07-06 12:49 GMT+02:00 :
>> On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce said:
>>> Add option to disable any reply not related to a listening socket,
>>> like RST/ACK for TCP and ICMP Port-Unreachable for UDP.
>>> Also disables IC
2015-07-06 12:49 GMT+02:00 :
> On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce said:
>> Add option to disable any reply not related to a listening socket,
>> like RST/ACK for TCP and ICMP Port-Unreachable for UDP.
>> Also disables ICMP replies to echo request and timestamp.
>> The stealth mode ca
On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce said:
> Add option to disable any reply not related to a listening socket,
> like RST/ACK for TCP and ICMP Port-Unreachable for UDP.
> Also disables ICMP replies to echo request and timestamp.
> The stealth mode can be enabled selectively for a singl
Add option to disable any reply not related to a listening socket,
like RST/ACK for TCP and ICMP Port-Unreachable for UDP.
Also disables ICMP replies to echo request and timestamp.
The stealth mode can be enabled selectively for a single interface.
Signed-off-by: Matteo Croce
---
check the patch
13 matches
Mail list logo
