I cannot authenticate to a DFS share without entering my password manually (which is not acceptable since I actually need to script a download to run unattended). Kerberos auth fails because of https://bugzilla.samba.org/show_bug.cgi?id=10288 while NTLM auth fails because of https://bugzilla.samba.org/show_bug.cgi?id=10279
samba-4.1.12-4.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/samba-4.1.12-4.fc20
I'm a litle confused because the commit that marks this as fixed doesn't actually include any *patches*. Just a note in the specfile that it's fixed. It isn't. It still asks me for my password when I use '-C', still uses the wrong SPN so Kerberos still fails, and still doesn't do SPNEGO correctly so GSS-NTLMSSP doesn't save the day. [dwoodhou@i7 f20]$ wbinfo -K dwoodhou Enter dwoodhou's password: plaintext kerberos password authentication for [dwoodhou] succeeded (requesting cctype: FILE) credentials were put in: FILE:/tmp/krb5cc_500 [dwoodhou@i7 f20]$ smbclient -C //amr.corp.intel.com/iss Enter dwoodhou's password: [dwoodhou@i7 f20]$ smbclient -k //amr.corp.intel.com/iss ads_krb5_mk_req: smb_krb5_get_credentials failed for cifs/amr.corp.intel.com.INTEL.COM (Server not found in Kerberos database) cli_session_setup_kerberos: spnego_gen_krb5_negTokenInit failed: Server not found in Kerberos database session setup failed: NT_STATUS_UNSUCCESSFUL [dwoodhou@i7 f20]$ kvno -S cifs amr.corp.intel.com cifs/orsamr403.amr.corp.intel.com.INTEL.COM: kvno = 12
Package samba-4.1.12-4.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing samba-4.1.12-4.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-11563/samba-4.1.12-4.fc20 then log in and leave karma (feedback).
samba-4.1.12-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
This wasn't fixed in 4.1.12 and I don't think any patches exist *anywhere* yet which address any of the three issues.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.