Open GoogleCodeExporter opened 9 years ago
I managed to recreate this issue using the latest release of TeamPass, build on
a clean install of Ubuntu 10.0.4 LAMP.
The files are still getting uploaded to the files directory but the PHP scripts
are getting the wrong file name passed to them, the difference is that the
files are now retain their original file names when they reach the files
directory. However the PHP scripts are still looking for files with long random
alphanumeric names and still failing.
I ended up working around this issue on, firstly my test TeamPass installation
and then on my real CpassMan installation by noting the random file name that
the PHP code is looking for and, renaming the uploaded file to match this, then
attempting to restore the same file again. The process generates the same
(wrong) filename and passes it to the PHP code which tries to open, decrypt and
restore the db dump. This time however it then finds the file it is expecting
and the db is restored.
As this is apparently an ongoing issue with TeamPass I'll file this on the
GitHub issue tracker too.
The strange this is I can remember restoring backups from dumps in the past and
it worked as expected.
There is some good news, once I got my passwords back I upgraded to TeamPass on
my real server, which I had been meaning to do for a while but the forced
downtime gave me the opportunity, thanks for implementing those automated
backups.
Original comment by spastic...@gmail.com
on 14 Feb 2012 at 5:31
Hi,
I've corrected a bug concerning files management in the next release 2.1.4 and
maybe the issue you're facing is a consequence of this old bug.
I've done some tests on my actual test base with this (soon released) 2.1.4 and
I've been able to create the encrypted backup and restoring it without any
issue.
Please wait until next release, update and tell me.
Original comment by nils.lau...@gmail.com
on 15 Feb 2012 at 7:47
Cheers nils, I'll pull the 2.1.4 code from GitHub and try and recreate in the
test server. I'll post results here and and on the GitHub issues page.
Original comment by spastic...@gmail.com
on 16 Feb 2012 at 4:36
Original issue reported on code.google.com by
spastic...@gmail.com
on 13 Feb 2012 at 11:09