tftp and ignite

[Joe J_1]

When iginte was installed it uncommented tftp in the inetd.conf. We do not use an ignite Server over the network and our security auditors said tftp should be commented out in the inetd.conf file.
If I comment out tftp what will this do when I run the make_recovery?

Thanks

[Helen French]

Hi,

I don't think uncommenting 'tftp' in /etc/inetd.conf will make you any difference when running make_recovery.

I have this uncommented in my systems and I didn't have any problems running make_recovery.

HTH,
Shiju

[Bill McNAMARA_1]

once you don't need to network recover boot a system it'll be fine.

It's true that tftp can be a security risk.

Booting from tape will not be a problem.

Later,
Bill

[Jeff Schussele]

I agree - if no net Ignite no tftp required & will be no problem.

I would also encourage you to get & use the newer make_tape_recovery util in the newer Ignite versions. More & better options available in it.

Rgds,
Jeff

[Martin Burnett_2 · Accepted solution]

Hello,

The way that ignite uses tftp is for processes used across the network (make_net_recovery, make_sys_image, etc). The client establishes contact with the server using the bootp protocol (this is why they have to be on the same subnet or have a boot helper installed) which downloads a mini kernel for the client to boot from. The client can then access the Ignite server and from then on tftp is used to transfer the image/files to the client. This is why Ignite uncomments the inetd.conf entry.

If you are simply using the make_tape_recovery capabilties, you definitely do not need the tftp protocol in any way.

If you ever decide to use the network capabilities of Ignite it is easy enough to reenable it.

Martin

[pap]

Not a problem as long as you are making recovery tape for restoration from your machine.