- Last post
- 14 Responses
I feel like we're in the stone ages at my work. How/where do you store client ftp info & passwords.
My company is against putting it anywhere online for security reasons. Currently we just have a huge Excel file.
What does your company do?
we have a custom tool for mac and pc what pulls the data from the local storage server (it was a simple nas previously), with the keys locked to the workstation you can connect and copy the details for the project.
the actual files are no excel or any 3rd party stuff just simple text.
root stuff is on usb storage (keys etc.)
we just had an evergrowing .txt file at my last job.
You'd be surprised at how many people still keep a Word doc / Excel doc of that stuff.
I personally put that kind of information into 1Password, but I'm a 1-man show so it works for me.
There are options to easily share logins through that app, but I have never had to use them.
The problem is that we have hundreds of clients and the Excel docs are getting pretty hefty. It does work, but I was hoping for something a little more elegant.
I store file in Dropbox and share across my devices.
Also android app
I've been using 1Password for years, and we recently started using the Team/Business version and it works great.
We just store them in the CRM along with the other client info and emails/attachments etc.
I use excel as well....
but you need to know the keywords and also what letters or numbers to swap out...
I keep a text doc of all my logins passwords in what looks like a learn "English for Japanese speakers worksheet" except it's all my logins written in hiragana/katakana. I then translate them back into English login/passwords.
For example, 456abc = 四五六アベセ
Looking at the document as a non Japanese reader/speaker you'd not think it contained passwords.
Haven't used FTP since my PHP days. Today, everything is done via SSH, which uses device specific keys instead of (or addition to) passwords. So, no need for usernames and passwords
Not saying switching everything to SSH is the solution, but something to consider.
Keepass, it's nice since you can have admin and client users, plus server users as read-only state and it can manage password updates.. plus supports multiple logins per site and the file itself is super secure. even if it is posted online but put in on a cloud storage like mega where all files are encrypted locally before they are uploaded and you gots yourself a pretty kick ass solution
I use an .xls file (I use KeePass personally) but I only have 4 clients at the moment so it doesn't count.