search for: kt_entri

Displaying 5 results from an estimated 5 matches for "kt_entri".

Did you mean: kt_entry
2016 Jun 07
2
Segfault when trying to generate keytab with samba 4.2.10
Of course i can! Hereby the backtrace with symbols: Program received signal SIGSEGV, Segmentation fault. free_PrincipalName (data=data at entry=0x45) at default/source4/heimdal/lib/asn1/asn1_krb5_asn1.c:961 961 default/source4/heimdal/lib/asn1/asn1_krb5_asn1.c: No such file or directory. (gdb) bt #0 free_PrincipalName (data=data at entry=0x45) at
2016 Jun 08
0
Segfault when trying to generate keytab with samba 4.2.10
On Tue, Jun 07, 2016 at 06:59:56AM +0000, Lars Maes wrote: > Of course i can! > > Hereby the backtrace with symbols: > > Program received signal SIGSEGV, Segmentation fault. > free_PrincipalName (data=data at entry=0x45) at default/source4/heimdal/lib/asn1/asn1_krb5_asn1.c:961 > 961 default/source4/heimdal/lib/asn1/asn1_krb5_asn1.c: No such file or directory. > (gdb)
2016 Jun 06
6
Segfault when trying to generate keytab with samba 4.2.10
Hi All, Whe tryin to use: net ads keytab create, I get the following segfault: Program received signal SIGSEGV, Segmentation fault. 0x00007fffef9d3f69 in free_PrincipalName () from /usr/lib/x86_64-linux-gnu/samba/libasn1-samba4.so.8 I am using samba 4.2.10 from Debian. Deb8u3 package Anyone knows how to fix this?
2006 Jul 13
2
Kerberos Keytab Code Update in 3.0.23
First thing - I'd like to say a big "THANK YOU" to the developers. I just upgraded to samba-3.0.23 and I've noticed an alarming issue with respect to my configuration. I've been using the built-in keytab management and it looks like the updated code no longer creates the userPrincipal in Active Directory. Whether this is an issue for others or not, it would be nice to have
2018 Jun 25
2
Samba 4.7.1 Generating Core Dumps
Hi, We are having issues with our samba server running on CentOS 7. It's generating core dumps and dumping them in the / (root filesystem) directory in the form of core.##### where the # is a series of numbers. Snippets of log files and some troubleshooting commands are below. Hope someone can have a look and see if I should file this as a bug, as there were similar posts in the samba