Displaying 3 results from an estimated 3 matches for "18t02".
Did you mean:
1802
2012 Feb 01
1
[PATCH] hivexml
...all --
>
> e689a4 02 eb8288c 7937 46 5
>
> The 02 (^B) is an invalid XML character in the 1.0 spec, and was
> causing xmllint to fail in the following manner
>
> [hivex-1.3.3-orig]# xmllint xmlout.orig
>
> xmlout.orig:2: parser error : PCDATA invalid Char value 2
> 18T02:23:42Z</mtime><value type="string-list" key="Autorecover MOFs"><string>??
> ^
>
>
> After the patch, ...with all the surrounding stuff cut away
> [hivex-1.3.3-new]#...
2020 Jul 16
3
Authentication with trusted credentials
On 16/07/2020 22:13, Yakov Revyakin wrote:
> Thank you! I have food for tomorrow. Now I only want to voice some of
> my considerations.
>
> Imagine that a domain had no trusts. At this time a PC became a member
> of this domain.
> After some time DC made trust with another domain. In this case
> existing members don't consider?any extra configuration like adding
>
2020 Jul 20
3
Authentication with trusted credentials
...kend. SSH session is created.
>
> # trusting user - authentication successful
>
> Kerberos: TGS-REQ test01 at SVITLA3.ROOM from ipv4:10.0.0.12:50510 for
> UC-SM18$@SVITLA3.ROOM
> Kerberos: TGS-REQ authtime: 2020-07-17T16:47:35 starttime:
> 2020-07-17T16:47:35 endtime: 2020-07-18T02:47:35 renew till: unset
>
> # trusted user - cross-realm authentication successful
>
> Kerberos: TGS-REQ jake at APEX.CORP from ipv4:10.0.0.12:52437 for
> UC-SM18$@SVITLA3.ROOM
> Kerberos: Client not found in database: no such entry found in hdb
> Kerberos: cross-realm APEX.C...