Now you can use a helper-script to set your file paths:Ĭopy-KeePassDB.ps1 -SourceDB "C:\mymaster.kdbx" -TargetDB "C:\mylocal.kdbx" -KeePassFolder "C:\Program Files\KeepPass\" Write-Host "Database copied and new credentials set, only accessible to $env:USERDOMAIN\$env:UserName" $m_pKeyNew.AddUserKey((New-Object ($PasswordForTarget))) $PwDatabase.Open($m_ioInfo,$m_pKey,$IStatusLogger) $m_pKey.AddUserKey((New-Object ($PasswordForSource))) $PwDatabase = new-object KeePassLib.PwDatabase # remove an existing copy and copy the masterĬopy-Item $SourceDB -Destination $TargetDB (Get-ChildItem -recurse $KeePassFolder | Where-Object ) | out-null $pass2 = Read-Host 'Type the password for new Local-KeePass database' -AsSecureString $pass = Read-Host 'Type the password for Master-KeePass database' -AsSecureString
Save the following into Copy-KeePassDB.ps1 param( So I wrote a PowerShell script that makes a copy of the database and sets the new master key That's only a few clicks, but I rather automate things. However after I changed any data in my master database, I had to make a new copy and change the masterkey again. This way I only have to type a short password, but when I use KeePass on different devices I still only use the strong password. My solution was to make a copy for local read-only use and set the master key with a less-strong password and my Windows user account. However I don't want to use it as a key for my main KeePass database. On my main workstation at home, my Windows account it pretty secure. You can also specify a key file or use your Windows account. KeePass offers more than just a password for authentication. I'm using a very long and complex master-password, which is kind of annoying to type in every time I open the program. I recently migrated from Password Safe to KeePass for storing my passwords. The Real Life Risks Of Re Using The Same Passwords by Bill Hess. This article is about using password managers, if you don't know why this is a good idea, read the article:
0 kommentar(er)
