I vaguely recall something about syslogd using localhost for messages, but I can't remember if that's the main reason we need to allow that traffic. Is that option D?
I think I remember that localhost traffic needs to be allowed because some applications rely on it to communicate, but I'm not entirely sure which option that is.
The iptables command communicating with netfilterd on localhost - that's an interesting detail. I'll make sure to keep that in mind as I work through this question.
All traffic to localhost should always be allowed? That doesn't sound right to me. I'll need to read the question more closely and consider the other options.
Okay, the key here is that some applications use localhost to communicate, so we need a rule to allow that traffic even with a DROP default policy. I think I've got a good strategy for this.
I think a rule allowing traffic to localhost should exist because some applications use the localhost interface to communicate with other applications.
C is the correct answer. Applications like database servers often use the localhost interface for internal communication, so a rule allowing this traffic is necessary.
Gail
4 months agoRyan
4 months agoYuki
4 months agoCherelle
4 months agoKenia
4 months agoMozell
5 months agoInocencia
5 months agoMaryann
5 months agoKaycee
5 months agoTarra
5 months agoMaurine
6 months agoAlease
6 months agoLasandra
6 months agoNikita
6 months agoRosamond
11 months agoKristal
9 months agoFabiola
9 months agoNobuko
10 months agoOretha
11 months agoRupert
9 months agoBong
9 months agoElena
10 months agoPamella
11 months agoVenita
10 months agoQuentin
10 months agoElouise
10 months agoGraciela
11 months agoEleonore
12 months agoJosue
12 months agoCarey
1 year agoErick
10 months agoLuke
10 months agoTonette
11 months agoLucina
11 months agoLawrence
11 months agoLinwood
11 months ago