-
```
What steps will reproduce the problem?
1. A basic configuration binding a Windows workstation
2. Honeyd started
3. Try to ping or otherwise contact the virtual IP
Expected behaviour is some inter…
-
```
What steps will reproduce the problem?
1. A basic configuration binding a Windows workstation
2. Honeyd started
3. Try to ping or otherwise contact the virtual IP
Expected behaviour is some inter…
-
```
One feature that is nice to have in Honeyd is the ability for proxied services
to look up the source and destination IP of incoming requests. This way, they
can tailor their responses based on t…
-
```
One feature that is nice to have in Honeyd is the ability for proxied services
to look up the source and destination IP of incoming requests. This way, they
can tailor their responses based on t…
-
```
On recent Linux systems, packets going through the loopback interface do
not get checksums inserted. This is reasonable behaviour as there is no
physical network to corrupt the data, but it does c…
-
```
On recent Linux systems, packets going through the loopback interface do
not get checksums inserted. This is reasonable behaviour as there is no
physical network to corrupt the data, but it does c…
-
```
On recent Linux systems, packets going through the loopback interface do
not get checksums inserted. This is reasonable behaviour as there is no
physical network to corrupt the data, but it does c…
-
```
What steps will reproduce the problem?
1. Start a virtual machine on tap1
2. Start honeyd on another interface with
"sudo honeyd -i eth0 -i tap1 test.config -d
3. Ping from inside the virtual mach…
-
```
What steps will reproduce the problem?
1. Send a large number of UDP packets of size > HONEYD_MTU which cause
fragmentation over Honeyd proxy.
2. Watch as memory corruption occurs - the pool_alloc…
-
```
What steps will reproduce the problem?
1. Send a large number of UDP packets of size > HONEYD_MTU which cause
fragmentation over Honeyd proxy.
2. Watch as memory corruption occurs - the pool_alloc…