Jonathan is a network administrator who is currently testing the internal security of his network. He is attempting to hijack a session, using Ettercap, of a user connected to his Web server. Why…

FTP (File Transfer Protocol) sessions are stateful and can be vulnerable to hijacking if not secured, so this statement is incorrect.

HTTPS sessions, being encrypted, are generally *more resistant* to hijacking than HTTP sessions because the encryption protects session tokens and communication from eavesdropping and tampering.

The HTTP protocol itself is stateless, meaning each request from a client to a server is treated as an independent transaction without inherent knowledge of previous requests. While web applications use mechanisms like cookies or URL rewriting to manage user sessions *on top of* HTTP, the protocol fundamentally does not maintain a persistent session that can be hijacked in the same manner as stateful protocols, making direct HTTP session hijacking problematic without targeting these higher-layer mechanisms.

DNS traffic can be manipulated or poisoned (e.g., DNS spoofing), but 'DNS session hijacking' in the context of user application sessions is not a typical attack vector; it relates more to redirecting traffic or resolving hostnames maliciously.