Piet, WU-FTP is a service and not an ftp client. Therefore it would not appear in your kde menu. If you go to /usr/share/doc/packages/ftp it should have documentation for you to read about setting it up correctly. You should be for warned that FTP by default transmits passwords in clear text of the internet. This is a Bad Thing tm and should be avoided. The documentation should have instructions for a more secure setup. An LUG is a Linux Users Group. There are very few places now days that don't have one readily accessable. If you don't know where yours meets you might asking around in the computer stores, I have found that although the people who work there don't go (If they did it would improve the quality of the support they offer, but even if you invite them they don't usually come) they know who is in it and where they meet. It is a valuable resource for someone just getting into the linux world and even for those of us that have been using it regulary since 93. Austin On Sun, Mar 03, 2002 at 08:00:14PM +0100, Piet Roorda wrote:
I just installed from cd wu-ftp, but I can't find it ( I guessed it would appear somewhere in the program list of my kde desktop, but this is probably sheer ignorance frm my side) ... a LUG???
piet
Austin Morgan wrote:
This is a lot more complicated than ftp or scp, but it is a clearer method to acomplish what you are suggesting. You might look at sfs. The self-certifying file system will give you the security and share the files out as a shared directory. I have never implemented this as a mac but I am sure there is a mac client out there. Another option would be to set up an ssh tunnel to an nfs share or a vpn setup. They all have their strengths and weaknesses. As strange as it may sound the VPN setup would probably be the easiest, just do the the ammount of information available to setup an VPN network on any type of system. Another option is to setup an majordomo type configuration so as people could send in an e-mail request for the image they need and it would e-mail it to them. The only problem there is they would need to know what images are available. As to how do they find you, you would need to make your ip address known to the host. I personally use a service called www.dyndns.org. If you find them useful please donate something to them. It will make your dynamic ip (or static) accesable by name such as myhost.dyndns.org. I hope this helps, there is unfortunately no best option. If you do not feel you are capable of doing the setup yourself you might go to your LUG and ask participants there. It is amazing how mcuh information you can get from a LUG.
Good luck, Austin
On Sun, Mar 03, 2002 at 09:05:46AM +0100, Piet Roorda wrote:
James Bliss wrote:
03/02/02 02:03:03 PM, Piet Roorda <prooroa@wanadoo.nl> wrote:
I don't have any influence ont the software the people of the Mac or the Windows box are using, is scp still an option then? So I do port 21 instead of 22. Still 2 things are bugging me: How do they find me (the linux box on the internet) and what is "decent" security in the entire context? I do not think I'll be able to set and reset the firewall all the time, closing and setting up FTP, is it possible to do this by a script after the download has finished? piet Austin Morgan wrote:
One small item out of Jim's suggestion, you should open port 21 not 22 for ftp. Also you might look at using an scp client on and ssh on the host. This is far more secure than ftp, and a lot easier to set up than some secure ftp servers.
Austin
<snip> Sorry about the port 21/22 mistake, I was typing faster than I was thinking.
Just like FTP, you can get SCP clients which are either shareware or freeware from the internet.
I do not understand what you are asking about how to connect. You should just be able to do an ifconfig and determine what IP address they need to connect to. This is assuming that you have a public IP address.
SSH is supposed to be secure (Secure SHell).
Regardless, you will need to make certain that the appropriate port is open in the firewall. This is port 22 for SSH by default but can be set to any port you like with the -p option for the sshd (ssh deamon).
There is a man page for sshd.
The script to start and stop SuSEfirewall2 is named just that.
SuSEfirewall2 stop - this will stop the firewall SuSEfirewall2 start - this will restart the firewall
Make certain you have read all of the documentation and feel comfortable with it. Otherwise, you should not be doing this.
Also, why can't you just email the document to them? Regardless of your connection, email or remote access will take the same amount of time to transmit the document.
I'll explain the actual situation: at the moment the workflow is like this: I scan my images in a batch scan, say 20 images, and mail them to a photodesk or whatever. I sent them in batches of 5 so I wont jam their mailbox if something goes wrong. They probably use only 5. Then there are some they want to use in Hi-res. but as I don't know which in advance I sent the lot in Hi-res. All in all a lot of data traffic, and too much time spent behind my box.
If they (the picturedesk) would be able to fetch the pictures from my box, and could make a selection, I just do the batchscan and mail them a password and they can select/fetch the images they realy want want in a desired filesize/type
piet
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- __ __ ____ ____ | / |/ ___/ ___| Austin Morgan | |/| | | ___ \ Morgan Computer Services | | | | |___ ___) | 479-857-1189 |_| |_|____|____/ www.morgancomputers.net