mon ran through the
> > next hour change and is still running as expected. The man page states
> > that the '-f' option matches against the full command line, not just the
> > process name. So, looking at the gnome-keyring-daemon command line:
> >
> >18
hat the '-f' option matches against the full command line, not just the
> process name. So, looking at the gnome-keyring-daemon command line:
>
>1857 ?SLsl 0:00 /usr/bin/gnome-keyring-daemon --foreground
> --components=pkcs11,secrets --control-directory=/run/use
Well, it appears like most things in life this one was self inflicted.
🤬
Yesterday I was working on another project and to verify something was
occurring the 'strace' utility was recommended. It dawned on me that
this could help me get a clue as to what was happening to the
gnome-keyr
ebian-archive-keyring_2023.4_all.deb
but neither provides the missing keys.
Which debian keyring packages do I have to install to verify Debian
packages from the archive repositories?
Regards
Harri
* On 2023 14 Aug 21:29 -0500, Max Nikulin wrote:
> On 14/08/2023 07:30, Nate Bargmann wrote:
> > Now, while typing this email all keyring PIDs have vanished!
>
> It may be a way to minimize RAM usage.
I don't think so. It has been persistent in the past in Buster and
Bullse
On 14/08/2023 07:30, Nate Bargmann wrote:
I have been using the GNOME keyring applet to manage the SSH public key
passwords I use as it prompts to save passwords and then lets me SSH to
other hosts without out a password prompt.
I do not know how it is arranged in Gnome, but I hope my
I now have two desktop systems running Bookworm with GNOME. The laptop
was upgraded last month and I upgraded the desktop this afternoon. I
have been using the GNOME keyring applet to manage the SSH public key
passwords I use as it prompts to save passwords and then lets me SSH to
other hosts
lease: Key
is stored in legacy trusted.gpg
keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in
apt-key(8) for details.
Has anybody else seen this? If so, what did you do? And did it help?
I _think_ the key should be stored in its own file under
/etc/apt/trusted.gp
gt;> Key is stored in legacy trusted.gpg
>>keyring (/etc/apt/trusted.gpg), see the DEPRECATION section
>> in apt-key(8) for details.
>> Has anybody else seen this? If so, what did you do? And did it help?
> I _think_ the key should be stored in its own file
Am 20.06.2023 um 04:58 schrieb Rick Thomas:
> PS: As an aside, it appears that the VirtualBox developers at Oracle waited
> until Bookworm was officially released before they started working on getting
> a bookworm version of their software, so I'm still using the Bullseye version
> -- which se
"apt update" I get this message:
> .W:
> https://download.virtualbox.org/virtualbox/debian/dists/bullseye/InRelease:
> Key is stored in legacy trusted.gpg
>keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in
> apt-key(8) for details.
>
> I&#
rtualbox/debian/dists/bullseye/InRelease: Key
is stored in legacy trusted.gpg
keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in
apt-key(8) for details.
I've thoroughly RTFM in search of a clue as to how to fix this, but I can't
figure out what I'm sup
Hi,
I have 4 EC keys (one is nistp256 [daily driver] and the others are nistp384).
I attempted to locally sign Greg's key
(647F28654894E3BD457199BE38DBBDC86092693E) using one of my nistp384 public
key, and using --local-user to specify the key. After entering the
passphrase, instead of the key be
webkit2gtk_2.34.6.orig.tar.xz
-rw-r--r-- 1 lbrtchx lbrtchx 195 Feb 17 13:08
webkit2gtk_2.34.6.orig.tar.xz.asc
$
$ file webkit2gtk_2.34.6-1~deb11u1.dsc
webkit2gtk_2.34.6-1~deb11u1.dsc: PGP signed message
$
$ gpg --verbose --keyring ./webkit2gtk_2.34.6-1~deb11u1.dsc --verify
webkit2gtk_2.34.6.orig.tar.xz.asc
.debian.tar.xz
gpg: Signature made Thu 17 Feb 2022 07:12:45 AM CST
gpg:using DSA key 5AA3BC334FD7E3369E7C77B291C559DBE4C9123B
gpg: Can't check signature: No public key
$
# apt-get install debian-keyring debian-archive-keyring
The key to verify those files is probably in the first of thos
$ gpg --verbose --recv-key 5AA3BC334FD7E3369E7C77B291C559DBE4C9123B
gpg: data source: https://keys.openpgp.org:443
gpg: armor header: Comment: 5AA3 BC33 4FD7 E336 9E7C 77B2 91C5 59DB E4C9 123B
gpg: pub dsa1024/91C559DBE4C9123B 2008-06-02 Adrián Pérez de Castro
(personal)
gpg: key 91C559DBE4C912
:using DSA key 5AA3BC334FD7E3369E7C77B291C559DBE4C9123B
gpg: Can't check signature: No public key
$
# apt-get install debian-keyring debian-archive-keyring
# apt-key update
# apt-get update
Reading package lists... Done
Building dependency tree... Done
Reading state information...
On Sat, 2021-02-27 at 09:36 -0500, reader wrote:
> I want to run evolution without any prompting for login keyring auth.
>
> I found piles of message on google about this, most are quite old. And
> quite of few tell of long complicated list of things to do.
>
> Surely the
I want to run evolution without any prompting for login keyring auth.
I found piles of message on google about this, most are quite old. And
quite of few tell of long complicated list of things to do.
Surely the is some basic and fairly simple may to remove that obstacle.
Can someone tell me
Hi.
On Sat, May 04, 2019 at 11:30:26PM +0530, Bapi Dey wrote:
> I am using deb.debian.org
>
> I need a Keyring for my apt. I am not able to find pub key of
> 8B48AD6246925553.
>
> I use apt-key adv --keyserver http://keyring.debian.org --recv-keys
apt-key ad
I am using deb.debian.org
I need a Keyring for my apt. I am not able to find pub key of
8B48AD6246925553.
I use apt-key adv --keyserver http://keyring.debian.org --recv-keys
But return error:- no valid OpenPGP data found. Total number process 0.
following signatures couldn't be verified because the public key
is not available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY
AA8E81B4331F7F50
Then I searched and saw a forum post sharing that the
debian-archive-keyring is maybe not up-to-date.
I downloaded the latest from sid/unstable and using
On 4/10/2018 4:33 PM, J.W. Foster wrote:
I just installed a new Debian 9 system on a reformatted disk in a multidisk
system. I used the Netinstall cd from Debian. Installation went ok and I am
sending this from the system. Problem is I tried to add the contrib and
non-free repos to synaptic i.
I just installed a new Debian 9 system on a reformatted disk in a multidisk
system. I used the Netinstall cd from Debian. Installation went ok and I am
sending this from the system. Problem is I tried to add the contrib and
non-free repos to synaptic i.e. apt sources.list I simply copied the
s
Hi,
On Mon, 16 Oct 2017 12:34:45 +0500
"Alexander V. Makartsev" wrote:
> For your situation I suggest to upgrade your installation to latest
> release, which is based on jessie, according to official FAQ:
> https://wiki.vyos.net/wiki/FAQ#Usage
> Updating to latest VyOS release is a good thing for
I don't have any experience with VyOS specifically, but at least have
some interest to try it at some point.
For your situation I suggest to upgrade your installation to latest
release, which is based on jessie, according to official FAQ:
https://wiki.vyos.net/wiki/FAQ#Usage
Updating to latest VyOS
Hi,
I've been asked that "can we verify old archive - e.g. squeeze? Since
VyOS is based on squeeze and want to build packages with squeeze
environment, and also want to ensure package is sane with GPG".
I have no idea - can someone tell me your idea, please?
--
Hideki Yamane
nt to automatize this process, but let nautilus starts in this
folder AND/OR use my terminal and the password saved on my gnome-keyring
Is possible?
Thanks you
Hi, folks,
I'm using Icedove with OpenPGP enabled by Enigmail.
Every time I open the application and send my first e-mail, it prompts me
for my PGP key.
After inserting it and mark to remember, it asks for my Gnome Keyring
password.
After that, everything works fine and I can send e-mails wi
2015-06-25 17:10 keltezéssel, Sven Arvidsson írta:
On Thu, 2015-06-25 at 17:00 +0200, Fekete Tamás wrote:
However, the Evolution still wants to synchronize my google calendar,
even if I don't want to. When I click on the gnome calendar (top
middle of the screen), a password-requiring windows c
On Thu, 2015-06-25 at 17:00 +0200, Fekete Tamás wrote:
> However, the Evolution still wants to synchronize my google calendar,
> even if I don't want to. When I click on the gnome calendar (top
> middle of the screen), a password-requiring windows comes to ask my
> password to do it. I'm unable to
7;d like.
Seahorse did solve the problem. Keyring password window disappeared when
I start Gnome. So thank you again.
However, the Evolution still wants to synchronize my google calendar,
even if I don't want to. When I click on the gnome calendar (top
middle of the screen), a password-r
On Wed, 2015-06-24 at 20:29 +0200, Fekete Tamás wrote:
> How can I let Evolution know my wish, that stop doing synchornisationtrials?
> How can I make Gnome stop asking keyring password on boot up?
And what's the use of a keyring at all(I completely not understand
It's a passw
Hy all,
I use gnome with wheezy and got a problem with a password keyring I
never used
before. The problem is that after Gnome starts, gives me a window which
asks me
to give the login keyring (I had to translate the
window title, so it might be different in english compared I gave it
former
Am 02.04.2015 um 14:37 schrieb Jonathan Dowland:
> Hi,
>
> On Thu, Apr 02, 2015 at 12:15:44PM +0200, Frank Lanitz wrote:
>> I've got a quiet big keyring (>2k keys inside it) and since last updates
>> of enigmail I'm recognizing issues with it. Ehenever it's
Hi,
On Thu, Apr 02, 2015 at 12:15:44PM +0200, Frank Lanitz wrote:
> I've got a quiet big keyring (>2k keys inside it) and since last updates
> of enigmail I'm recognizing issues with it. Ehenever it's about
> verifying a signature Enigmail is starting a gpg2 process l
Hi folks,
I've got a quiet big keyring (>2k keys inside it) and since last updates
of enigmail I'm recognizing issues with it. Ehenever it's about
verifying a signature Enigmail is starting a gpg2 process like that
/usr/bin/gpg2 --charset utf-8 --display-charset utf-8 --batch
WHEN I DO:
~/$ gnome-keyring-daemon --start
I GET:
Couldn't access conrol socket:
/home/tom/.cache/keyring-qGnJVR/control: No such file or directory
GNOME_KEYRING_CONTROL=/home/tom/.cache/keyring-laCd8D
SSH_AUTH_SOCK=/home/tom/.cache/keyring-laCd8D/ssh
GPG_AGENT_INFO=/home/tom/.cache/ke
I installed wheezy a week ago (with the installer which includes
xfce), and nm-applet was working fine. But today it won't start and
gives the message:
WARNING: gnome-keyring:: couldn't connect to:
/home/tom/.cache/keyring-4LJPFc/pkcs11: No such file or directory
** Message: applet n
I installed wheezy a week ago (with the installer which includes
xfce), and nm-applet was working fine. But today it won't start and
gives the message:
WARNING: gnome-keyring:: couldn't connect to:
/home/tom/.cache/keyring-4LJPFc/pkcs11: No such file or directory
** Message: applet n
On 05/03/2014 09:15 PM, Paul E Condon wrote:
On 20140502_1600-0700, David Christensen wrote:
But, it looks like Debian Wheezy packages are now (were then?) available:
2014-05-02 15:51:20 dpchrist@desktop ~
$ apt-cache search mate | egrep '^mate' | head
mate-applets - Various apple
On Sat, 3 May 2014 22:15:27 -0600
Paul E Condon wrote:
>
> I'm running Wheezy and using xfce4. Aptitude shows no sign of 'mate-*'
> packages mentioned above. I wonder how this could be ..., probably
> an error on my part... but what?
>
Wheezy is the stable release, so the Mate packages will
ous applets for the MATE panel (common files)
> mate-applets-dbg - Various applets for the MATE panel (debugging
> symbols)
> mate-archive-keyring - GnuPG key of the MATE repository
> mate-backgrounds - a set of backgrounds packaged with the MATE desktop
> mate-bl
mate | egrep '^mate' | head
mate-applets - Various applets for the MATE panel
mate-applets-common - Various applets for the MATE panel (common files)
mate-applets-dbg - Various applets for the MATE panel (debugging
symbols)
mate-archive-keyring - GnuPG key of the MATE repo
David Christensen writes:
> NP. MATE is unsupported on Debian.
The MATE Packaging Team will be
amazed to learn that.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas
On 05/02/2014 10:48 AM, Ralf Mardorf wrote:
sorry, we simply don't know how to help you.
NP. MATE is unsupported on Debian.
David
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https:
On Fri, 2014-05-02 at 10:38 -0700, David Christensen wrote:
[snip]
> On 05/01/2014 10:06 PM, David Christensen wrote:
> > My guess is that MATE, mplayer, and/or smplayer aren't integrated,
> > and that the above solution might work if I add MATE to the
> > gnome-keyri
erminal=False
Exec=/usr/bin/jwm
TryExec=jwm
[Window Manager]
SessionManaged=true
[rocketmouse@archlinux ~]$
Even the now "disabled" Type=Application entry worked without
side-effects.
> What happens to the Gnome keyring functionality under JWM?
Evolution does work without issues, I d
kspace/ desktop switcher
I use lightdm. If I install the jwm package, will it be integrated into
lightdm automagically?
What happens to the Gnome keyring functionality under JWM?
David
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe".
On Thu, 2014-05-01 at 22:06 -0700, David Christensen wrote:
> Any suggestions?
Don't use MATE. I've got MATE and Cinnamon installed, because I like
GNOME 2, but I neither use MATE nor Cinnamon. IMO both DEs are a PITA.
JFTR I sometimes still use Xfce4, but after testing several DEs and WMs,
I now
oving\ Pictures/01\ Tom\ Sawyer.wav
WARNING: gnome-keyring:: couldn't connect to:
/home/dpchrist/.cache/keyring-gEGbS3/pkcs11: No such file or directory
...
STFW I've run into this problem before with XFCE:
https://lists.debian.org/debian-user/2013/08/msg00935.html
Whi
Hello,
On 02/01/14 04:31, Bob Proulx wrote:
> Paul E Condon wrote:
>> Bob Proulx wrote:
>>> The path of least resistance then would seem to be to install
>>> gnome-keyring to include that file. If it existed then you wouldn't
>>> get the error any longe
Paul E Condon wrote:
> Bob Proulx wrote:
> > The path of least resistance then would seem to be to install
> > gnome-keyring to include that file. If it existed then you wouldn't
> > get the error any longer. YMMV.
>
> I installed gnome-keyring and it pulled
On 20131231_221413, Reco wrote:
> Hi.
>
> On Tue, 31 Dec 2013 09:11:26 -0700
> Paul E Condon wrote:
>
> > > Ok, now it is starting to get interesting. gnome-keyring by itself is a
> > > process which should store user credentials. gnome-keyring-pkcs11.so is
Hi.
On Tue, 31 Dec 2013 09:11:26 -0700
Paul E Condon wrote:
> > Ok, now it is starting to get interesting. gnome-keyring by itself is a
> > process which should store user credentials. gnome-keyring-pkcs11.so is
> > a library that (judging by name) is called by PolicyKit and
On Tue 31 Dec 2013 at 09:11:26 -0700, Paul E Condon wrote:
> root@big:~# aptitude why libgnome-keyring0
> i gnome-disk-utility Depends libgnome-keyring0 (>= 2.22)
>
> I think I use disk-utility when formatting new disks to extN from
> Windows whatever. Does this indicate that I must choose betw
have no idea what
> > to do because of it.
>
> Ok, now it is starting to get interesting. gnome-keyring by itself is a
> process which should store user credentials. gnome-keyring-pkcs11.so is
> a library that (judging by name) is called by PolicyKit and is linked
> to a g
p11-kit.
>
> But also, according to aptitude, p11-kit is in status 'p',
> i.e. not installed at all. So what is generating the message
> This seems to be an important clue, and I have no idea what
> to do because of it.
Ok, now it is starting to get interesting
On 20131230_150423, Bob Proulx wrote:
> Paul E Condon wrote:
> > p11-kit: couldn't load module:
> > /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
> > /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared
> > object file: No such
On 20131231_002740, Reco wrote:
> Hi.
>
> On Mon, 30 Dec 2013 12:52:41 -0700
> Paul E Condon wrote:
>
> > p11-kit: couldn't load module:
> > /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
> > /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.s
Paul E Condon wrote:
> p11-kit: couldn't load module:
> /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
> /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared
> object file: No such file or directory
>
> This message seems to be a warning,
Hi.
On Mon, 30 Dec 2013 12:52:41 -0700
Paul E Condon wrote:
> p11-kit: couldn't load module:
> /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
> /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared
> object file: No such file or directory
On Mon, 2013-12-30 at 12:52 -0700, Paul E Condon wrote:
> I do use gnome-terminal as my favorite terminal emulator so gnome
> is not truly and completely purged, but I know from what I report
> above that I don't really need the keyring part.
You should test Xfce-Terminal, AFAIR
ished. But there is an annoying leftover of Gnome
(within CUPS? or Xfce? or other?):
When I print files using CUPS, I get a message:
p11-kit: couldn't load module:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shar
Hello,
I use Debian Wheezy (|Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1
x86_64 GNU/Linux) and have try different Wine Versions (1.4.4 and 1.5.5)
but allways there is the same error:
||p11-kit: couldn't load module:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
/usr/lib/i386-
Curt wrote:
http://hongouru.blogspot.com.ar/2012/07/solved-warning-gnome-keyring-couldnt.html
I'd seen that before, but it didn't work OOTB. I needed to make a
change for XFCE:
$ diff gnome-keyring-pkcs11.desktop-orig gnome-keyring-pkcs11.desktop
127a128,142
> [Desktop
On 2013-08-23, David Christensen wrote:
>
> I see:
>
> WARNING: gnome-keyring:: couldn't connect to:
> /home/dpchrist/.cache/keyring-HEidxT/pkcs11: No such file or directory
>
> If I ssh in from a Debian 6.0.7 i386 Gnome box, there is no warning.
>
debian-user:
I have a Debian 7.1 amd64 box running XFCE.
When I invoke mplayer to convert a WMA file to a WAV file:
$ mplayer -vo null -vc dummy -af resample=44100 -ao pcm
-really-quiet -nolirc foo.wma
I see:
WARNING: gnome-keyring:: couldn't connect to:
/home/dpchrist/.
On Sun, 2013-06-23 at 13:32 -0400, Ethan Rosenberg, PhD wrote:
> Dear List -
>
> I get this message when the Keyring appears.
>
> "The password that you use to login to your computer no longer matches
> that of your login keyring"
>
> What can I do?
Dear List -
I get this message when the Keyring appears.
"The password that you use to login to your computer no longer matches
that of your login keyring"
What can I do?
Ethan
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubs
After upgrading to wheezy yesterday, I see the following when I print
something (using lp $file), or use mutt...probably will come up for
other stuff, but I have only seen it under these circumstances:
[quote=error]
WARNING: gnome-keyring:: couldn't connect to:
/home/tony/.cache/keyring-G
Hi,
I am using wheezy and I just did a safe-upgrade and now gnome ask me
all the time for the password for the keyring. It seems that the
password for the keyring is not anymore my login password. I do not
know why that happened. How could I reset the keyring and get rid of
the annoying message
Csanyi Pal writes:
> Hi,
>
> I'm trying to install on my Debian GNU/Linux SID the
> gnome-keyring-manager package:
> http://packages.debian.org/sid/gnome-keyring-manager
>
> but can't find it:
> aptitude search gnome-keyring-manager gives me no result.
> How
Hi,
I'm trying to install on my Debian GNU/Linux SID the
gnome-keyring-manager package:
http://packages.debian.org/sid/gnome-keyring-manager
but can't find it:
aptitude search gnome-keyring-manager gives me no result.
My sources.list has the following lines:
deb-src http://ftp.
On 07.02.2012 09:12, Camaleón wrote:
> Johann Spies sun.ac.za> writes:
>
>> On Mon, Feb 06, 2012 at 06:16:38PM +0200, Camaleón wrote:
>>>
>>>> The following problem is preventing me from printing:
>>>>
>>>> WARNING: gnome-keyring:: c
Johann Spies sun.ac.za> writes:
> On Mon, Feb 06, 2012 at 06:16:38PM +0200, Camaleón wrote:
> >
> > > The following problem is preventing me from printing:
> > >
> > > WARNING: gnome-keyring:: couldn't connect to:
> > >
On Mon, Feb 06, 2012 at 06:16:38PM +0200, Camaleón wrote:
>
> > The following problem is preventing me from printing:
> >
> > WARNING: gnome-keyring:: couldn't connect to:
> > /tmp/keyring-SkXSYp/pkcs11: No such file or directory
> > HP_LaserJet_P3005_15CF
On Mon, 06 Feb 2012 12:22:15 +0200, Johann Spies wrote:
> The following problem is preventing me from printing:
>
> WARNING: gnome-keyring:: couldn't connect to:
> /tmp/keyring-SkXSYp/pkcs11: No such file or directory
> HP_LaserJet_P3005_15CFFF is not ready
>
> There
On 2012-02-06 12:22:15 +0200, Johann Spies wrote:
> The following problem is preventing me from printing:
>
> WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-SkXSYp/pkcs11: No
> such file or directory
> HP_LaserJet_P3005_15CFFF is not ready
>
> There are tw
The following problem is preventing me from printing:
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-SkXSYp/pkcs11: No
such file or directory
HP_LaserJet_P3005_15CFFF is not ready
There are two (probably the same thing) bugs recorded about this:
http://bugs.debian.org/cg
On 13.12.2011 15:37, Camaleón wrote:
> On Tue, 13 Dec 2011 11:53:09 +, Anthony Campbell wrote:
>
>> There is currently a bug in gnome-keyring which keeps throwing up an
>> error message about "no socket to connec to". I don't know why I have
>> this pa
On 13 Dec 2011, Camaleón wrote:
> On Tue, 13 Dec 2011 11:53:09 +, Anthony Campbell wrote:
>
> > There is currently a bug in gnome-keyring which keeps throwing up an
> > error message about "no socket to connec to". I don't know why I have
> > this packag
On Tue, 13 Dec 2011 11:53:09 +, Anthony Campbell wrote:
> There is currently a bug in gnome-keyring which keeps throwing up an
> error message about "no socket to connec to". I don't know why I have
> this package, given that I don't use gnome (or any other des
There is currently a bug in gnome-keyring which keeps throwing up an
error message about "no socket to connec to". I don't know why I have
this package, given that I don't use gnome (or any other desktop
manager). Will anything dreadful happen if I remove it?
--
On Wed, 03 Aug 2011 19:28:46 +0200, Jerome BENOIT wrote:
>>> Have anyone submit a bug report for it ?
>>
>> To enhance the gnome-keyring doc/readme? Nope (most probably because of
>> the aforementioned lazyness) :-)
>
> I see !
>
>
> In fact, a
Hello:
On 03/08/11 19:04, Camaleón wrote:
On Wed, 03 Aug 2011 18:33:39 +0200, Jerome BENOIT wrote:
On 03/08/11 14:07, Camaleón wrote:
(...)
Anyway, I sincerely doubt the only way to widely disable
"gnome-keyring- ssh" starts by forcing the user to compile the
application with s
On Wed, 03 Aug 2011 18:33:39 +0200, Jerome BENOIT wrote:
> On 03/08/11 14:07, Camaleón wrote:
(...)
>> Anyway, I sincerely doubt the only way to widely disable
>> "gnome-keyring- ssh" starts by forcing the user to compile the
>> application with ssh keyring-a
Hello:
On 03/08/11 14:07, Camaleón wrote:
On Tue, 02 Aug 2011 21:23:27 +0200, Jerome BENOIT wrote:
On 02/08/11 19:46, Camaleón wrote:
(...)
This does not actually remove gnome-keyring, but it does allow
lower level system software to handle SSH keys, for instance.
Yes, but is it a per
On Tue, 02 Aug 2011 21:23:27 +0200, Jerome BENOIT wrote:
> On 02/08/11 19:46, Camaleón wrote:
(...)
>>>>>> This does not actually remove gnome-keyring, but it does allow
>>>>>> lower level system software to handle SSH keys, for instance.
>>>&
On 20110802_090648, Jerome BENOIT wrote:
> Hello List:
>
> On 02/08/11 00:10, Paul E Condon wrote:
> >On 20110801_230130, Jerome BENOIT wrote:
> >>
> >>
> >>
> >>Indeed, because I would suspect that a lot of packages depend on
> >&g
-keyring, but it does allow lower
level system software to handle SSH keys, for instance.
Yes, but is it a per useir set up, not a system wide set up.
Mmm, maybe not...
There is only one file located under "/etc/xdg/autostart/gnome-keyring-
ssh.desktop" and no more, I mean, there is
On Tue, 02 Aug 2011 19:22:06 +0200, Jerome BENOIT wrote:
> Hello:
>
> On 02/08/11 17:42, Camaleón wrote:
>> On Tue, 02 Aug 2011 09:06:48 +0200, Jerome BENOIT wrote:
>>
>>> On 02/08/11 00:10, Paul E Condon wrote:
>>
>> (...)
>>
>>>> Th
Hello:
On 02/08/11 17:42, Camaleón wrote:
On Tue, 02 Aug 2011 09:06:48 +0200, Jerome BENOIT wrote:
On 02/08/11 00:10, Paul E Condon wrote:
(...)
This does not actually remove gnome-keyring, but it does allow lower
level system software to handle SSH keys, for instance.
Yes, but is it a
On Tue, 02 Aug 2011 09:06:48 +0200, Jerome BENOIT wrote:
> On 02/08/11 00:10, Paul E Condon wrote:
(...)
>> This does not actually remove gnome-keyring, but it does allow lower
>> level system software to handle SSH keys, for instance.
>
> Yes, but is it a per user set
Hello List:
On 02/08/11 00:10, Paul E Condon wrote:
On 20110801_230130, Jerome BENOIT wrote:
Indeed, because I would suspect that a lot of packages depend on gnome-keyring
as I could read on Google. But as only a `minimal' Gnome is actually
installed on my box, it appeared that no pa
On 20110801_230130, Jerome BENOIT wrote:
>
>
>
> Indeed, because I would suspect that a lot of packages depend on gnome-keyring
> as I could read on Google. But as only a `minimal' Gnome is actually
> installed on my box, it appeared that no package depends on it.
> OT
e to install what you need and to not install what you do
not need or do not want. Really!
Yes, but Jerome was not complaining about a "bloated" system but how to
solve a specific problem he had with gnome-keyring and how to disable it.
He read the docs and did not found a convenient
ry well. But that isn't Debian. In Debian it is
> perfectly fine to install what you need and to not install what you do
> not need or do not want. Really!
Yes, but Jerome was not complaining about a "bloated" system but how to
solve a specific problem he had with gnome-keyri
e and it annoys the pig."
Unfortunately sometimes that is true of software projects too.
> Anyway, "gnome-keyring" is part of the GNOME security stack and password
> management and I find it very convenient for this task, but that's of
> course up to each user.
If
have removed/renamed
>>>
>>> If I remember well, this causes trouble.
>
> I meant removing the `/etc/xdg/autostart/gnome-keyring-ssh.desktop'
Remove or better yet, move it to another place. Is just a ".desktop" file
to be run system wide, so if you don'
1 - 100 of 185 matches
Mail list logo
