[opensuse] Where is keepassX 1.X in repos? (not security, that has 2 alpha and CANNOT ready my files)
All, Where is a version of keepassx 1X in the repositories. To my surprise, the current keepassx 2.0 in security CAN NOT read my keepass files (.kdb). This is a panic moment - I have hundreds of entries I must be able to get to. This is crazy. Not a good first exposure for 13.1... If you find a link let me know. Otherwise, I'll keep picking around. Also, How can I get a status bar on this firefox... whatever it is. Status4Evar cannot even get a bottom status bar and now it is trying to put all url status on my address bar - looks horrible... I love updates :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne Ne 13. července 2014 04:41:18, David C. Rankin napsal(a):
All,
Where is a version of keepassx 1X in the repositories. To my surprise, the current keepassx 2.0 in security CAN NOT read my keepass files (.kdb). This is a panic moment - I have hundreds of entries I must be able to get to. This is crazy. Not a good first exposure for 13.1... If you find a link let me know. Otherwise, I'll keep picking around.
You can download it from KeePass web and launch it using Mono. Best, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
On 07/13/2014 05:39 AM, Vojtěch Zeisek wrote:
Dne Ne 13. července 2014 04:41:18, David C. Rankin napsal(a):
All,
Where is a version of keepassx 1X in the repositories. To my surprise, the current keepassx 2.0 in security CAN NOT read my keepass files (.kdb). This is a panic moment - I have hundreds of entries I must be able to get to. This is crazy. Not a good first exposure for 13.1... If you find a link let me know. Otherwise, I'll keep picking around.
You can download it from KeePass web and launch it using Mono. Best, Vojtěch
Why using mono, the app on 11.4 was a qt app? This is a very serious issue that will catch any users of the earlier 0.4.3 by surprise and leave them dead in the water. I have 10 years of data in my kdb database and it just blows my mind that the "New" version cannot read any of it. (shaking head in disgust) Surely this has been addressed. Why not provide both versions until 2.0alpha grows up enough to be able to read .kdb files instead of its .kdbx files? I opened a report at: https://bugzilla.novell.com/show_bug.cgi?id=887043 -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-13 12:55, David C. Rankin wrote:
Why using mono, the app on 11.4 was a qt app? This is a very serious issue that will catch any users of the earlier 0.4.3 by surprise and leave them dead in the water. I have 10 years of data in my kdb database and it just blows my mind that the "New" version cannot read any of it. (shaking head in disgust) Surely this has been addressed. Why not provide both versions until 2.0alpha grows up enough to be able to read .kdb files instead of its .kdbx files?
Maybe you can install a virtual machine with 11.4, install keepassx there, red your files, and export them, somehow - this last part I don't know if it can do, I do not use that program. However, I see many repos having version 0.4.3 for openSUSE 13.1. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 07/13/2014 07:17 AM, Carlos E. R. wrote:
On 2014-07-13 12:55, David C. Rankin wrote:
Why using mono, the app on 11.4 was a qt app? This is a very serious issue that will catch any users of the earlier 0.4.3 by surprise and leave them dead in the water. I have 10 years of data in my kdb database and it just blows my mind that the "New" version cannot read any of it. (shaking head in disgust) Surely this has been addressed. Why not provide both versions until 2.0alpha grows up enough to be able to read .kdb files instead of its .kdbx files?
Maybe you can install a virtual machine with 11.4, install keepassx there, red your files, and export them, somehow - this last part I don't know if it can do, I do not use that program.
However, I see many repos having version 0.4.3 for openSUSE 13.1.
Nah... I'm just going to rebuild a 0.4.3 rpm for 13.1. Easier all the way around. Only current build errors are scope errors on getpid(): [ 39%] Building CXX object src/CMakeFiles/keepassx.dir/lib/random.cpp.o /home/david/rpmbuild/BUILD/keepassx-0.4.3/src/lib/random.cpp: In function 'void initStdRand()': /home/david/rpmbuild/BUILD/keepassx-0.4.3/src/lib/random.cpp:98:19: error: 'getpid' was not declared in this scope stream << getpid(); ^ make[2]: *** [src/CMakeFiles/keepassx.dir/lib/random.cpp.o] Error 1 make[1]: *** [src/CMakeFiles/keepassx.dir/all] Error 2 make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.GJAMYK (%build) Shouldn't be that hard to figure out what compiler defaults are causing the issue. It may be as simple as the build string missing a `-std=` that will allow it to compile without error. <rant> I know it is the `security` repo supported by build service, but c'mon, you change versions of a critical app and don't even check that what you are providing now is compatible with what was built 3 months ago?? It's like the kde4 kiddies moved over to the security repo..... </rant> -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
Nah... I'm just going to rebuild a 0.4.3 rpm for 13.1. Easier all the way around.
+1.
Only current build errors are scope errors on getpid():
[ 39%] Building CXX object [ src/CMakeFiles/keepassx.dir/lib/random.cpp.o /home/david/rpmbuild/BUILD/keepassx-0.4.3/src/lib/random.cpp: In function 'void initStdRand()': /home/david/rpmbuild/BUILD/keepassx-0.4.3/src/lib/random.cpp:98:19: error: 'getpid' was not declared in this scope stream << getpid(); ^ make[2]: *** [src/CMakeFiles/keepassx.dir/lib/random.cpp.o] Error 1 make[1]: *** [src/CMakeFiles/keepassx.dir/all] Error 2 make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.GJAMYK (%build)
Shouldn't be that hard to figure out what compiler defaults are causing the issue.
I think that's a namespace issue, but should be easy to fix.
<rant> I know it is the `security` repo supported by build service, but c'mon, you change versions of a critical app and don't even check that what you are providing now is compatible with what was built 3 months ago?? It's like the kde4 kiddies moved over to the security repo..... </rant>
Our testing processes leave a lot to be desired - an awful lot. As to whether keepass is critical, I can't say - I've never even heard of it :-) -- Per Jessen, Zürich (20.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/13/2014 12:34 PM, Per Jessen wrote:
Our testing processes leave a lot to be desired - an awful lot. As to whether keepass is critical, I can't say - I've never even heard of it :-)
If you had ever tried it in the past, it was an app you cannot live without. (better than e-mail...) I found it about a decade ago, as soon as it came out and I have that many years of info in it. My credentials to all my legal research sites, the state bar, the FAA medical program, The Board of Professional Engineers, plus every damn internet account I've collected over the past 10 years -- so "Is it CRITICAL?" you tell me. All in a cryptographic format so secure you can post the datafile publicly and feel relatively secure. I'll post back on the scope issue for your help. I'm fairly good at those issues after working with TDE through the gcc 4.5, 4.6 and 4.7 transitions, but every once in a while, I just can't see the forest for the trees ;-) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-13 19:58, David C. Rankin wrote:
On 07/13/2014 12:34 PM, Per Jessen wrote:
All in a cryptographic format so secure you can post the datafile publicly and feel relatively secure.
I would prefer a plain text file encrypted with PGP, using a text editor that can open it in memory, without temporary unencrypted files. No, I don't know of such a thing. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
David C. Rankin wrote:
On 07/13/2014 12:34 PM, Per Jessen wrote:
Our testing processes leave a lot to be desired - an awful lot. As to whether keepass is critical, I can't say - I've never even heard of it :-)
If you had ever tried it in the past, it was an app you cannot live without. (better than e-mail...) I found it about a decade ago, as soon as it came out and I have that many years of info in it. My credentials to all my legal research sites, the state bar, the FAA medical program, The Board of Professional Engineers, plus every damn internet account I've collected over the past 10 years -- so "Is it CRITICAL?" you tell me.
Okay, so kind of like the KDE wallet ? Yes, I can see that being pretty critical. -- Per Jessen, Zürich (18.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-13 19:34, Per Jessen wrote:
David C. Rankin wrote:
Shouldn't be that hard to figure out what compiler defaults are causing the issue.
I think that's a namespace issue, but should be easy to fix.
Well, I mentioned that the old package is available in several repos, perhaps half a dozen, built for 13.1. You can pick it from there, or just pick the spec file and find out how they did and what patches they applied.
Our testing processes leave a lot to be desired - an awful lot. As to whether keepass is critical, I can't say - I've never even heard of it :-)
He was using 11.4, right? The process of upgrading from Evergreen to the current release is not designed for :-( -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2014-07-13 19:34, Per Jessen wrote:
David C. Rankin wrote:
Shouldn't be that hard to figure out what compiler defaults are causing the issue.
I think that's a namespace issue, but should be easy to fix.
Well, I mentioned that the old package is available in several repos, perhaps half a dozen, built for 13.1. You can pick it from there, or just pick the spec file and find out how they did and what patches they applied.
Even better.
Our testing processes leave a lot to be desired - an awful lot. As to whether keepass is critical, I can't say - I've never even heard of it :-)
He was using 11.4, right?
The process of upgrading from Evergreen to the current release is not designed for :-(
I doubt if following the regular upgrade process would have or would provide any less difficulties, Carlos. I have a very recent example where upgrading to the latest-and-greatest completely screwed up things for more than six months. (yes, support is lacking too). Upgrading openSUSE _is_ _dangerous_ in an environment where people depend on openSUSE working every day. Like I said, "our testing processes leave a lot to be desired - an awful lot"! -- Per Jessen, Zürich (18.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/13/2014 07:17 AM, Carlos E. R. wrote:
However, I see many repos having version 0.4.3 for openSUSE 13.1.
I'll look, I searched OBS, but the only thing I found was 2.0alpha. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/14/2014 02:36 AM, David C. Rankin wrote:
On 07/13/2014 07:17 AM, Carlos E. R. wrote:
However, I see many repos having version 0.4.3 for openSUSE 13.1.
I'll look, I searched OBS, but the only thing I found was 2.0alpha.
Found it! The https://software.opensuse.org/package search crashed (see initial post). Once it was back up. It was easy to locate. Here is a screenshot: http://www.3111skyline.com/dl/ss/keepassx.jpg If you are not using keepassx, you should be. It beats the file/gpg trick :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-14 10:05, David C. Rankin wrote:
If you are not using keepassx, you should be. It beats the file/gpg trick :)
Nay. The gpg file thing is cross-platform-standard. :-) Of course, I don't get the cute features you do, but anyway, I don't use KDE... -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 7/14/2014 1:05 AM, David C. Rankin wrote:
Here is a screenshot:
http://www.3111skyline.com/dl/ss/keepassx.jpg
If you are not using keepassx, you should be. It beats the file/gpg trick :)
Agreed that as our hard-earned geezerhood approaches, the rising "number-of-things-to-remember" curve crosses the "available-internal-memory-slots" declining curve we will all need some password vault. However, I've found I need these keys on the go, and prefer to put them in something that can run on my phone, tablet, laptop, and desktop, and have all of them kept in sync. There are dozens of this type of thing for both Android and iPhone, and there are at least three implementations of Keepass compatible apps in the android play store. and Minikeepass for iphone (and probably more in the apple store). You can Sync via dropbox, since your keepass file is encrypted by its own mechanism (and does not rely on dropbox for protection). There are dropbox clients for everything. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/14/2014 01:36 PM, John Andersen wrote:
Agreed that as our hard-earned geezerhood approaches, the rising "number-of-things-to-remember" curve crosses the "available-internal-memory-slots" declining curve we will all need some password vault.
However, I've found I need these keys on the go, and prefer to put them in something that can run on my phone, tablet, laptop, and desktop, and have all of them kept in sync.
JA I agree with the portability need, but unless it is open-souce, there IS NO WAY IN HELL I'm trusting my credentials to any package I can't verify isn't copying it somewhere else :-) That has always been the rub. Think about all those duplicitous apps out there designed to steal your personal information. Chromium, and just about every other app that touches your information collects it and phones-home for "Big Data" mining. With the risk of identity theft at an all time high, no way am I trusting anything from apple or google (or 3rd parties that write for their stores) with my data. That is where keepassx has always had the advantage. Open-source, and in simpler times, it provided the solution by a datafile that was transferable between windows and linux (that was a big deal 10 years ago). It also made a portable version for usb. I haven't had the time to keep up on all the developments, but keepassx was always the stepchild of 'keepass' which has continued heavy development and does have a mobile version floating around, but licensing gets mucked up when offered through apple or google. I'm glad to see 2.0alpha under development, but do not have the time or desire to spend 1/2 day kicking the tires to enable a comfortable move to it from 0.4.3. Moreover, what to do about Linux/Windows portability of the new .kdbx format. Can it be transferred to the windows boxes at the office, and can the office pw file be read by whoever orders the next round of supplies? That is why there is "stable/current release" software and then a classification called "Alpha" software (for testing and development, but NOT for mainstream use). Distros should not release "Alpha" software in place of "stable" software for just these reasons. There are real world costs involved with with this that, to a large degree, prevents Linux from ever being considered for business use. I digress. I always keep a lookout for a clean keepass or keepassx to hit the mobile shops, but so far, I just haven't found one that is trustworthy enough to try with real data. The thought of entering test data and then having to capture all traffic from the device for at least 30 days to insure it wasn't phoning-home just isn't practical for me. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13/07/14 10:41, David C. Rankin wrote:
All,
Where is a version of keepassx 1X in the repositories. To my surprise, the current keepassx 2.0 in security CAN NOT read my keepass files (.kdb). This is a panic moment - I have hundreds of entries I must be able to get to. This is crazy. Not a good first exposure for 13.1... If you find a link let me know. Otherwise, I'll keep picking around.
David, I have got KeePassX 2.0 alpha 6 installed here. In the Database menu there is an option to "Import KeePass 1 database", which should be able to import a .kbd file (if you can provide the Master Key). Are you saying you don't see that menu entry, or that it won't import the .kbd file? Bob - -- Bob Williams System: Linux 3.11.10-17-desktop Distro: openSUSE 13.1 (x86_64) with KDE Development Platform: 4.13.2 Uptime: 06:00am up 5 days 9:43, 4 users, load average: 0.09, 0.08, 0.06 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlPDCCkACgkQ0Sr7eZJrmU7T4wCfQbujqIDgd4LYMxZODMxBC+vq AckAoKTA8yJPNGzrF09Pus/4v/zp+oT3 =Ztu+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Bob Williams -
Carlos E. R. -
David C. Rankin -
John Andersen -
Per Jessen -
Vojtěch Zeisek