Skip to content

Instantly share code, notes, and snippets.

Created January 2, 2014 01:34
  • Star 49 You must be signed in to star a gist
  • Fork 7 You must be signed in to fork a gist
Star You must be signed in to star a gist
What would you like to do?
Command-line implementation of Symantec's "VIP Access" token application on OSX. This will read from the same secret key and produce the same time-based one-time-passwords as the GUI application, but with output that can be captured and used in scripts. This can be useful for things like automating two-factor AnyConnect VPN logins through openco…
#!/usr/bin/expect -f
# VIPAccess.exp
# Command-line emulation of Symantec's VIP Access software token.
# Usage:
# ./VIPAccess.exp [v]
# If the "v" argument (or any argument) is specified, verbose output
# will be produced on stderr. The OTP value will be output on stdout.
set timeout 10
log_user 0
set aes_key D0D0D0E0D0D0DFDFDF2C34323937D7AE
set keychain /Users/$env(USER)/Library/Keychains/VIPAccess.keychain
proc vlog { s } { if $::argc { puts stderr $s } }
vlog "Finding machine serial number (used by VIPAccess to secure the keychain.):"
spawn /bin/sh -c "ioreg -rac IOPlatformExpertDevice | xpath 'plist/array/dict/key\[.=\"IOPlatformSerialNumber\"\]/following-sibling::*\[position()=1\]/text()' 2>/dev/null"
expect eof
set serial $expect_out(buffer)
vlog " $serial"
vlog "Reading encrypted Credential ID and OTP secret key from $keychain:"
spawn security unlock-keychain $keychain
expect "password to unlock $keychain: "
send "${serial}SymantecVIPAccess$env(USER)\n"
expect eof
spawn security find-generic-password -gl CredentialStore $keychain
expect -re \"acct\"<blob>=\"\(\[a-zA-Z0-9/+\]+=\)\"
set id_crypt $expect_out(1,string)
vlog " $id_crypt"
expect -re password:\ \"\(\[a-zA-Z0-9/+\]+=\)\"
set key_crypt $expect_out(1,string)
vlog " $key_crypt"
vlog "Decrypting Credential ID and OTP key:"
spawn /bin/sh -c "openssl enc -aes-128-cbc -d -K $aes_key -iv 0 -a <<< '$id_crypt'"
expect -re \(.*\)Symantec
set id_plain $expect_out(1,string)
vlog " $id_plain"
spawn /bin/sh -c "openssl enc -aes-128-cbc -d -K $aes_key -iv 0 -a <<< '$key_crypt' | xxd -p"
expect -re \[0-9a-f\]+
set key_plain $expect_out(0,string)
vlog " $key_plain"
vlog "Generating current OTP using secret key."
spawn oathtool --totp $key_plain
expect -re \\d+
set otp $expect_out(0,string)
puts $otp
Copy link

hgocent commented Apr 22, 2020

Hello everyone, I could use this very much for the purpose of automating the VPN autentication and I can't still figure out how should I use this script.
I only have VIP access app on my phone, do I have to install the desktop version of the app in order for this to work?
Could someone explain a little how can I implement this from scratch so I can test it? sorry I am not a developer and thank you all very much.

Copy link


a version written in bash which runs a little faster

I only just now got around to looking at this. Nice. The reason I used expect is because this is actually a small piece of a larger automation task I've written which needs expect for some other steps anyway. Absent that, yes, bash is going to be faster/simpler for others to use.

Copy link

p120ph37 commented Sep 10, 2020

@hgocent, in order to automate VPN authentication, you will need a bit more than just this script. Here are the pieces, and some suggestions for how to address them:

  • Provisioning of a 2FA token: In the typical case, you will have been instructed to download the "VIP Access" app, and go through some steps to register it to your account. If you have a Mac, this will result in a "keychain" file (encrypted config file), which my script can then use to generate one-time-passwords. As an alternative to provisioning via the VIP Access app, or if you don't have a mac, you could use this Python script instead.
  • Generating the OTP: In the typical case, you are expected to open the VIP Access GUI app and transcribe the shown code manually. If you have a Mac and have already run the VIP Access app, you can use my script above (or this alternate version ) which will use the existing VIP Access app config to generate OTP codes on the command-line where you can tie it into other automation. Alternatively, if you have the plain OTP secret (either from looking at the output of my script, or because you used the Python script instead of the VIP Access app), you can use it with oathtool like this: oathtool --totp $key_plain or with a TOTP-capable password-manager like KeePassXC.
  • Connecting to the VPN: You will probably have been instructed to use something like Cisco AnyConnect for this. In any case, it will usually be some sort of GUI app that prompts for your username/password/OTP. GUI apps are often hard to automate, so you may want to try an alternative such as openconnect
  • Providing the OTP to the VPN: During the VPN login process, you will be prompted for the OTP. This is usually not something that can be passed as a command-line parameter to the VPN client app (e.g. openconnect), and is instead part of the interactive text-based login prompt that the server provides during connection. If you are using a GUI app (e.g. Cisco AnyConnect), it will probably be presented as a text-box on-screen. You will probably want to use expect scripting, or a password-manager's autotype feature to fill in the password and OTP. The details of how to set that up are going to vary depending on your exact situation.

Here is another post of mine describing how to set up VIP-Access/AnyConnect VPN from a Mac:

Copy link

aselvan commented Mar 14, 2021

The password for unlocking VIPAccess keychain i.e. "<value of IOPlatformSerialNumber>SymantecVIPAccess<$USER>" does not work for me. I just installed the VIP Access application (version 1.0.7) and I am on BigSur 11.2.2 (20D80).

Is this just me or anyone ran into this problem? or did Symantec changed the password?

Any help would be greatly appreciated.

Copy link

p120ph37 commented Mar 15, 2021

@aselvan, your issue isn't that the password is wrong, it's that since OSX 10.12, there is an additional layer of access-control on keychains, in addition to the unlock mechanism. The first time this script tries to access your VIPAccess.keychain, OSX will pop up a prompt window asking (again) for the keychain password. If you paste the password there, and hit "Always Allow", that prompt will not reappear on subsequent runs of this script. (note: the same applies to the shell variant of this script that @ykhemani created).

You can echo the password to your terminal with this command if you like (for easy copy+paste into that popup dialog):

serial=$(ioreg -rac IOPlatformExpertDevice | xpath 'plist/array/dict/key[.="IOPlatformSerialNumber"]/following-sibling::*[position()=1]/text()' 2>/dev/null)
echo ${serial}SymantecVIPAccess${USER}

You can read a little bit about this additional authorization mechanism here:

After reading the above article, you might think you can apply the "Always Allow" action directly from the terminal by doing this (but it won't work):

security set-generic-password-partition-list -S teamid:9PTGMPNXZ2,apple-tool: -k "${serial}SymantecVIPAccess${USER}" $keychain

It won't work because OSX now checks not only the partition-id but also the application-name of the accessing application, and there is currently no security subcommand to add application authorizations to an existing keychain entry. So long story short, the simplest way to do this is to just paste the password into the popup and hit "Always Allow". Or use @cyrozap's Python app instead of the Symantec app entirely:

Copy link

aselvan commented Mar 16, 2021

Update: Please ignore my response earlier on password not working. I missed reading your note about the second time prompt. I got past that step and retrieved the secret key which is really what I am after. I have written a script that I use which is a wrapper on top of oathtool for all my other 2F needs so all I needed was the SymantecVIP secret key to generate TOTP. I am good now, thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment