Hide Forgot
Description of problem: Nautilus ignores bad password entered for Windows share if Sea Horse server string is already saved and has a good password. Version-Release number of selected component (if applicable): nautilus-3.2.1-2.fc16.x86_64 seahorse-3.2.1-2.fc16.x86_64 samba-client-3.6.1-75.fc16.x86_64 dbus-1.4.10-3.fc16.x86_64 kernel-3.1.5-1.fc16.x86_64 How reproducible: Always Steps to Reproduce: 1) Verify no server connection strings are saved in Sea Horse 2) With Nautilus “Connect to Server…” correctly populate Windows Share dialog boxes 3) Check on “Remember this password”, click Connect, connection will connect as expected 4) With Nautilus ‘eject’ the new share 5) Verify server connection string and password in Sea Horse, everything is as expected 6) With Nautilus “Connect to Server…” correctly populate Windows Share dialog box but leave the password field blank OR supply a bad password. Both cases produce the same successful result. 7) Click Connect, connection is made. Actual results: Expected results: Steps 1-6 above are the same Step 7, Click Connect, connection should fail. Additional info: If however Sea Horse has a bad password saved (which I manually made bad at Step 5), the connection attempt will first use the Sea Horse password and fail then use the Nautilus supplied password as evident in the Samba server logs. [2011/12/13 17:17:02.588978, 0] auth/auth_domain.c:327() domain_client_validate: unable to validate password for user dudek in domain MYDOMAIN to Domain controller MYDC. Error was NT_STATUS_WRONG_PASSWORD. [2011/12/13 17:17:02.674658, 1] smbd/service.c:1070() black (129.82.216.50) connect to service myshare initially as user dudek (uid=12345, gid=100) (pid 29233)
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.