This article was nominated for deletion on 5 May 2020. The result of the discussion was redirect. |
This redirect does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||
|
Security
editThe german article has the section section 'Security'. What i found quite amusing was the note, that this approach also has it's limits. In the german version there is:
from: http://de.wikipedia.org/wiki/Peg_DHCP
"Schon bei der Veranstaltung, auf die das Verfahren zurückgeht, gewährleistete es nicht die Sicherheit des Netzes. Ein Teilnehmer hatte seinem Computer die IP-Adresse des Routers zugewiesen und blockierte dadurch den Zugang zum Internet. Ein so eingestellter Computer mit entsprechender Ausstattung kann einen Man-in-the-middle-Angriff ausführen."
I try this in english: This approach could not ensure the security / availability of the network. One attended used the IP address of the router on his host and thus blocked the route to the internet. A host configured like this could be used for a man - in - the middle attack. (sic)
In this article is: 'Peg DHCP was successfully used on Hacking in Progress'
Do we need this in this article? —Preceding unsigned comment added by 84.58.182.230 (talk) 21:02, 26 November 2008 (UTC)
- I guess this is directly from the RFC? Right at the end of (page 5) it is mentioned:
-
- Due to the human factor of the clients transferring information from peg to IP stack, the information can be misinterpreted, which could cause network troubles. In the field test at HIP this became perfectly clear when someone mixed up the numbers and used the address from the default router as his IP-number, rendering the network useless for a period of time.
- Seems like a useful thing to include in the article. -- magetoo 08:10, 24 June 2009 (UTC)