Downloads:

640

Downloads of v 2.28.0.2:

640

Last Update:

19 Jul 2015

Package Maintainer(s):

Software Author(s):

  • Theo Beisch

Tags:

keepass plugin security

KeePass Plugin iTanMaster

2.28.0.2 | Updated: 19 Jul 2015

Downloads:

640

Downloads of v 2.28.0.2:

640

Maintainer(s):

Software Author(s):

  • Theo Beisch

KeePass Plugin iTanMaster 2.28.0.2

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Passing Test


Validation Testing Unknown


Verification Testing Passed

Details

To install KeePass Plugin iTanMaster, run the following command from the command line or from PowerShell:

>

To upgrade KeePass Plugin iTanMaster, run the following command from the command line or from PowerShell:

>

To uninstall KeePass Plugin iTanMaster, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade keepass-plugin-itanmaster -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade keepass-plugin-itanmaster -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure keepass-plugin-itanmaster installed
  win_chocolatey:
    name: keepass-plugin-itanmaster
    state: present
    version: 2.28.0.2
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'keepass-plugin-itanmaster' do
  action    :install
  version  '2.28.0.2'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: keepass-plugin-itanmaster,
    Version: 2.28.0.2,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller keepass-plugin-itanmaster
{
   Name     = 'keepass-plugin-itanmaster'
   Ensure   = 'Present'
   Version  = '2.28.0.2'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'keepass-plugin-itanmaster':
  provider => 'chocolatey',
  ensure   => '2.28.0.2',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install keepass-plugin-itanmaster version="2.28.0.2" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator ferventcoder on 13 Aug 2015.

Description

iTans or 'indexed security tokens' are becoming standard to improve access security in
online banking and similar applications.

iTanMaster installs as a KeePass plugin and provides easy access to the encrypted storage
of indexed security tokens.

iTanMaster supports single or dual token systems (presently Interactive Brokers and Flatex) where the final
token is constructed from two separately indexed and then concatenated token parts.

In order to enable iTanMaster token selection the following conditions need to be met:

  • iTanMaster needs to be loaded (ITanMaster.dll resides in KeePass working directory,
    matches the KeePass version, KeePass Version > 2.07, ....)
  • [optional * depending on your safety requirements] the website or application primary
    access key (for the 1st logon step) may be stored and configured according to KeePass
    window recognition rules.
    (The iTanWizard will generate an entry with button 'Store access entries' * this entry
    (if desired) needs to be configured by the user (username/password/window-identification))
  • a special access key titled <ITAN2> MUST be present in the group.
    This key will be used to identify the respective iTan entry window and then intercept
    the credentials creation so that iTanMaster can ask the user for a single (entry title = '<ITAN2>'),
    two (entry title = '<ITAN2>InteractiveBrokers') or three indices (<ITAN2>Flatex) to access the stored / encrypted iTan tokens.
    (The iTanWizard can generate the <ITAN2> or <ITAN2>(InteractiveBrokers/Flatex) entries with
    'Store access entries').
    The entry needs to be configured by the user to support window-identification.
  • iTans and access keys need to be stored in the same KeePass entry key group.

The iTanWizard currently supports 4 iTan import modes: InteractiveBrokers (IB), Flatex, Card and Sequential.

  • IB and Card: This mode is useful in case input data is sequenced in columns and possibly on multiple pages.
  • IB only: the preset is 2 pages, 16 lines and 7 columns. Also (IB), the step 2 database entry (by button 'Store Access Entries') is generated as an <ITAN2>2 for dual token support.
  • Flatex: the preset is 1 page, 11 lines (A..M) and 9 columns (1..9). Also (Flatex), the step 2 database entry (by button 'Store Access Entries') is generated as an <ITAN2>2 for token support.
  • FlatexCH: the preset is 1 page, 10 lines (1..10) and 8 columns (A..H). Also (FlatexCH), the step 2 database entry (by button 'Store Access Entries') is generated as an <ITAN2>2 for token support.
  • Sequential: Parsing wil process the input text line by line, tokens separated by ' ' (space), leading and trailing whitespace is trimmed.

You can also opt to import the iTANs marked as 'onetime use' - KeePass and iTanMaster will mark the tokens so that they will be expired if used.

As a note: for large amounts of tokens, using a scanner and OCR software had proven quite efficient. Visual verification is recommended though! (SimpleOCR - www.simpleocr.com - worked nicely for me).

I recommended to generate and store the primary and secondary access keys first, using the iTanWizard ('Store Access Entries') and manually configuring the remaining details. This ensures those keys will be positioned on top of the list.


tools\chocolateyInstall.ps1
# powershell v2 compatibility
$psVer = $PSVersionTable.PSVersion.Major
if ($psver -ge 3) {
  function Get-ChildItemDir {Get-ChildItem -Directory $args}
} else {
  function Get-ChildItemDir {Get-ChildItem $args}
}
$packageName = 'keepass-plugin-itanmaster'
$typName = 'iTanMaster'
$packageSearch = 'KeePass Password Safe'
$url = 'http://keepass.info/extensions/v2/itanmaster/iTanMaster-2.28.0.2.zip'
$checksum = '0779e88986f952743918f1f8b1ef7e38533f8d1e'
$checksumType = 'sha1'
try {
# search registry for location of installed KeePass
$regPath = Get-ItemProperty -Path @('HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*',
                                    'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*',
                                    'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*') `
                            -ErrorAction:SilentlyContinue `
           | Where-Object {$_.DisplayName -like "$packageSearch*" `
                           -and `
                           $_.DisplayVersion -ge 2.28 `
                           -and `
                           $_.DisplayVersion -lt 3.0 } `
           | ForEach-Object {$_.InstallLocation}
$installPath = $regPath
# search $env:ChocolateyBinRoot for portable install
if (! $installPath) {
  Write-Verbose "$($packageSearch) not found installed."
  $binRoot = Get-BinRoot
  $portPath = Join-Path $binRoot "keepass"
  $installPath = Get-ChildItemDir $portPath* -ErrorAction SilentlyContinue
}
if (! $installPath) {
  Write-Verbose "$($packageSearch) not found in $($env:ChocolateyBinRoot)"
  throw "$($packageSearch) location could not be found."
}
$pluginPath = (Get-ChildItemDir $installPath\Plugin*).FullName
if ($pluginPath.Count -eq 0) {
  $pluginPath = Join-Path $installPath "Plugins"
  [System.IO.Directory]::CreateDirectory($pluginPath)
}
# download and extract PLGX file into Plugins dir
Install-ChocolateyZipPackage -PackageName "$packageName" `
                             -Url "$url" `
                             -UnzipLocation "$pluginPath" `
                             -Checksum "$checksum" `
                             -ChecksumType "$checksumType"
# rename PLGX file so it is clear which plugins are managed via choco
foreach ($i in Get-ChildItem -Path $pluginPath) {
  Rename-Item -Path $i.Fullname `
              -NewName $i.Name.Replace($typName,$packageName) `
              -Force `
              -ErrorAction SilentlyContinue
}
# report state
if ( Get-Process -Name "KeePass" `
                 -ErrorAction SilentlyContinue ) {
  Write-Warning "$($packageSearch) is currently running. Plugin will be available at next restart of $($packageSearch)." 
} else {
  Write-Output "$($packageName) will be loaded the next time KeePass is started."
  Write-Output "Please note this plugin may require additional configuration. Look for a new entry in KeePass' Menu>Tools"
}} catch {
  throw $_.Exception
}
tools\chocolateyUninstall.ps1
# powershell v2 compatibility
$psVer = $PSVersionTable.PSVersion.Major
if ($psver -ge 3) {
  function Get-ChildItemDir {Get-ChildItem -Directory $args}
} else {
  function Get-ChildItemDir {Get-ChildItem $args}
}
$packageName = 'keepass-plugin-itanmaster'
$typName = 'iTanMaster'
$packageSearch = 'KeePass Password Safe'
try {
# search registry for installed KeePass
$regPath = Get-ItemProperty -Path @('HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*',
                                    'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*',
                                    'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*') `
                            -ErrorAction:SilentlyContinue `
           | Where-Object {$_.DisplayName -like "$packageSearch*"} `
           | ForEach-Object {$_.InstallLocation}
$installPath = $regPath
# search $env:ChocolateyBinRoot for portable install
if (! $installPath) {
  Write-Verbose "$($packageSearch) not found in registry."
  $binRoot = Get-BinRoot
  $portPath = Join-Path $binRoot "keepass"
  $installPath = Get-ChildItemDir $portPath* -ErrorAction SilentlyContinue
}
if (! $installPath) {
  Write-Verbose "$($packageSearch) not found in $($env:ChocolateyBinRoot)"
  throw "$($packageSearch) install location could not be found."
}
$pluginPath = (Get-ChildItemDir $installPath\Plugin*).FullName
if ($pluginPath.Count -eq 0) {
  throw "Plugins directory not found."
}
$installFile = Join-Path $pluginPath "$($packageName)"
Remove-Item -Path $installFile* `
            -Force `
            -ErrorAction Continue
if ( Get-Process -Name "KeePass" `
                 -ErrorAction SilentlyContinue ) {
  Write-Warning "$($packageSearch) is running. $($packageName) will be removed at next restart of $($packageSearch)." 
}} catch {
  throw $_.Exception
}

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status

Program

12/06/2014

  • Fixed IP autotype problem (javaw was getting Return too early) by ensuring CLR /Win to consume Return and delay key entry by 500mS
  • Added plugin Revision number to show on windows form

11/07/2014

  • Added support for FlatexCH 1..10 / A..H / single token

03/01/2012

  • Added support for broker Flatex AG (Germany)
  • The code now parses indexes from a single text box, blank delimits the individual tokens
  • (IB) Removed space as delimiter between tokens (website account access chokes on space between tokens)

Package

  • Automatically built and uploaded by dtgm

Discussion for the KeePass Plugin iTanMaster Package

Ground Rules:

  • This discussion is only about KeePass Plugin iTanMaster and the KeePass Plugin iTanMaster package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or KeePass Plugin iTanMaster, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus