What is the purpose of TCP wrapper?

Question

Options

• AManage and adjust bandwidth used by TCP services.
• BBind a network service to a TCP port.
• CEncapsulate TCP messages in IP packets.
• DAdd SSL support to plain text TCP services.
• ELimit access to a network service.

• B
  5% (2)
• C
  8% (3)
• D
  3% (1)
• E
  85% (33)

Explanation

TCP Wrapper is a host-based access control system (originally implemented as tcpd on Unix/Linux) that intercepts incoming network connections and checks them against rules in /etc/hosts.allow and /etc/hosts.deny to permit or deny access - making E correct.

Why the distractors are wrong:

• A (bandwidth management) - TCP wrappers have no traffic-shaping or QoS capability; that's the job of tools like tc or firewall rate-limiting rules.
• B (binding services to ports) - Port binding is handled by the service itself (e.g., sshd, vsftpd) or by inetd/xinetd; TCP wrappers sit in front of services, not beneath them.
• C (encapsulating TCP in IP) - That's normal IP stack behavior at the network layer, completely unrelated to application-layer access control.
• D (adding SSL) - SSL/TLS wrapping is done by tools like stunnel or built-in TLS support in services; TCP wrappers deal with who can connect, not how the connection is encrypted.

Memory tip: Think of TCP wrappers as a bouncer at the door - they check your ID (IP address/hostname) against a guest list (hosts.allow/hosts.deny) before letting you into the club (the service). They don't manage the music (bandwidth), build the door (port binding), seal the envelope (encapsulation), or add a lock (SSL).

No community discussion yet for this question.