|
> > Fair enough Joe, but initially you argued that it shouldn't be done from a > > security/data separation point of view (which I believe is a flawed > > argument) then you made it an economic argument, which has a great deal > > more validity, even though it is not a "technical argument" and somewhat > > dependent on how you see things. > > Actually, my initial argument was against anonymous FTP (or FTP with > hardcoded user ID and password, which is the same thing from a security risk > standpoint) to an inadequately secured AS/400. Not exactly - Anonymous FTP allows access to a single Server (FTPSERVER) without the use of a password. Well written Qnonymous FTP examples (and there are pleny of freebee's on the web) will also restrict function ("Put" only or "Get" only) as well as the directory that the user can operate in. Hardcoded UserID and passowrd's can (as you've already discovered) be disclosed and run the risk of being used elsewhere. Because Anonymous FTP does not use a password, access can only be gained through an FTP server with an Exit Program attached. jte
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.