Finlayson, R., "Bootstrap Loading using TFTP", RFC 906, Stanford, June 1984. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Automated Recovery in a Secure Bootstrap Process - Arbaugh, Keromytis, Farber.. (1998) (10 citations) (Correct)
....recovery procedure it becomes isomorphic to a secure network boot with the purpose of retrieving valid bootstrap components rather than an operating system. We leverage this fact by adding authentication to the well known network protocols supporting Remote Program Loading (RPL) DHCP[12] and TFTP[17] and using them as our recovery protocol. As a result, our approach is similar to that proposed in the NetPC specification[8] The biggest difference, however, between our approach and the NetPC approach, in addition to that noted above, is the addition of security. Currently, the NetPC ....
R. Finlayson. Bootstrap Loading using TFTP. Internet RFC 906, June 1984.
Secure Zero Configuration - Toivanen (Correct)
....IP address arises. The question is, How the computer without permanent disk capacity can know its own IP address [1] The first protocols to configure the computer automatically were a Reverse Address Resolution Protocol (RARP) 2] to get the IP address from the corresponding server and a TFTP [3] as a way to make a Bootstrap Loading. They both are from the year 1984. An other, later version of the same song is Bootstrap Protocol (BOOTP) 4] from the year 1985. The reason for developing BOOTP was to get the protocol on the upper level than 1 HUT TML 2000 Tik 110.501 Seminar on Network ....
R. Finlayson. Bootstrap Loading using TFTP. RFC 906, http://www.ietf.org/rfc/rfc0906.txt, June 1984.
Automated Recovery in a Secure Bootstrap Process - Arbaugh, Keromytis, Farber.. (1998) (10 citations) (Correct)
....The resultant AEGIS boot process is shown in figure 2. Note that when the boot process enters the recovery procedure it becomes isomorphic to a secure network boot. We leverage this fact by adding authentication to the well known network protocols supporting the boot process DHCP[Dro97] and TFTP[Fin84] and using them as our recovery protocol. Expansion ROMs Boot Block Operating System Initiate POST BIOS Section 1 BIOS Section 2 AEGIS ROM Level 0 User Programs Network Host Recovery Transition Control Transition Legend Level 1 Level 2 Level 3 Level 4 Level 5 Figure 2: AEGIS boot control flow 3 ....
Ross Finlayson. Bootstrap Loading using TFTP. Internet RFC 906, June 1984.
Automated Recovery in a Secure Bootstrap Process - Arbaugh, Keromytis, Farber.. (1998) (10 citations) (Correct)
....procedure it becomes isomorphic to a secure network boot with the purpose of retrieving valid bootstrap components rather than an operating system. We leverage this fact by adding authentication to the well known network protocols supporting Remote Program Loading (RPL) DHCP[Dro97b] and TFTP[Fin84] and using them as our recovery protocol. As a result, our approach is simExpansion ROMs Boot Block Operating System Initiate POST BIOS Section 1 BIOS Section 2 AEGIS ROM Level 0 User Programs Network Host Recovery Transition Control Transition Legend Level 1 Level 2 Level 3 Level 4 Level 5 ....
Ross Finlayson. Bootstrap Loading using TFTP. Internet RFC 906, June 1984.
Network Working Group D. Brownell Request For Comments.. - Automatic Network.. (Correct)
No context found.
Finlayson, R., "Bootstrap Loading using TFTP", RFC 906, Stanford, June 1984.
Unknown - (Correct)
No context found.
Finlayson, R., "Bootstrap Loading Using TFTP", RFC 906, Stanford, June 1984.
Initialization (BOOTP and DHCP) - Jain (Correct)
No context found.
R. Finlayson, "Bootstrap loading using TFTP", 06/01/1984, 4 pages.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC