Thanks, I agree with you on the scoping issue. That is the next thing I am working on. I do like the idea of setting constants for certain thing like $version.
I also strongly dislike coding in the login and password for an ftp account, but this program is designed to ftp to one account by default. The user can pass in an alternate ftp server and login / password with the command line options. The one problem I had (and the reason I coded in the login / pasword) is that users who are not allowed access to the ftp server can still use this to place files there. Do you have an idea on a workaround for that circumstance?
I did consider making it a package, but didn't think it was important enough. I assumed there was already something like this on cpan, I didn't check to see if there was, I just assumed. | [reply] |
As an alternative to a username/password, you could create a keypair and use something like scp instead of FTP, and only grant access to the private key file to users who are supposed to put files using this program. No password, and you're moving your access control/security problem out to the file system, rather than creating a new security problem. And if you need to replace the key because it has been compromised, you can do it without changing the code.
--
Spring: Forces, Coiled Again!
| [reply] |
Great Idea. I had not thought of that method. it would be much easier on the users as well. I will look into it.
Thanks.
| [reply] |