> After looking at this I have few suggestions. > > 1) Allow the user to disable the newtwork includes. How? The includes are to be used to specify the config file - the only place to set them would be on the command line. And even then you'd probably not have a functional config file at all. > 2) Have do not allow network includes to override already > configured global items. It wouldn't have to override them - it would just have to add a repository that had newer packages than you do or than the other repos do. > 3) Perhaps have certain items that cannot be set (or unset) > via a network include. I think that would be a mess both programmatically and from a user perspective. > I think would go a long way towards making it more secure in a network > environment. > > Cheers...james > > P.S. The gpg signing did come to mind, but now I am in fear of saying it > (-; The problem with gpg signing the config file snippets is this: 1. you'd have to use gpg to check them 2. you'd have to have configured a place to store the gpg keyring - b/c we're checking text files, not rpms at that point. 3. where would you look to find the configuration data to know where the gpg keyring is stored? At that point it starts being highly questionable as to whether or not to have this feature at all, b/c at that point running yum as a user would be almost impossible depending on where the gpg keyring is stored. -sv
