Why does SILICA give me a warning message about another interface when doing man-in-the-middle or passive session hijacking?
SILICA detects if there is another interface that has an IP address before proceeding to do an attack. This warning message is designed to let you know that there could possibly be a conflict due to default gateways and routes. If you are trying to replay a stolen session cookie and the associated web application has tied the cookie to the original client’s IP address the cookie replay will fail if you send the cookie from a different network. The interface silica0 associates to the same network that the target client(s) are on and therefore will be behind the same NAT when making requests – this ensures that your remote IP address will be the same as the original client therefore allowing for those cookies with that extra layer of protection to still be hijacked. This is only true when making requests from the silica0 interface. If you are experiencing any issues when replaying sessions and you have received the warning message try bringing any other interface that has an IP address d
Related Questions
- I get a warning message about not being able to register memory and possibly out of privileged memory while running on Solaris, what can I do?
- Im getting "TCP port XX is already occupied by another modem or network service" message don know what Im doing wrong. Can you explain?
- When doing a truss on the ns-httpd process, I occasionally see and EAGAIN message. What does this mean?