8 ms·
Not at all. 1FTP connects to FTP servers, that's it. There's no storing of any files on our servers, it's just a pass through to provide end-user security (no s
by sxates 15y ago
Not at all. 1FTP connects to FTP servers, that's it. There's no storing of any files on our servers, it's just a pass through to provide end-user security (no sniffing passwords over wifi) and user access.
1FTP sits between the user and the FTP server, controlling access. User > 1FTP > FTP Server. Result: More secure, easy to control access (share and unshare, like Dropbox), log all activity to know who's doing what.
The big problem is that today everyone shares a single log in to the FTP server which is often passed around via email - to coworkers, outside agencies, contractors, etc. Everyone is logging in as the same user, so you no longer know who is actually logging in. 1FTP solves this, among other things.
- ceejayoz 15y agoHow are you solving the password sharing problem?
- tedunangst 15y ago1FTP has the magic FTP password. Everyone else has an individual password to get into the website, so they don't need to know the actual FTP password. You could create ftp accounts for each user, but that's just not how things are done.
- sxates 15y agoEvery 1FTP user has a unique 1FTP account. So to share access, you would simply choose one of the connections you own, click 'share' and input an email address, and then that user would get an email letting them know they have access (if they have an account, or prompt them to create a password for their account if they don't). Think Dropbox. So all users have 1FTP IDs, and are only connecting to 1FTP, not the actual server. 1FTP connects on their behalf on the backend.
- ceejayoz 15y agoOK, but what's stopping the non-technical project manager from passing the credentials on to the team, contractors, etc.? I can set up individual accounts for a normal FTP too.
- dools 15y agoOkay so you're saying the bonus is that, using 1FTP, I can have a single sign-on ID which allows me to connect to multiple different FTP servers, so when someone wants to give me access to their FTP account they can do it via my 1FTP id rather than adding a user for me on their FTP account, and sending me yet another username and password. Like OpenID for FTP (and presumably, you could accept login via Facebook or Twitter as well ... ) I get it now, sorry I didn't understand that you were proxying through to random FTP servers rather than supplying storage (a la dropbox). One thing, though, unless you're using SFTP or SCP to connect to the destination server, wouldn't it be possible for someone to sniff network packets coming out of your servers to grab the plain text passwords for any of the myriad FTP servers you connect to? I don't really know much about the logistics of it but it seems as though your servers would become a bit of a hub for discovering insecure FTP logins to thousands of servers.