ike-scan

Descubra e identifique anfitriões IKE (Servidores VPN IPsec)

Índice

Construção e Instalação
Visão Geral
Uso
Detalhes de Implementação
Saída do Programa
Exemplos
Plataformas Suportadas
Leitura Adicional e RFCs
Informações de Contato

Construção e Instalação

O ike-scan utiliza as ferramentas padrão GNU autoconf e automake, portanto a instalação é o processo normal:

Execute git clone https://github.com/royhills/ike-scan.git para obter o código fonte do projeto
Execute cd ike-scan para entrar no diretório fonte
Execute autoreconf --install para gerar um arquivo ./configure viável
Execute ./configure ou ./configure --with-openssl para usar as bibliotecas OpenSSL
Execute make para compilar o projeto
Execute make check para verificar se tudo funciona como esperado
Execute make install para instalar (você precisará de root ou sudo para esta parte)

Se você planeja realizar quebra de chave pré-compartilhada, então deve configurar o ike-scan para usar as funções de hash do OpenSSL em vez das funções internas, pois as do OpenSSL são normalmente mais rápidas. Para fazer isso, certifique-se de ter os arquivos de inclusão e bibliotecas do OpenSSL instalados e execute o configure como ./configure --with-openssl. Usar ou não o OpenSSL não afetará a funcionalidade do ike-scan, apenas a velocidade da quebra de chave pré-compartilhada com o psk-crack.

Alguns sistemas operacionais instalam os cabeçalhos e bibliotecas do OpenSSL por padrão; outros exigem que você instale um pacote opcional, por exemplo no Debian Linux você precisa instalar o pacote libssl-dev. Alternativamente, você pode baixar e instalar o tarball do OpenSSL em http://www.openssl.org/

Deve compilar na maioria dos sistemas operacionais modernos do tipo Unix. Funciona no Windows com Cygwin e pode ser usado como um executável Windows autônomo quando o cygwin1.dll estiver presente.

Se você estiver usando o pacote binário Windows-32, leia também o arquivo README-WIN32 que detalha as diferenças ao executar na plataforma Windows.

Sabe-se que o programa compila e funciona em Linux, FreeBSD, OpenBSD, NetBSD, Win32/Cygwin, Solaris, MacOS X, HP Tru64, HP-UX e SCO OpenServer. Para mais detalhes, veja a seção "PLATAFORMAS SUPORTADAS" abaixo.

Visão Geral

O ike-scan descobre anfitriões IKE e também pode identificá-los usando o padrão de backoff de retransmissão.

O ike-scan pode realizar as seguintes funções:

Descoberta Determinar quais anfitriões em um determinado intervalo de IP estão executando IKE. Isso é feito exibindo os anfitriões que respondem às solicitações IKE enviadas pelo ike-scan.
Fingerprinting Determinar qual implementação IKE os anfitriões estão usando e, em alguns casos, determinar a versão do software que estão executando. Isso é feito de duas maneiras: primeiro por fingerprinting de backoff UDP, que envolve registrar os tempos dos pacotes de resposta IKE dos anfitriões alvo e comparar o padrão de backoff de retransmissão observado com padrões conhecidos; e segundo por fingerprinting de ID do Fornecedor, que compara os payloads de ID do Fornecedor dos servidores VPN com padrões conhecidos de ID do fornecedor.
Enumeração de Transform Descobrir quais atributos de transform são suportados pelo servidor VPN para a Fase 1 do IKE (por exemplo, algoritmo de criptografia, algoritmo de hash etc.).
Enumeração de Usuários Para alguns sistemas VPN, descobrir nomes de usuário VPN válidos.
Quebra de Chave Pré-Compartilhada Realizar quebra de senha por dicionário offline ou força bruta para o Modo Agressivo IKE com autenticação por Chave Pré-Compartilhada. Isso usa o ike-scan para obter o hash e outros parâmetros, e o psk-crack (que faz parte do pacote ike-scan) para realizar a quebra.

O conceito de fingerprinting de backoff de retransmissão é discutido em mais detalhes no artigo sobre fingerprinting de backoff UDP, que deve estar incluído no kit ike-scan como Artigo sobre Fingerprinting de Backoff UDP.

O programa envia solicitações de fase 1 IKE (Modo Principal ou Modo Agressivo) para os anfitriões especificados e exibe quaisquer respostas que sejam recebidas. Ele lida com repetição e retransmissão com backoff para lidar com perda de pacotes. Também limita a quantidade de largura de banda usada pelos pacotes IKE de saída.

IKE é o protocolo Internet Key Exchange, que é o mecanismo de troca de chaves e autenticação usado pelo IPsec. Quase todos os sistemas VPN modernos implementam IPsec, e a grande maioria das VPNs IPsec usa IKE para troca de chaves. O Modo Principal é um dos modos definidos para a fase 1 da troca IKE (o outro modo definido é o modo agressivo). A RFC 2409 seção 5 especifica que o modo principal deve ser implementado, portanto, todas as implementações IKE podem ser esperadas para suportar o modo principal. Muitas também suportam o Modo Agressivo.

Uso

Para ver as informações de uso atuais, execute o binário ike-scan da seguinte forma:ike-scan -h

Additional documentation is provided on the NTA Monitor Wiki

To report bugs or suggest new features, please create a GitHub issue.

Implementation Details

Host Input and Memory Requirements

The hosts to scan can be specified on the command line or read from an input file using the --file=<fn> option. The program can cope with large numbers of hosts limited only by the amount of memory needed to store the list of host_entry structures. Each host_entry structure requires 45 bytes on a 32-bit system, so a class B network (65534 hosts) would require about 2.8 MB for the list. The hosts can be specified as either IP addresses or hostnames, however the program will store all hosts internally as IP addresses and will only display IP addresses in the output (ike-scan calls gethostbyname(3) to determine the IP address of each host, but this can be disabled with the --nodns option).

Rate Limiting

The program limits the rate at which it sends IKE packets to ensure that it does not overload the network connection. By default it uses an outbound data rate of 56000 bits per second. This can be changed with the --bandwidth option.

If you want to send packets at a specific rate, you can use the --interval option.

ike-scan generates unique IKE cookies for each host, and it uses these cookies to determine which host the response packets belong to. Note that it does not rely on the source IP address of the response packets because it is possible for a response packet to be sent from a different IP address than it was originally sent to. See the PROGRAM OUTPUT section for an example of this.

The cookies are generated by taking the first 64 bits of an MD5 hash of the current time in seconds and microseconds as returned by gettimeofday(), the unique host number, and the host IP address. This ensures that the cookies are unique with a reasonable degree of certainty.

If --verbose is in effect, any packets that are received with cookies that do not match will result in a message like:

Ignoring 84 bytes from 172.16.2.2 with unknown cookie 195c837e5a39f657 Se --verbose não estiver em vigor, esses pacotes são silenciosamente ignorados.

Esse tipo de incompatibilidade de cookie pode ser causado por:

O host ainda está retornando respostas IKE a uma execução anterior do ike-scan;
O pacote não é um pacote IKE ou foi corrompido de alguma forma; ou
Um pacote IKE que não tem nada a ver com o ike-scan foi recebido.

Detalhes do Pacote IKE

Os pacotes do modo principal enviados contêm um cabeçalho ISAKMP e um payload SA. O payload SA contém uma única proposta, e a proposta pode conter um número variável de transformações, conforme detalhado abaixo.

Por padrão, a proposta SA contém 8 transformações. Essas 8 transformações representam todas as combinações possíveis de:

Algoritmo de Criptografia: DES-CBC e 3DES-CBC;
Algoritmo de Hash: MD5 e SHA-1; e
Grupo DH: 1 (MODP 768) e 2 (MODP 1024).

Um exemplo de saída tcpdump do pacote do modo principal enviado pelo ike-scan usando o conjunto de transformações padrão é mostrado abaixo. Isso mostra as 8 transformações e também a ordem em que são enviadas:

16:57:16.024536 192.168.124.8.500 > 172.16.2.2.500:  [udp sum ok]isakmp 1.0 msgid 00000000: phase 1 I ident:
  (sa: doi=ipsec situation=identity
    (p: #1 protoid=isakmp transform=8
      (t: #1 id=ike (type=enc value=3des)(type=hash value=sha1)(type=auth value=preshared)(type=group desc value=modp1024)(type=lifetype value=sec)(type=lifeduration len=4 value=00007080))
      (t: #2 id=ike (type=enc value=3des)(type=hash value=md5)(type=auth value=preshared)(type=group desc value=modp1024)(type=lifetype value=sec)(type=lifeduration len=4 value=00007080))
      (t: #3 id=ike (type=enc value=1des)(type=hash value=sha1)(type=auth value=preshared)(type=group desc value=modp1024)(type=lifetype value=sec)(type=lifeduration len=4 value=00007080))
      (t: #4 id=ike (type=enc value=1des)(type=hash value=md5)(type=auth value=preshared)(type=group desc value=modp1024)(type=lifetype value=sec)(type=lifeduration len=4 value=00007080))
      (t: #5 id=ike (type=enc value=3des)(type=hash value=sha1)(type=auth value=preshared)(type=group desc value=modp768)(type=lifetype value=sec)(type=lifeduration len=4 value=00007080))
      (t: #6 id=ike (type=enc value=3des)(type=hash value=md5)(type=auth value=preshared)(type=group desc value=modp768)(type=lifetype value=sec)(type=lifeduration len=4 value=00007080))
      (t: #7 id=ike (type=enc value=1des)(type=hash value=sha1)(type=auth value=preshared)(type=group desc value=modp768)(type=lifetype value=sec)(type=lifeduration len=4 value=00007080))
      (t: #8 id=ike (type=enc value=1des)(type=hash value=md5)(type=auth value=preshared)(type=group desc value=modp768)(type=lifetype value=sec)(type=lifeduration len=4 value=00007080)))) (DF) (ttl 64, id 0, len 364)```

Este conjunto de transformações padrão foi projetado para ser aceitável para a maioria das implementações IKE - a maioria aceitará pelo menos uma das transformações oferecidas. No entanto, às vezes é necessário usar um método de autenticação diferente (chave pré-compartilhada é o mais comum, mas nem sempre é suportado), e ocasionalmente é necessário especificar uma cifra diferente, como AES de 256 bits. Mais raramente, pode ser necessário alterar o tempo de vida. Finalmente, algumas implementações exigem que uma string específica de "Vendor ID" seja enviada pelo cliente antes de responderem. Isso pode ser especificado com a opção --vendor.

O conjunto de transformações padrão resulta em um comprimento de dados de pacote de 336 bytes que, quando os cabeçalhos IP e UDP são adicionados, dá um tamanho total de pacote de 364 bytes.

É possível especificar o Método de Autenticação com --auth (o padrão é 1 - chave pré-compartilhada) e o tempo de vida IKE em segundos com --lifetime (o padrão é 28800 segundos ou 8 horas, conforme recomendado pela RFC 2407). Se você especificar --lifetime como 0, nenhum atributo de tempo de vida será incluído nos payloads de transformação. Se você estiver especificando transformações personalizadas, pode usar esta opção mais de uma vez para produzir payloads de transformação com diferentes tempos de vida. Cada opção --trans usará o valor de tempo de vida especificado anteriormente.

É possível especificar um conjunto de transformações personalizado com --trans=e[/l],h,a,g onde "e" é o Algoritmo de Criptografia, "l" é o comprimento da chave para cifras de comprimento variável, "h" é o Algoritmo de Hash, "a" é o Método de Autenticação e "g" é o Grupo DH. Estes são especificados como valores numéricos; consulte o Apêndice A da RFC 2409 para obter detalhes sobre quais valores usar.

Por exemplo: --trans=5,2,1,2 especifica:Enc=5 (3DES-CBC), Hash=2 (SHA1), Auth=1 (shared key), DH Group=2 (modp 1024)

and --trans=7/256,1,1,5 specifies: Enc=7 (AES), Keylen=256 bits, Hash=MD5, Auth=shared key, DH Group=5 (modp 1536) Você pode usar a opção --trans mais de uma vez para enviar um número arbitrário de transformações personalizadas na proposta.

Especificar um conjunto de transformações personalizadas substitui qualquer método de autenticação especificado com --auth. No entanto, ele ainda usa o valor de lifetime especificado na última opção --lifetime.

Um exemplo de um conjunto complexo de transformações personalizadas é:--trans=5,2,1,2 --lifetime=0 --trans=7/256,1,3,5 --lifetime=600 --trans=7/128,1,3,5

This would specify the following three transforms:

3DES Encryption with SHA1 hash, shared key authentication, DH group 2, and the default lifetime;
256-bit AES Encryption with MD5 hash, RSA authentication, DH group 5, and no lifetime; and
128-bit AES Encryption with MD5 hash, RSA authentication, DH group 5, and lifetime of 600 second.

If a custom transform set is specified, the packet length will differ from the default. Fewer than 8 transforms will make it smaller, and more than 8 transforms will make it larger. If the packet size exceeds the MTU, then it will be fragmented. You may need to increase the --interval setting for large packets to avoid overloading your network connection. Some VPN servers may ignore very long packets.

A custom transform can be useful in the following situations:

If none of the transforms in the default transform set is acceptable to the remote IKE implementation;
If you know that a particular transform will be acceptable, and you want to minimise bandwidth use or allow faster scanning rates; or
If you want to determine exactly which transforms a remote IKE implementation supports for fingerprinting.

The default mode used is Main Mode. However, it is possible to specify Aggressive Mode with the --aggressive option. When this is done, three additional payloads will be included: Key Exchange, Nonce and ID. This will increase the packet size, and you may need to increase --interval to ensure that ike-scan doesn't try to use too much bandwidth as a result. If you use Aggressive Mode, you can also use the following options:

--id Set identification value.
--idtype Set identification type (Default 3 (ID_USER_FQDN)).
--dhgroup Specify Diffie-Hellman group (Default 2 - MODP 1024).

If you use Aggressive Mode, then you can only use one Diffie Hellman group in the transform set. If you specify custom transforms with the --trans option, you should ensure that they all use the same group, and that this group matches the DH group specified with the --dhgroup option, or the default of 2 if --dhgroup is not specified.

IKE hosts may respond in one of two ways:

With an IKE main or aggressive mode response packet containing the cookie that was originally sent to the host. This is a "handshake" response and indicates that the host supports IKE and finds our proposal acceptable; or
With an IKE notify message containing the cookie that was originally sent to the host. This is a "notify" response and indicates that the host is running IKE, but does not accept our proposal.

An example tcpdump output for a "handshake" response is:

16:57:48.068698 172.16.2.2.500 > 192.168.124.8.500:  [udp sum ok]isakmp 1.0 msgid 00000000: phase 1 R ident:
  (sa: doi=ipsec situation=identity
    (p: #1 protoid=isakmp transform=1
      (t: #1 id=ike (type=enc value=3des)(type=hash value=sha1)(type=auth value=preshared)(type=group desc value=modp1024)(type=lifetype value=sec)(type=lifeduration len=4 value=00007080)))) (ttl 126, id 37891, len 112)

This shows that the IKE host has responded with an ISAKMP header and an SA payload containing a single proposal. This proposal contains a single transform representing the transform chosen from the proposal sent by ike-scan.

An example tcpdump output for a "notify" response is:

17:12:55.038554 192.168.89.22.500 > 192.168.37.1.500:  [udp sum ok]isakmp 1.0 msgid 00000000: phase 1 R inf:
  (n: doi=0 proto=1 type=NO-PROPOSAL-CHOSEN) (ttl 52, id 39577, len 68)

This shows that the IKE host has responded with an ISAKMP header and a notify payload. The notify payload is an informational message with the type "NO-PROPOSAL-CHOSEN".

ike-scan does not respond to any of the IKE responses it receives, so the IKE main mode handshake will never complete. Some IKE implementations do not log handshakes that don't complete; these implementations will not log the scanning and therefore the owners of these systems will not be aware of the scanning. It is possible to use ike-scan to determine if a given implementation will log these scanning attempts if you have access to the system logs.

Backoff Fingerprinting

For those hosts that respond, ike-scan records the times of the received IKE responses. The backoff between IKE responses varies between different IKE implementations and can therefore be used as a fingerprint. The --showbackoff option is used to display the backoff times for each host which responded. Note that using the --showbackoff option will cause ike-scan to wait for 60 seconds after the last received packet to ensure that it has seen all of the responses. This 60 second wait can be altered by specifying a different value in seconds to the --showbackoff option.

When all of the packets have been received, the backoff table is displayed, and the program attempts to match the backoff pattern against the known backoff patterns contained in the text file ike-backoff-patterns. It is possible to add new patterns to this file.

Note that only hosts which respond with a handshake can be fingerprinted by backoff timings; hosts which respond with a notify message cannot. This is because notify messages are only ever sent once and are not subject to retransmission with backoff.

If you discover IKE hosts with backoff patterns which are not recognised by ike-scan, then you are encouraged to submit the pattern and details of the IKE implementation to me so I can incorporate it into future versions of ike-scan. You can do this by opening an issue, or a pull request on github.

Note that any packet loss will prevent the backoff fingerprinting from working because the program needs to see all of the responses.

ike-scan can also be used to fingerprint IKE hosts in other ways. For example:

Some systems (such as Checkpoint Firewall-1) allow the use of any source port (e.g. --sport=0) whereas others (e.g. Windows 2000) only respond to IKE requests from source port 500 (actually, Windows 2000 responds to requests from any port, but always sends the responses back to port 500 which amounts to the same thing).
Some systems use proprietary notify message codes which allows them to be identified. For example, Checkpoint Firewall-1 4.0, 4.1 and NG Base use notify message code 9101. ike-scan recognises this and will identify the system as "Checkpoint Firewall-1 4.x or NG Base".
Different systems support different transforms, and this support can be determined by trying all possible combinations with --trans. Note however, that the user can usually change the transform set, so this cannot be relied upon by itself.
Different implementations require different IKE Lifetimes. Some implementations will accept any lifetime, whereas others will only accept lifetimes below a certain value.
By using another tool (e.g. tcpdump) to sniff the returned IKE packets, the IP ID and IP TTL can be determined. These can be useful in fingerprinting the IP stack which can help to determine the IKE implementation.
The IKE host may send Vendor ID payloads which uniquely identify the implementation. This Vendor ID fingerprinting method was first proposed by Brett Eldridge [email protected]. ike-scan will display any vendor ID payloads that it receives, and will attempt to match these against known Vendor ID patterns.

Program Output

The program output consists of two sections:

The IKE host detection section; and
The IKE backoff pattern section (if --showbackoff is specified).

The IKE host detection section contains one line for each host that responds. The response can either be a successful handshake or an informational message. Only the first packet returned by any given host is displayed in this section.

Some examples of the IKE host detection section are:

10.0.1.98        IKE Handshake returned (1 transforms)
10.0.1.22        Notify message 14 (NO-PROPOSAL-CHOSEN)
10.0.1.189        (10.0.1.130) Notify message 9101 (No common authentication method with Firewall.)

In the above example output, host 10.0.1.98 has returned an IKE handshake, 10.0.1.22 has returned notify message 14 (decimal) which corresponds to the RFC-defined error message "NO-PROPOSAL-CHOSEN" (see RFC 2408 section 3.14.1), and 10.0.1.189 has returned a non-standard notify message 9101 but the response has come from the IP address 10.0.1.130 rather than the address which the request was sent to (presumably this is a multi-homed system). Notify message 9101 is not defined by RFC 2408, but it is known to be a Checkpoint proprietary notify code (therefore the system is probably Firewall-1) and the program displays the text included in the notify message.

Some examples of the IKE backoff pattern section are:

IP Address      No.     Recv time               Delta Time
172.16.2.2      1       1042549209.247980       0.000000
172.16.2.2      2       1042549211.239254       1.991274
172.16.2.2      3       1042549213.241935       2.002681
172.16.2.2      4       1042549215.244731       2.002796
172.16.2.2      5       1042549217.247512       2.002781
172.16.2.2      6       1042549219.250254       2.002742
172.16.2.2      7       1042549221.253044       2.002790
172.16.2.2      8       1042549225.258551       4.005507
172.16.2.2      9       1042549229.264074       4.005523
172.16.2.2      10      1042549233.269605       4.005531
172.16.2.2      11      1042549237.275145       4.005540
172.16.2.2      12      1042549241.280654       4.005509
172.16.2.2      Implementation guess: Firewall-1 4.1/NG

IP Address      No.     Recv time               Delta Time
10.0.1.98        1       1042549209.426540       0.000000
10.0.1.98        2       1042549224.425435       14.998895
10.0.1.98        3       1042549239.422251       14.996816
10.0.1.98        Implementation guess: Cisco IOS / PIX

Here, host 172.16.2.2 returned a total of 12 packets and the pattern matched "Firewall-1 4.1/NG", and host 10.0.1.98 returned 3 packets matching the pattern for "Cisco IOS / PIX". The recv time column shows the absolute time when the packet was received in seconds and microseconds since the epoch; delta time shows the elapsed time between packets in seconds and microseconds.

Examples

The below example will run IKE detection against the single host 172.16.2.2. No backoff fingerprinting will be done, and all options (timeouts, retrys, transform set Etc) will be the default.

ike-scan 172.16.2.2

This will read the target hosts from the file "hostlist.txt".

ike-scan --file=hostlist.txt

This reads the hosts from stdin and performs both IKE detection and backoff fingerprinting. The backoff wait is specified as 20 seconds.

cat hostlist.txt | ike-scan --file=- --showbackoff=20

This will run ike-scan against all hosts in the network specified by 172.16.0.0/16 (including network and broadcast addresses). In this case, this will result in a total of 65536 hosts being scanned - from 172.16.0.0 to 172.16.255.255 inclusive.

ike-scan 172.16.0.0/16

This uses the range notation to scan a total of 65536 hosts from 172.16.0.0 to 172.16.255.255 inclusive.

ike-scan 172.16.0.0-172.16.255.255

Supported Platforms

ike-scan has been built and tested on the following platforms:

Debian Linux 1.3.1 on IA32 with gcc 2.7.2.1, libc5 and 2.0.29 Kernel
Debian Linux 2.2r7 (Potato) on IA32 with gcc 2.95.2 and 2.2.17 Kernel
Debian Linux 3.0r1 (Woody) on IA32 with gcc 2.95.4 and 2.4.18 Kernel
Debian Linux 3.1 (Sarge) on IA32 with gcc 3.3.4 and 2.4.27 Kernel
Debian Linux 3.0 (Woody) on PA-RISC with gcc 3.0.4 and 2.4.17-64 Kernel
Debian Linux 3.0 (Woody) on Alpha with gcc 3.3.1 and 2.4.18-smp Kernel
Redhat Advanced Server 3.2 on IA64 with gcc 3.2.3 and 2.4.21-19.EL Kernel
HP-UX 11.11 on PA-RISC with gcc 3.4.1
HP-UX 11.11 on PA-RISC with HP cc HP92453-01 B.11.11.32003.GP
FreeBSD 4.3 on IA32 with gcc 2.95.3
OpenBSD 3.1 on IA32 with gcc 2.95.3
NetBSD 1.6 on IA32 with gcc 2.95.3
SCO OpenServer 5.0.7 on IA32 with gcc 2.95.3
Windows NT 4.0 / Cygwin 1.5.12 on IA32 with gcc 3.3.3
Solaris 2.8 on SPARC with gcc 2.95.3
HP Tru64 Unix v5.1 on Alpha with Tru64 cc
MacOS X (Darwin 7.7.0) on PowerPC

I've also had reports that it builds OK on the following systems:

RedHat Linux 7.1 with 2.4 Kernel
RedHat Linux 8.0 with 2.4 Kernel
Debian Linux 3.1 on Alpha
Debian Linux 3.1 on ARM
Debian Linux 3.1 on HP PA-RISC
Debian Linux 3.1 on Intel IA64
Debian Linux 3.1 on Motorola 68000
Debian Linux 3.1 on MIPS
Debian Linux 3.1 on PowerPC
Debian Linux 3.1 on IBM S390
Debian Linux 3.1 on SPARC

It should work, or be capable of working, on any Unix-like system which has a 64-bit integer type, supports sockets and has the system calls malloc, gethostbyname, gettimeofday, inet_ntoa, memset, select, socket, and strerror.

If you port ike-scan to a system not listed above, please let me know the details of the changes required so I can add them to future releases.

Contact Information

The best way to contact me is via the ike-scan repository on github.

I would like to hear from you if you have any of the following:

A modern Unix-like OS which ike-scan won't build on;
An OS not listed in the list above which ike-scan builds and runs OK on;
Any IKE implementation patterns that are not already in the ike-backoff-patterns file.
- Please include details of the pattern and also details of the IKE implementation;
Any Vendor ID pattern that is not already in the ike-vendor-ids file; or
Any comments or suggestions about the program.

If you need to contact me offline, please email me at [email protected]

ike-scan

Mais Populares

ike-scan

Índice

Construção e Instalação

Visão Geral

Uso

Implementation Details

Host Input and Memory Requirements

Rate Limiting

Cookie Generation and Remote Host Identification

Detalhes do Pacote IKE

Backoff Fingerprinting

Program Output

Examples

Supported Platforms

Further Reading and RFCs

Contact Information