diff options
| author | Owen Jacobson <owen.jacobson@grimoire.ca> | 2013-10-29 21:05:34 -0400 |
|---|---|---|
| committer | Owen Jacobson <owen.jacobson@grimoire.ca> | 2013-10-29 21:05:34 -0400 |
| commit | f12d129becd0a54f2094611a0956128fe4b2fc83 (patch) | |
| tree | 8753f818e2bdf7780fd451e77262d67a66e9a2d1 /wiki/ethics/linkedin-intro.md | |
| parent | 86204c92eb7f1e32f799fb14748aba159721a0d8 (diff) | |
Not a footnote.
Diffstat (limited to 'wiki/ethics/linkedin-intro.md')
| -rw-r--r-- | wiki/ethics/linkedin-intro.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/wiki/ethics/linkedin-intro.md b/wiki/ethics/linkedin-intro.md index 3944786..b3b9d0c 100644 --- a/wiki/ethics/linkedin-intro.md +++ b/wiki/ethics/linkedin-intro.md @@ -23,7 +23,7 @@ outgoing mail server to deliver mail with correct SPF or DKIM validation. This implies that LinkedIn Intro must know the user's email credentials, which it acquires from their mobile device. Since this is a "use" of a password, not merely a "validation" of an incoming password, the password must be available -_to LinkedIn_ as plain text*. There are two serious problems with this that +_to LinkedIn_ as plain text. There are two serious problems with this that are directly LinkedIn's responsibilty, and a third that's indirect but important. (Some email providers - notably Google - support non-password, revokable authentication mechanisms for exactly this sort of use. It's not |