Closed GoogleCodeExporter closed 9 years ago
This is because you are using a modified version of a digitally-signed copy of
Tunnelblick.app, probably a "Deployed" version.
If a digitally-signed application (such as Tunnelblick) is modified, the
signature is invalidated and the application cannot modify the Keychain. The
modification could have been done manually or by the automatic restoration of
the "Deploy" folder from a backup.
Try updating to Tunnelblick 3.2.2. If your current 3.2.1 is Deployed, the
update will be to an "unsigned" version of Tunnelblick, and you will be asked
to give the updated version permission to use the Keychain.
See <a
href="http://code.google.com/p/tunnelblick/wiki/cDigitalSignatures">Tunnelblick
and Digital Signatures</a> for more details.
Original comment by jkbull...@gmail.com
on 9 Jan 2012 at 11:46
My earlier comment was WRONG -- there's a bug that makes Deployed versions of
Tunnelblick update to the SIGNED instead of UNSIGNED version.
So the only way to fix your problem is to update Tunnelblick manually. To do
that, you must download and install the "Unsigned" version of Tunnelblick. (It
will replace the signed version you have now.)
Downloads are available at
http://code.google.com/p/tunnelblick/wiki/DownloadsEntry?tm=2
Once you have an unsigned version (even 3.2.2), you will be running an unsigned
version, which will update to unsigned versions.
Original comment by jkbull...@gmail.com
on 10 Jan 2012 at 3:29
Fixes for this have been committed to the source code and will be included in
the 3.2.3 update.
Original comment by jkbull...@gmail.com
on 21 Jan 2012 at 8:00
Original issue reported on code.google.com by
marc.mie...@gmail.com
on 9 Jan 2012 at 11:02