- A hozzászóláshoz be kell jelentkezni
- 2936 megtekintés
Hozzászólások
Nagyrészt csak médiahype. Nem kell túlzottan komolyan venni.
- A hozzászóláshoz be kell jelentkezni
ez biztos? :)
- A hozzászóláshoz be kell jelentkezni
Igy probalsz menekulni attol, hogy csinalni kelljen valamit?;))
- A hozzászóláshoz be kell jelentkezni
Idézek:
It's important to realize that you're only vulnerable to this issue if you're *not* doing integrity checking via IPSEC. Most major VPN infrastructures I run across use ESP with both confidentiality *and* integrity functionality enabled (some use AH as well). If that's the case for network x, then network x has nothing to fear from this.
Always read vulnerability details; people love to sensationalize stuff like this to the extreme.
és
Any of the following methods can be used to rectify this issue: 1. Configure ESP to use both confidentiality and integrity protection. This is the recommended solution. 2. Use the AH protocol alongside ESP to provide integrity protection. However, this must be done carefully: for example, the configuration where AH in transport mode is applied end-to-end and tunnelled inside ESP is still vulnerable. 3. Remove the error reporting by restricting the generation of ICMP messages or by filtering these messages at a firewall or security gateway.
- A hozzászóláshoz be kell jelentkezni