Summary: | Konqueror's SMB:// doesn't authenticate with MacOSX | ||
---|---|---|---|
Product: | [Unmaintained] kio | Reporter: | fleona |
Component: | smb | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | adawit |
Priority: | NOR | ||
Version: | 3.2.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
fleona
2004-05-17 20:46:09 UTC
it will always try anonymous login and if that succeeds, it won't give an error. If you want to login, use smb://username@machine - or specify a default user name in the kcontrol module. What happens if you access your mac from your windows? When accesing the mac from windows i get a login/password request as expected. I fill it and then i get my files. I will try doing smb://username:password@machine and report back, but as an user i expect user friendlyness (getting the dialog) i had to do smb://machine/share in order to be asked the password. Macs by default only share the home directory of the user and somehow konqueror cannot get a password dialog to see what shares are available. smbclient will NOT show the share unless i pass the password. So i guess konqueror is showing blank since it isn't using one. Now, what events trigger if a password is asked? Perhaps konqueror tries by default an anonymous login and since the mac doesn't reject it (but shows nothing) then this is what it's happening. So, maybe not a bug. Should konqueror always ask for a password? No, it shouldn't. I kind of would like to know what windows and MacOS talk, do you have another computer on the same lan you could use to do a tcpdump (please do not attach it here, but send it to me - it might contain your password in clear text) I dont have another machine, but the mac comes with tcpdump, just tell me what i need to do with it and i will email it to you "tcpdump -w file" should be enough KDE 3 is no longer maintained. Feel free to reopen if this is still an issue with the latest version of KDE 4. |