On Sun, Jun 24, 2012 at 09:59:55PM -0800, Jef Spaleta wrote:
On Sun, Jun 24, 2012 at 9:50 PM, Pierre-Yves Chibon pin...@pingoured.fr
wrote:
I had a number of problem with guake and its gconf schema, so after
discussion here I added this to the spec file:
%posttrans
killall -HUP
On Sun, Jun 24, 2012 at 9:50 PM, Pierre-Yves Chibon pin...@pingoured.fr wrote:
I had a number of problem with guake and its gconf schema, so after
discussion here I added this to the spec file:
%posttrans
killall -HUP gconfd-2 /dev/null || :
That pretty much forces gconf to reload.
Uhm
On Mon, Jun 25, 2012 at 9:46 AM, Jef Spaleta jspal...@gmail.com wrote:
On Mon, Jun 25, 2012 at 5:36 AM, Tom London seli...@gmail.com wrote:
Hmm... Still seeing spew:
Here is what I did:
1. I 'rpm -Uvh --force' the new package.
2. I 'recovered' my old ~/.gconf/apps/revelation/ settings (I had
On Mon, Jun 25, 2012 at 11:22 AM, Tom London seli...@gmail.com wrote:
On Mon, Jun 25, 2012 at 9:46 AM, Jef Spaleta jspal...@gmail.com wrote:
On Mon, Jun 25, 2012 at 5:36 AM, Tom London seli...@gmail.com wrote:
Hmm... Still seeing spew:
Here is what I did:
1. I 'rpm -Uvh --force' the new
On Sun, Jun 24, 2012 at 12:57 PM, Jef Spaleta jspal...@gmail.com wrote:
Rawhide target scratch build of the upstream tree with the fix.
http://koji.fedoraproject.org/koji/taskinfo?taskID=4191839
I have done a local build and test on an F16 system. Revelation
informs me that the key file is
this is part of the gconf drift introduced in 0.14.3.
See comments in related upstream report
http://oss.codepoet.no/revelation/issue/77/generating-password-on-rhel6-raises
A fresh test user wont experience the preference problem.
The question becomes how do we force gconf to load the new
On Sun, Jun 24, 2012 at 12:45 PM, Jef Spaleta jspal...@gmail.com wrote:
Users with existing revelation configurations can blow away
.gconf/apps/revelation and relogin to avoid the errors and reconfig
revelation in the process. But clearly that is not optimal. If there
is a packaging mechanism
On Sun, Jun 24, 2012 at 12:17 PM, Tom London seli...@gmail.com wrote:
Haven't checked the crypto changes, but I do notice this spew when I
try 'Edit-Preferences':
Okay I think I have the GConf scriptlets fixed:
http://koji.fedoraproject.org/koji/taskinfo?taskID=4191873
On local testing.
On 06/24/2012 05:07 PM, Jef Spaleta wrote:
On Sun, Jun 24, 2012 at 12:45 PM, Jef Spaleta jspal...@gmail.com wrote:
Users with existing revelation configurations can blow away
.gconf/apps/revelation and relogin to avoid the errors and reconfig
revelation in the process. But clearly that is not
On Sun, 2012-06-24 at 13:39 -0800, Jef Spaleta wrote:
On Sun, Jun 24, 2012 at 12:17 PM, Tom London seli...@gmail.com wrote:
Haven't checked the crypto changes, but I do notice this spew when I
try 'Edit-Preferences':
Okay I think I have the GConf scriptlets fixed:
On Sat, Jun 16, 2012 at 12:31:46PM -0500, Jon Ciesla wrote:
On Fri, Jun 15, 2012 at 4:18 PM, Chris Murphy li...@colorremedies.com wrote:
On Jun 15, 2012, at 12:51 PM, Jon Ciesla wrote:
They are using PBKDF2 with SHA-256, default 500 rounds up to 100,000
rounds. The database is locally
Quoting Jef Spaleta (2012-06-15 22:00:31)
So yeah... revelation is back to being entirely noarch python again.
Is bouncing a package from arch to noarch as an update going to cause
problems?
Last time I've done this, I had to add Obsoletes: XX current_VR
I assume this hasn't changed in past
On Fri, Jun 15, 2012 at 4:18 PM, Chris Murphy li...@colorremedies.com wrote:
On Jun 15, 2012, at 12:51 PM, Jon Ciesla wrote:
They are using PBKDF2 with SHA-256, default 500 rounds up to 100,000
rounds. The database is locally encrypted. Offline access is possible. The
free version supports
On Thu, Jun 14, 2012 at 11:24:20AM -0700, Adam Williamson wrote:
On Thu, 2012-06-14 at 17:21 +0200, Tomas Mraz wrote:
On Thu, 2012-06-14 at 07:40 -0500, Josh Bressers wrote:
Hello all,
I suspect this is going to be a weird problem to figure out.
Relevation password manager
On Jun 15, 2012, at 3:09 AM, Daniel P. Berrange wrote:
FWIW, I'd recommend KeePassX as an impressive alternative to Revelation,
with much more advanced flexible functionality
I've been using Lastpass for a few months and like the automatic
synchronization between computers and browsers
It seems there is a new upstream for revelation as of March this year.
I'll poke at them a little bit to see what's going on. It's been a
while since there has been an active upstream for this codebase.
Here's a thought... what's Debian's policy concerning security issues
is packages with a
On Fri, 2012-06-15 at 10:56 -0800, Jef Spaleta wrote:
It seems there is a new upstream for revelation as of March this year.
I'll poke at them a little bit to see what's going on. It's been a
while since there has been an active upstream for this codebase.
Have they fixed the crash-on-exit
On Fri, Jun 15, 2012 at 11:05 AM, Adam Williamson awill...@redhat.com wrote:
On Fri, 2012-06-15 at 10:56 -0800, Jef Spaleta wrote:
It seems there is a new upstream for revelation as of March this year.
I'll poke at them a little bit to see what's going on. It's been a
while since there has
On Fri, Jun 15, 2012 at 11:14 AM, Jef Spaleta jspal...@gmail.com wrote:
On Fri, Jun 15, 2012 at 11:05 AM, Adam Williamson awill...@redhat.com wrote:
On Fri, 2012-06-15 at 10:56 -0800, Jef Spaleta wrote:
It seems there is a new upstream for revelation as of March this year.
I'll poke at them a
On Fri, 2012-06-15 at 11:14 -0800, Jef Spaleta wrote:
On Fri, Jun 15, 2012 at 11:05 AM, Adam Williamson awill...@redhat.com wrote:
On Fri, 2012-06-15 at 10:56 -0800, Jef Spaleta wrote:
It seems there is a new upstream for revelation as of March this year.
I'll poke at them a little bit to
So yeah... revelation is back to being entirely noarch python again.
Is bouncing a package from arch to noarch as an update going to cause
problems?
-jef
On Fri, Jun 15, 2012 at 11:22 AM, Adam Williamson awill...@redhat.com wrote:
On Fri, 2012-06-15 at 11:14 -0800, Jef Spaleta wrote:
On Fri,
On Fri, Jun 15, 2012 at 11:22 AM, Adam Williamson awill...@redhat.com wrote:
Well, not so much exit as shutdown. It seems to frequently throw an
exception of some kind on shutdown, which seems to block up the shutdown
process until you dismiss the error dialog. Maybe it's Just Me (TM)
On Jun 15, 2012, at 12:51 PM, Jon Ciesla wrote:
They are using PBKDF2 with SHA-256, default 500 rounds up to 100,000 rounds.
The database is locally encrypted. Offline access is possible. The free
version supports Google Authenticator for TFA, other forms of TFA are
available in the not
On Thu, 14 Jun 2012 07:40:50 -0500
Josh Bressers j...@bress.net wrote:
Hello all,
I suspect this is going to be a weird problem to figure out.
Relevation password manager
https://admin.fedoraproject.org/pkgdb/applications/Revelation
Password Manager
Has been found to be unsafe.
On 06/14/2012 10:42 AM, Kevin Fenzi wrote:
On Thu, 14 Jun 2012 07:40:50 -0500
Josh Bressers j...@bress.net wrote:
Hello all,
I suspect this is going to be a weird problem to figure out.
Relevation password manager
https://admin.fedoraproject.org/pkgdb/applications/Revelation
Password Manager
On Thu, 2012-06-14 at 07:40 -0500, Josh Bressers wrote:
Hello all,
I suspect this is going to be a weird problem to figure out.
Relevation password manager
https://admin.fedoraproject.org/pkgdb/applications/Revelation Password Manager
Has been found to be unsafe.
On Thu, 2012-06-14 at 17:21 +0200, Tomas Mraz wrote:
On Thu, 2012-06-14 at 07:40 -0500, Josh Bressers wrote:
Hello all,
I suspect this is going to be a weird problem to figure out.
Relevation password manager
https://admin.fedoraproject.org/pkgdb/applications/Revelation Password
On Thu, Jun 14, 2012 at 08:42:47AM -0600, Kevin Fenzi wrote:
- Obsolete the package with another password manager thats more secure.
This is not very ideal though as it's unlikely to have the same
features and so on.
- Update the package with a readme, etc on the issue, replacing the
On Thu, Jun 14, 2012 at 08:42:47AM -0600, Kevin Fenzi wrote:
Possible options:
...
- Update the file format to fix the password problem and transparently
upgrade the file the next time the user opens it.
I've had a local patch doing this for some time now. The blog post has
me rethinking
29 matches
Mail list logo
