Displaying 20 results from an estimated 2000 matches similar to: "Unloking gnome keyring on login"
2011 Dec 26
2
gnome keyring
I am having an issue I have not ran into before...
I set my box to "auto" login by changing the file:
more /etc/gdm/custom.conf
# GDM configuration storage
[daemon]
AutomaticLoginEnable=true
AutomaticLogin=silentm
TimedLoginEnable=true
TimedLogin=silentm
TimedLoginDelay=0
[security]
[xdmcp]
[greeter]
[chooser]
[debug]
It does auto login - however then when I try to VNC into
2009 Mar 09
1
need help with keyring
I should mention that I'm a total newbie with keyrings! I tried
searching for help sites - found 1, but I still have a problem. If there
is a website (or sites) that explain this, please post it (them)!
Ok, so I have a laptop with wifi, running CentOS 5.2. When I boot it, it
finds the nearby wifi signals, and tries to connect to mine. To do this,
it puts up a window to get my default
2014 Feb 21
2
Re: [PATCH 2/2] builder: use a disposable GPG keyring for every Sigchecker
On Fri, Feb 21, 2014 at 01:50:30PM +0100, Pino Toscano wrote:
> On Friday 21 February 2014 11:10:54 Richard W.M. Jones wrote:
> > On Thu, Feb 20, 2014 at 11:53:17AM +0100, Pino Toscano wrote:
> > > Create a temporary directory and tell gpg to use it as homedir, so
> > > imported keys do not get into the user's keyring. This also avoid
> > > importing the
2009 Jul 07
1
Installing debian-backports-keyring
I want to install debian-backports-keyring on puppet clients. However, I
can''t install it because the client doesn''t already have the key:
--------------------------------------------------------------------------------
err: //Node[basenode]/tclbase/Package[debian-backports-keyring]/ensure:
change from purged to present failed: Execution of ''/usr/bin/aptitude -y
-o
2014 Feb 21
2
Re: [PATCH 2/2] builder: use a disposable GPG keyring for every Sigchecker
On Thu, Feb 20, 2014 at 11:53:17AM +0100, Pino Toscano wrote:
> Create a temporary directory and tell gpg to use it as homedir, so
> imported keys do not get into the user's keyring. This also avoid
> importing the default key when a different one is needed to check the
> signature.
>
> The only exception is when a non-default fingerprint is used: in this
> case, that key
2018 Jan 05
3
Using keyring on tinc
Hi all!
Is there any way to make tinc use keys from a keyring or similar?
I'm trying to find a way to manage multiple server, making it easier to
register a new user to the network.
Thanks!
--
Martin IƱaki Malerba
inakimmalerba at gmail.com
inaki at satellogic.com
2012 Oct 04
0
CEBA-2012:1334 CentOS 6 gnome-keyring Update
CentOS Errata and Bugfix Advisory 2012:1334
Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1334.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
834ad2fc6f3d74700c5fc601b4298e7383b8eddd8e4e1aff7d6f3144361bfa76 gnome-keyring-2.28.2-8.el6_3.i686.rpm
2009 Mar 18
0
wifi and the default keyring
Hello.
I'm using my laptop (an Acer Aspire 3680, with built-in Atheros wifi). I
installed 5.2 on it, and it's working nicely. But, I have an issue with
the keyring. I should mention that this is my *first* experience with
keyrings.
When I set up the wifi, it stated basically that "nm-applet wants to
access the default keyring, but it's locked. Enter password." So I did.
2010 Jan 21
0
PAM and GNOME keyring
Hi everybody,
I have a CentOS 5.4 server I need to se-up as Subversion server. On the server GNOME keyring has been installed and the integration with Subversion works fine: I'm asked for the keyring password the first time and that's it.
I am now trying to set it up so that after login the default keyring is unlocked. This way I won't be asked for the keyring password ever. I have
2020 Mar 21
0
gnome-keyring auto locking
Hey all,
I am preparing some workstations with C8/GNOME here and wonder if there
is a smart way to automatically lock the keyring after some defined time
(e.g 1800 seconds). The net suggests killing the gnome-keyring-daemon
process - not the smartest way. I can manually lock the keyring with
seahorse but this way doesn't scale very well :-)
Any hints?
Leon
2012 Sep 20
1
[PATCH 1/2] ./run: Make sure that the temporary directory exists so test scripts can produce output files
---
run.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/run.in b/run.in
index ed4971b..548ac20 100644
--- a/run.in
+++ b/run.in
@@ -51,6 +51,7 @@ b=@abs_builddir@
#
# chcon --reference=/tmp tmp
export TMPDIR="$b/tmp"
+mkdir -p "$b/tmp"
# Set local environment relative to this script.
export LIBGUESTFS_PATH="$b/appliance"
--
1.7.10.4
2016 Apr 21
2
Winbind idmap question
All DC are running same Samba version : 4.4.2. All DC are hosted on same
Centos 7.
On broken server(s):
wbinfo -i mdufresne
failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND
Could not get info for user mdufresne
On working servers:
wbinfo -i mdufresne
AD.DOMAIN\mdufresne:*:12104:100:Mathias Dufresne
(TEMP):/home/AD.DGFIP/mdufresne:/bin/false
The smb.conf is:
2016 Nov 20
1
Skype for Centos Desktop
On 11/17/16 22:23, geo wrote:
>
>
> On 11/17/2016 07:47 PM, Peter wrote:
>> On 18/11/16 11:01, Liam O'Toole wrote:
>>> On 2016-11-17, Rodrigo Pichi?ual Norin
>>> <rodrigo.pichinual at gmail.com> wrote:
>>>> Hi all.
>>>>
>>>> I search info in the web about how to install skype on centos 6.5, but
>>>> just
2008 Nov 07
2
Problem building kernel (gpg problem) - 2.6.18-92.1.17
With new kernel, appeared some problems with build proccess here.
After many minutes waiting for rpmbuild were over, a gpg problem appears!!:
...
scripts/modsign/mod-extract.c:311: warning: format '%lx' expects type
'long unsigned int', but argument 3 has type 'Elf64_Xword'
+ KEYFLAGS='--no-default-keyring --homedir ..'
+ KEYFLAGS='--no-default-keyring
2013 Apr 16
2
[Bug 2093] New: don't forward authentication for the whole keyring
https://bugzilla.mindrot.org/show_bug.cgi?id=2093
Bug ID: 2093
Summary: don't forward authentication for the whole keyring
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.5p1
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component:
2015 Jun 11
2
NetworkManager / wireless on latest Centos7 installs
----- Oorspronkelijk bericht -----
Van: "johan vermeulen7" <johan.vermeulen7 at telenet.be>
Aan: "CentOS mailing list" <centos at centos.org>
Verzonden: Dinsdag 9 juni 2015 18:23:58
Onderwerp: Re: [CentOS] NetworkManager / wireless on latest Centos7 installs
----- Oorspronkelijk bericht -----
Van: "m roth" <m.roth at 5-cent.us>
Aan: "CentOS
2013 Jul 28
2
What does this Centos Network Manager error message mean
Here is the error message:
http://i41.tinypic.com/2zz71bp.png
Wireless Network Authentication Required
Unlock Keyring: The application 'NetworkManager Applet'
(/usr/bin/nm-applet) wants access to the default keyring,
but it is locked.
The funny thing is,
(a) I've never seen this message before (in a year of using CentOS)
(b) I am the system administrator but it won't take the
2020 Jul 29
1
kerberos ticket on login problem
On 7/28/2020 4:11 PM, Jason Keltz wrote:
>
> On 7/28/2020 3:59 PM, Jason Keltz via samba wrote:
>> I'm experimenting with smb + winbind.
>>
>> My host is joined to AD and I can login to my host fine using my AD
>> credentials via SSH.?? The only issue is that I don't get a Kerberos
>> ticket generated.
>>
>> In
2014 Jul 01
2
remote yum update aborted with session closing - won't boot
I was upgrading a system remotely from Centos 6.3 to 6.5 via VNC. Now
the system will not boot. Or at least without bringing up the console
and switching to the older kernel. The last messages I see in
/var/log/messages are:
Jul 1 14:53:51 rigel yum[3220]: Updated: scl-utils-20120927-8.el6.i686
Jul 1 14:53:53 rigel gnome-keyring-daemon[2710]: dbus failure
unregistering from session:
2024 Oct 18
1
Confusion using "ssh-add -D" and then "ssh-add -l"
Hi,
On 18.10.24 13:50, Chris Green wrote:
> chris$ ps -fe | grep ssh-agent
> chris 2463 1530 0 12:33 ? 00:00:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh
>
> but:-
>
> chris$ env | grep SSH
> SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
>
> So SSH_AUTH_SOCK doesn't appear to be the socket that ssh-agent thinks
> it