ake which looked odd. We are trying to
investigate further in this direction.
bye,
Sumit
>
>
>
> Awesome.
>
>
>
> Todd
>
>
>
>
>
>
>
> -Original Message-
> From: James Ralston
> Sent: Thursday, February 13, 2020 3:50 PM
they are logged as unsigned whether they use it or not.
Awesome.
Todd
-Original Message-
From: James Ralston
Sent: Thursday, February 13, 2020 3:50 PM
To: End-user discussions about the System Security Services Daemon
Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
On Thu
On Thu, Feb 13, 2020 at 10:24 AM Mote, Todd wrote:
> Only using GSSAPI causes the unsigned SASL event.
>
> root@anti-test:~ # ldapsearch -H ldap://dc01a.ADTEST.domain.com -Y GSSAPI -b
> '' -s base
> SASL/GSSAPI authentication started
> SASL username: ANTI-TEST$@ADTEST.domain.com
> SASL SSF: 256
I just installed a AD site, and will be deploying Linux machines as well.
I would personally be afraid of ANY patch coming from Microsoft that after
being applied, would put your LINUX services into question afterwards.
I am in a NIST/PCI compliance location, and I do not mix the two as a
ions about the System Security Services Daemon
>
> Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
>
> On Thu, Feb 13, 2020 at 03:10:31PM +, Mote, Todd wrote:
> > Tangentially, GSS-SPNEGO isn't available on RHEL 6, correct?
>
> Hi,
>
> not not availabl
, 2020 9:17 AM
To: End-user discussions about the System Security Services Daemon
Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
On Thu, Feb 13, 2020 at 03:10:31PM +, Mote, Todd wrote:
> Tangentially, GSS-SPNEGO isn't available on RHEL 6, correct?
Hi,
not not available in RHEL-6, i
Bose
Sent: Thursday, February 13, 2020 9:16 AM
To: End-user discussions about the System Security Services Daemon
Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
On Thu, Feb 13, 2020 at 03:02:59PM +, Mote, Todd wrote:
> ldapsearch -H ldap://ad-server.ADTEST.domain.com -Y GSSAPI -b ''
> Sent: Thursday, February 13, 2020 8:51 AM
> To: End-user discussions about the System Security Services Daemon
>
> Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
>
> On Thu, Feb 13, 2020 at 01:42:33PM +, Mote, Todd wrote:
> > I'll work on getti
> Binding Type:
> 0
>
> -Original Message-
> From: Sumit Bose
> Sent: Thursday, February 13, 2020 8:51 AM
> To: End-user discussions about the System Security Services Daemon
>
> Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
>
> On Thu, Fe
Tangentially, GSS-SPNEGO isn't available on RHEL 6, correct?
Todd
-Original Message-
From: Sumit Bose
Sent: Thursday, February 13, 2020 8:51 AM
To: End-user discussions about the System Security Services Daemon
Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
On Thu, Feb 13, 2020
discussions about the System Security Services Daemon
Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
On Thu, Feb 13, 2020 at 01:42:33PM +, Mote, Todd wrote:
> I'll work on getting that today. This is what I know so far.
>
>
>
> Test system updated through our Satell
needed
>
> * Sending netlogon pings to domain controller: cldap://xxx.xxx.xxx.xxx
>
> * Received NetLogon info from: dc01a.adtest.domain.com
>
> * Checking RestrictedKrbHost/anti-test.adtest.domain.com
>
> * Added RestrictedKrbHost/anti-test.adtest.domain.com
>
&g
lists.fedorahosted.org<mailto:sssd-users@lists.fedorahosted.org>
> Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
>
> On Thu, Feb 06, 2020 at 03:05:13PM +, Ondrej Valousek wrote:
> > did you try refreshing the machine password in AD?Looks like it's too old.
> &g
connection attempt of adcli which causes the issue?
bye,
Sumit
>
> Todd
>
> -Original Message-
> From: Sumit Bose
> Sent: Thursday, February 6, 2020 10:18 AM
> To: sssd-users@lists.fedorahosted.org
> Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
>
> On Thu
___
> From: David David
> Sent: Thursday, February 6, 2020 5:20 PM
> To: sssd-users@lists.fedorahosted.org
> Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
>
> Ahoj Ondro,
> well my knowledge about sssd is limited, but I would say that the daemon did
> it instead me.
@lists.fedorahosted.org
Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
On Thu, Feb 06, 2020 at 03:05:13PM +, Ondrej Valousek wrote:
> did you try refreshing the machine password in AD?Looks like it's too old.
> O.
>
> From: David David
> Sent: Thursday, F
into it as I'm not sure either.
Ondra
From: David David
Sent: Thursday, February 6, 2020 5:20 PM
To: sssd-users@lists.fedorahosted.org
Subject: [SSSD-users] Re: sssd 1.16.4. ADV190023.
Ahoj Ondro,
well my knowledge about sssd is limited, but I would say that the daemon did
Ahoj Ondro,
well my knowledge about sssd is limited, but I would say that the daemon did it
instead me. See the middle message:
Task [AD machine account password renewal]: finished successfully
This task is by default scheduled after restart of sssd service always.
However, I probably found
On Thu, Feb 06, 2020 at 03:05:13PM +, Ondrej Valousek wrote:
> did you try refreshing the machine password in AD?Looks like it's too old.
> O.
>
> From: David David
> Sent: Thursday, February 6, 2020 12:09 PM
> To: sssd-users@lists.fedorahosted.org
> Subject:
did you try refreshing the machine password in AD?Looks like it's too old.
O.
From: David David
Sent: Thursday, February 6, 2020 12:09 PM
To: sssd-users@lists.fedorahosted.org
Subject: [SSSD-users] sssd 1.16.4. ADV190023.
Hello,
i guess that you probably heard
20 matches
Mail list logo
