A free software implementation of Symantec's VIP Access application and protocol
Pull request Compare This branch is 12 commits ahead of cyrozap:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
.gitignore Added Python .gitignore Mar 14, 2015



This is a fork of @cyrozap's python-vipaccess.

Main differences:

  • No dependency on qrcode or image libraries
  • Option to generate either the desktop (VSST) or mobile (VSMT) version on the VIP Access tokens; as far as I can tell there is no real difference between them, but some clients require one or the other specifically.
  • Command-line utility is expanded to support both token provisioning (creating a new token) and emitting codes for an existing token (inspired by the command-line interface of stoken, which handles the same functions for RSA SecurID tokens


python-vipaccess is a free and open source software (FOSS) implementation of Symantec's VIP Access client.

If you need to access a network which uses VIP Access for two-factor authentication, but can't or don't want to use Symantec's proprietary applications—which are only available for Windows, MacOS, Android, iOS—then this is for you.

As @cyrozap discovered in reverse-engineering the VIP Access protocol (original blog post), Symantec VIP Access actually uses a completely open standard called Time-based One-time Password Algorithm for generating the 6-digit codes that it outputs. The only non-standard part is the provisioning protocol used to create a new token.


If you have pip installed on your system, you can install them with pip install lxml oath PyCrypto requests.


  1. Check out this repository by running git clone https://github.com/dlenski/python-vipaccess.git
  2. Switch to the python-vipaccess directory by running cd python-vipaccess
  3. Install the vipaccess module

    • With pip: pip install .
    • Without pip: python setup.py install


(This section covers the expanded CLI options of this fork, rather than @cyrozap's original version.)

Provisioning a new VIP Access credential

This is used to create a new VIP Access token: by default, it stores the new credential in the file .vipaccess in your home directory (in a format similar to stoken), but it can store to another file instead, or instead just print out the "token secret" string with instructions about how to use it.

usage: vipaccess provision [-h] [-p | -o DOTFILE] [-t TOKEN_MODEL]

optional arguments:
  -h, --help            show this help message and exit
  -p, --print           Print the new credential, but don't save it to a file
  -o DOTFILE, --dotfile DOTFILE
                        File in which to store the new credential (default
  -t TOKEN_MODEL, --token-model TOKEN_MODEL
                        VIP Access token model. Should be VSST (desktop token,
                        default) or VSMT (mobile token). Some clients only
                        accept one or the other.

Here is an example of the output from vipaccess provision -p:

Credential created successfully:
This credential expires on this date: 2019-01-15T12:00:00.000Z

You will need the ID to register this credential: VSST12345678

You can use oathtool to generate the same OTP codes
as would be produced by the official VIP Access apps:

    oathtool -d6 -b --totp    AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA  # 6-digit code
    oathtool -d6 -b --totp -v AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA  # ... with extra information

Here is the format of the .vipaccess token file output from vipaccess provision [-o ~/.vipaccess]. (This file is created with read/write permissions only for the current user.)

version 1
id VSST12345678
expiry 2019-01-15T12:00:00.000Z

Generating access codes using an existing credential

The vipaccess [show] option will also do this for you: by default it generates codes based on the credential in ~/.vipaccess, but you can specify an alternative credential file or specify the OATH "token secret" on the command line.

usage: vipaccess show [-h] [-s SECRET | -f DOTFILE]

optional arguments:
  -h, --help            show this help message and exit
  -s SECRET, --secret SECRET
                        Specify the token secret on the command line (base32
  -f DOTFILE, --dotfile DOTFILE
                        File in which the credential is stored (default

As alluded to above, you can use other standard OATH-based tools to generate the 6-digit codes identical to what Symantec's official apps produce.