Displaying 6 results from an estimated 6 matches for "smb_krb5_open_keytab".
2009 Feb 16
1
samba-3.2.8 - KRB5_KT_UNKNOWN_TYPE;
...;use kerberos keytab = yes" in smb.conf is set with samba-3.2.8 and
the environment variable KRB5_KTNAME is not set with the value using
prefix "FILE:" or the default_keytab in /etc/krb5.conf is set without
the prefix i.e.
default_keytab_name = /etc/v5srvtab
then the function smb_krb5_open_keytab() returns KRB5_KT_UNKNOWN_TYPE.
If smb_krb5_open_keytab with a filename "/etc/v5srvtab" it would work
fine, however if the "default" keytab is used the expectation is that it
must have a prefix "FILE:" or "WRFILE:".
Is this the correct logic? It appear...
2016 Dec 01
2
cannot access to linux share from windows
...server from Fedora 24 to 25 recently.
And I cannot access linux shares located on the F25 client from a windows
desktop.
I get these messages:
[2016/12/01 11:42:19.218759, 1]
../source3/librpc/crypto/gse_krb5.c:534(fill_mem_keytab_from_dedicated_keytab)
../source3/librpc/crypto/gse_krb5.c:534: smb_krb5_open_keytab failed (Key
table name malformed)
[2016/12/01 11:42:19.218800, 1]
../source3/librpc/crypto/gse_krb5.c:627(gse_krb5_get_server_keytab)
../source3/librpc/crypto/gse_krb5.c:627: Error! Unable to set mem keytab
- -1765328205
[2016/12/01 11:42:19.218823, 1]
../auth/gensec/gensec_start.c:698(gensec_s...
2018 May 11
2
smb_krb5_open_keytab failed (Key table name malformed)
...nt I get these
errors on the Samba server:
========== 8< ==========
May 11 17:10:30 fileserv smbd[3634]: [2018/05/11 17:10:30.181182, 1]
../source3/librpc/crypto/gse_krb5.c:542(fill_mem_keytab_from_dedicated_keytab)
May 11 17:10:30 fileserv smbd[3634]:
../source3/librpc/crypto/gse_krb5.c:542: smb_krb5_open_keytab failed (Key
table name malformed)
May 11 17:10:30 fileserv smbd[3634]: [2018/05/11 17:10:30.183815, 1]
../source3/librpc/crypto/gse_krb5.c:635(gse_krb5_get_server_keytab)
May 11 17:10:30 fileserv smbd[3634]:
../source3/librpc/crypto/gse_krb5.c:635: Error! Unable to set mem keytab -
-1765328205
Ma...
2016 Dec 01
2
cannot access to linux share from windows
...ated on the F25 client
> > from a windows desktop.
> >
> > I get these messages:
> >
> > [2016/12/01 11:42:19.218759, 1]
> > ../source3/librpc/crypto/gse_krb5.c:534(fill_mem_keytab_
> from_dedicated_keytab)
> > ../source3/librpc/crypto/gse_krb5.c:534: smb_krb5_open_keytab
> > failed (Key table name malformed)
> > [2016/12/01 11:42:19.218800, 1]
> > ../source3/librpc/crypto/gse_krb5.c:627(gse_krb5_get_server_keytab)
> > ../source3/librpc/crypto/gse_krb5.c:627: Error! Unable to set mem
> > keytab
> > - -1765328205
> > [2016...
2016 Dec 01
0
cannot access to linux share from windows
...y. And I cannot access linux shares located on the F25 client
> from a windows desktop.
>
> I get these messages:
>
> [2016/12/01 11:42:19.218759, 1]
> ../source3/librpc/crypto/gse_krb5.c:534(fill_mem_keytab_from_dedicated_keytab)
> ../source3/librpc/crypto/gse_krb5.c:534: smb_krb5_open_keytab
> failed (Key table name malformed)
> [2016/12/01 11:42:19.218800, 1]
> ../source3/librpc/crypto/gse_krb5.c:627(gse_krb5_get_server_keytab)
> ../source3/librpc/crypto/gse_krb5.c:627: Error! Unable to set mem
> keytab
> - -1765328205
> [2016/12/01 11:42:19.218823, 1]
> .....
2016 Dec 01
0
cannot access to linux share from windows
...> from a windows desktop.
>> >
>> > I get these messages:
>> >
>> > [2016/12/01 11:42:19.218759, 1]
>> > ../source3/librpc/crypto/gse_krb5.c:534(fill_mem_keytab_from
>> _dedicated_keytab)
>> > ../source3/librpc/crypto/gse_krb5.c:534: smb_krb5_open_keytab
>> > failed (Key table name malformed)
>> > [2016/12/01 11:42:19.218800, 1]
>> > ../source3/librpc/crypto/gse_krb5.c:627(gse_krb5_get_server_keytab)
>> > ../source3/librpc/crypto/gse_krb5.c:627: Error! Unable to set mem
>> > keytab
>> > - -17...