similar to: provision broken on linux

Hi Trever, things improved after resetting user/machine passwords, however only the session key is using aes256 now, the ticket itself is still arcfour: root at ubuntu1:~# kinit user09999 user09999 at S4DOM.TEST's Password: root at ubuntu1:~# klist -v Credentials cache: FILE:/tmp/krb5cc_0 Principal: user09999 at S4DOM.TEST Cache version: 4 Server: krbtgt/S4DOM.TEST at

Hi again, the attached patch (re-)enables parts of lua's liolib.c, especially io.write() for formatted output (similar to printf() ): Example: -- define printf() function printf = function(s,...) return io.write(s:format(...)) end -- function printf("Hallo, this is hex %04x\n", 64321) Bye, Marcel -------------- next part -------------- A non-text

Hi! I've been working with pxelinux for quite some time now, and I'd like to use PXE and a simple kind of selection menu (like syslinux does). But I couldn't get it to work. I can enter several "label" sections to my pxelinux.cfg/<something> but it'll never ask, just boot the first/default one ... Is this currently supported at all? Or did I miss something?

On 08/19/2015 12:02 AM, Ritter, Marcel (RRZE) wrote: > Hi Trever, > > things improved after resetting user/machine passwords, however only the session key is using aes256 now, the ticket itself is still arcfour: > > root at ubuntu1:~# kinit user09999 > user09999 at S4DOM.TEST's Password: > root at ubuntu1:~# klist -v > Credentials cache: FILE:/tmp/krb5cc_0 >

Hi, I just played with the new GPL PV driver release a bit, and there''s a problem when running the included install.bat from a read-only device (pvdriver.zip was extracted, and "burned" to virtual CD) Cause of this problem: During installation dpinst.exe is copied to the matching driver directory (located on the install media) and executed there. Unfortunately this fails

> Marcel Ritter wrote: > > > > The good thing about it: The PXE code removal seems to work now ... > > > > But I'm not quite sure about the syntax - is the following right? > > > > label undi > > kernel memdisk keeppxe > > append initrd=UNDITest/dosundi.1 > > > > The documentation only says: > > > > ... option

Try this on your samba DC. amba-tool spn list PCNAME$ You should see something like: PCNAME$$ User CN=PCNAME,CN=Computers,DC=internal,DC=domain,DC=tld has the following servicePrincipalName: HOST/PCNAME HOST/PCNAME.internal.domain.tld nfs/PCNAME.internal.domain.tld nfs/PCNAME.internal.domain.tld at YOUR_REALM can you confirm this for both your servers which

Ok, i clarify a bit more. \\servername.internal.domain.tld\users2\%username% is used in my AD for the home folder of the users. %username% translates to the username. I tried 2 setups now, windows acl base setup and posix based setup. Both fail for me. THE SERVER with the shares ( and is nfs server) The samba/windows part. ( postix rights setup ) On the server this is /home/samba/users2

Hi! I've spent the last days trying to get PXE working (with all the nice stuff that's in the specification - doesn't work :-( ) So I tried the new 1.75 with the Intel DOSUndi Bootdisk (which should verify that everything works correctly) but it does no longer work with syslinux-1.75! 1.74 is fine - so I guess something is broken here ... Please have a look at it - and let me know

Hi, the first attached patch extends the argument parsing code to allow (shell like) spaces. A config like LABEL BIOSupdate KERNEL dmiselect.c32 APPEND "ESPRIMO P5925" "memdisk initrd=/dos/FSC-E5925.img raw" will result in args[]: ESPRIMO P5925 memdisk initrd=/dos/FSC-E5925.img raw instead of (current code): "ESPRIMO P5925" "memdisk

Hi, I’ve been running a samba 4 DC for quite some time now, and while testing some kerberos related stuff, I noticed that all kerberos tickets I can get from the DC are of encryption type ?arcfour-hmac-md5“: # kinit testuser1 testuser1 at S4DOM.TEST's Password: # klist -v Credentials cache: FILE:/tmp/krb5cc_0 Ticket etype: arcfour-hmac-md5, kvno 1 I can create keytabs containing

Hai marcel, Im using nfsv4 kerberos based host/client. This is the line of the cat /proc/mounts nfs4 rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=192.168.xx.xx,local_lock=none,addr=192.168.xxx.xxx 0 0 fstab only contains : nfs4 sec=krb5 Yes, i did see the nfs4-acl-tools, seen that, hoped that helped a bit, But i did

hai, The servers have "A and PTR" records? You have for both server these UPNs. nfs/${SETFQDN} ${SETHOSTNAME_CAPS}$ nfs/${SETFQDN}@${SAMBA_KERBEROS_REALM} ${SETHOSTNAME_CAPS}$ on the samba side the nfs spn is in you keytab file? and if your brave, read, * dont run it, since i did not test this with windows servers.

Hi again, I just started to debug things on the samba4 side: When trying to mount the Windows NFS share, I get the following error on the samba4 dc (just grepping for nfs in the logs): auth_check_password_send: Checking password for unmapped user [S5DOM.TEST]\[nfs/nfsclient.mydom.test]@[] map_user_info_cracknames: Mapping user [MYDOM.TEST]\[nfs/nfsclient.mydom.test] from workstation []

After thinking a bit of the multi-file support in 3.31-pre1, and considering a few users' feedback on the subject, I have made a couple of changes: 1. The dummy filename ~ can be used to mean "the main config file". 2. There is a MENU INCLUDE directive now. -hpa

Hi, during my tests to use Samba4 as a kdc for kerberized NFS, I found a bug in the KDC code, when generating a principal without pac (e.g. with msktutil and option --no-pac), that causes Samba4 to crash: Running the following command on one of the client machines msktutil -c --upn nfs/testa.linex.org -h testa.linex.org --computer-name testa-service-nfs --server s4-dc1.linex.org --no-pac

> Marcel Ritter wrote: > > > > I had a stupid config error in my pxelinux.cfg files - my fault. > > Works fine now. > > > > But there's still one question: > > > > Is it possible to use shortcut keys to load a certain image? > > > > Something like: > > > > Press 1 for option one > > Press 2 for option two > >

Hi, I know there've been some workarounds on this topic, however I'm missing the reason for winbind to behave differently on a DC and on a member server (I also had to work around that problem and I'd really like it fixed). If there's a technical reason for it, it'd be nice to know about it. If there isn't, then it's just a bug that should be fixed. Could someone of

On 10/07/15 08:05, Ritter, Marcel (RRZE) wrote: > Hi, > > I know there've been some workarounds on this topic, however I'm missing > the reason for winbind to behave differently on a DC and on a member > server (I also had to work around that problem and I'd really like it fixed). The reason is a bit historical, originally samba4, when running as an AD DC, used the

On 08/18/2015 02:28 PM, Ritter, Marcel (RRZE) wrote: > Hi, > > I’ve been running a samba 4 DC for quite some time now, and while testing some kerberos related stuff, I noticed that all kerberos tickets I can get from the DC are of encryption type ?arcfour-hmac-md5“: > > # kinit testuser1 > testuser1 at S4DOM.TEST's Password: > > # klist -v > Credentials cache: