Disclaimer: I admit to hating outlook upfront, I think it is the most braindead mailclient I have ever seen...
Today I decided to spend my friday afternoon fixing half hour with derk a co-worker.
He can't get our vpn connect to work on his laptop despite the fact that everyone else in the company can.
I also (wrongly) accused him of having a goldfish styled memory, because it appeared that he couldn't remember the passphrase for his vpn-certificate.
It turned out that I was soooooo very wrong on that last part.
There is nothing wrong with derk's memory, there is something wrong with his choice of mailclient.
He's using the latest version of microsoft office for Mac.
We send pkcs12 certificate bundles to employees by email to use for vpn connections.
These pkcs12 bundles are protected by a passphrase they get to pick themselves.
Weirdly enough, his vpn client (tunnelblick) kept reporting that it could not decode his private key with the passphrase he supplied, hence the goldfish accusation.
It turns out after approx. 30 minutes of debugging that Outlook mail client for Mac alters attachments as it sees fit. After downloading the pkcs12 from the webinterface of the exchange server instead of saving the attachment in the mailclient......... everything magically started to work flawlessly.
I'd ditch that email client.........
Subscribe to:
Post Comments (Atom)
1 comment:
I was also facing same issue i.e. get our vpn connect to work on my laptop despite the fact that everyone else in the company can.But As you mentioned the problem was the choice of mailclient.I was using the latest version of microsoft office for Mac.For now I reverted back to older version
Post a Comment