151 reputation
8
bio website iandunn.name
location Seattle, WA
age 31
visits member for 2 years, 1 month
seen Mar 25 at 18:47

Mar
17
awarded  Popular Question
May
20
answered Mac OS X - macports - Warning: No index(es) found! Have you synced your source indexes?
Mar
21
awarded  Critic
Mar
1
revised How can clients easily and securely send me passwords?
changes the example passphrases in step 3
Jan
12
comment Chrome prompts for sign in on startup
This looks like a dup of superuser.com/q/432822/121091
Jan
12
comment Disabling “Sign In ” tab on startup
Make sure Chrome is closed before you edit the file. Otherwise your changes will be overwritten when Chrome closes.
Oct
3
comment Remove Aptana Rubles folder
It works for me with both aptana.ruble.user.location and studio.rubleUserLocation. I've read that using quotes breaks it, so try removing them.
Sep
3
revised How can clients easily and securely send me passwords?
removed crypto.cat option in step 1 because sending you the session name over email would be almost as insecure as sending the password itself
Sep
1
answered How do I get Java support on Google Chrome in Linux?
Aug
3
comment How can clients easily and securely send me passwords?
Yeah, if you're already on the phone with them, then that's much better than if you e-mail/text the room name to them. I personally prefer the process I laid out in my answer, but I think your approach is a good one too.
Aug
3
revised How can clients easily and securely send me passwords?
minor grammar fixes
Aug
3
revised How can clients easily and securely send me passwords?
added passphrase advantage note
Aug
3
awarded  Commentator
Aug
3
comment How can clients easily and securely send me passwords?
I think a phone call is a less-bad way to transmit the information. The caller ID can be spoofed, but it's much harder to mimic somebody's voice, mannerisms, etc.
Aug
3
comment How can clients easily and securely send me passwords?
One of the downsides to using crypto.cat for this purpose is that you still have to share the chat room name, which essentially becomes a password in-and-of itself. If an attacker intercepted the room name, they could impersonate the client and get the system password. So now you need a way to securely share the crypto.cat password, and you're back at square one. It isn't fundamentally more secure, it just adds an extra weak layer. 2 weak layers are still better than 1, though, and if you want to keep the process simple then maybe that's an acceptable risk.
Aug
3
comment How can clients easily and securely send me passwords?
Password Pusher is a similar service.
Aug
3
awarded  Teacher
Aug
2
revised How can clients easily and securely send me passwords?
added suggestion to use crypto.cat in addition to phone
Aug
2
comment How can clients easily and securely send me passwords?
That doesn't make sense to me. This isn't a forum thread; the whole point of Stack Exchanges sites is to build a repository of knowledge. I would think the age of the question is irrelevant. There are even badges for working on old questions, like Necromancer and Archaeologist. But, if anyone sees any flaws in my answer, please point them out so I can improve it.
Aug
2
revised How can clients easily and securely send me passwords?
fixed punctuation