SANDRO NOEL  I was using the system prompted dialogue before, and you complained about it.

There is not much many ways for me to control the system dialogue from the API that is available.

If you know of a way to do it, you should let me know.

Thanks.  
(Version 1.9.2)

WUFFE  Well I'm no expert in your BM codebase - but I guess that you along with your own username/password dialog implementation must have changed something "else" around the handling of empty passwords (ok admitted this is unclear).

What I saw with BM 1.9 was the correct username/password dialog box - but the wrong username filled out. In parallel with that background threads seemed to be attempting to login with the correct username but an empty password - after 3 attempts in less than a second my account was blocked before I could fillout the username/password dialog.

(I admit) without knowing your code I'm just guessing :-)

Kind regards Uffe  
(Version 1.9.2)

SANDRO NOEL  Uffe

The only thing that has changed and the reason why you do not see the threads asking for a password is that before the mounting threads get launched, BM will check if any of the mounts require a password.

It will ask for that password and then pass it along to the mounting procedure as needed.

The password will remain in RAM for the duration of the execution of the program. once BM is closed the passwords are lost they are not saved to disk.

This procedure allows me to mount multiple shares from the same host with the same username/password.

as opposed to asking the system to validate it against the server and THEN ask the user for the password.

Since BM is a multi threaded application, up to 4 mounts can happen at the same time

thus causing the system to ask to 4 passwords at once even if they are for the same host. witch is not a desired situation for the users.

NOTE: This password scheme, was developed expressly for you, since no one else has mentioned the need for it. If you have now lost trust in BM because the password dialogue is a custom dialogue, I do not know what to say else than, do what you think is best, even if it means discontinuing the use of BM.

Best Regards.  
(Version 1.9.2)

WUFFE  I think you misunderstood me. I'm still happy a happy BM user and i do thrust your app. I just meant that the os dialog could save you from specialized implementation - but apparetly you've already tried that and it did not work as I expected it to.

Kind regards Uffe :-)

  
(Version 1.9.2)

SANDRO NOEL  Ok, I'm looking into it, but you realize that I do not have access to a SecureID server to test this out, so I'm pretty much on a trail and error here.

and well, you are the trail :)  
(Version 1.9)

SANDRO NOEL  i'm working on a release, if you would like to test it before i release it, please send me a mail @ bonjour.mounter@gmail.com  
(Version 1.9)

WUFFE  I guess that you should be able to (sort of) recreeate the problem if you try to mount from BM with a wrong username/password against a smb share ?

BTW: I'll send you an email - I'd be happy to do some testing for you :-)  
(Version 1.9)

SANDRO NOEL  Delete the entry for witch you want to have a prompt and reenter it WITHOUT any password or username.  
(Version 1.7)

SANDRO NOEL  1.9 should fix it....  
(Version 1.9)

SANDRO NOEL  CIFS is a Microsoft extension to SMB.

yes BM will prompt for a password if it is wrong but only if it is not already in you keychain.  
(Version 1.6)

SANDRO NOEL  Yes I noticed yesterday that the domain was getting chopped off,

I intended to chop off .local. only I fixed it,

it will be released in 1.7 as soon as I'm done with all the other features.  
(Version 1.6)

WUFFE  Just tried the new BM 1.7 version

From the log I can see that BM 1.7 now uses the full host/domain-name.

But it does not prompt for username password like you state - and my keychain is completely empty.

the mount attempts in the log are look like this:

Dec 10 11:43:21 macpac Bonjour Mounter[1111]: mount failed for server smb://xxx.yyy.zzz/tmp, error == -5042

I've filled our the username field and expected (like you said) to be prompted with a logon box with username filled out - just like Kinder does...  
(Version 1.6)

SANDRO NOEL  it is supposed to, but i changed so many things as of late, I'll look into it.  
(Version 1.6)

WUFFE  Well it does not I checked with the admin of the fileserv that my mount requests are sent to and the reply is that they see repeating mount attempts with the right username but an empty password and after a number of attempts my account is locked for 15 min.

Since I'm propably not the only one with such access restriction policies - how about a check box ala "do not save password/prompt for password" - or maybe your check if password field is empty is not good enough ?

  
(Version 1.6)

SANDRO NOEL  the actual procedure is a little more complicated, but I will do something that will implement an alternate method if the password is not in the box. and i will add the checkboz to not save the password.

But why exactly do you not want to save your password in BM ? or in your keychain ?

if you cant mount with full name and password, removing it from BM will not change anything, it will just prompt you for it.  
(Version 1.6)

WUFFE  prompting during mount is exactly what I want BM to help me with.

I cannot save my password - it changes for every minute (SecurID)  
(Version 1.6)

SANDRO NOEL  By the way the error 5042 = Password has expired on server.  
(Version 1.6)

SANDRO NOEL  AH! that makes it understandable now.

i'll get back to you asap.  
(Version 1.6)

WUFFE  sorry wrong log line - that is ofcourse during the time period where my account is logged due to too many logon attempts.

Here is another code -5023 - I've also seen -5016

Dec 10 13:28:54 macpac Bonjour Mounter[1410]: mount failed for server cifs://xxx.yy.zz/tmp, error == -5023

Where do you lookup these codes ?

kind reagrds Uffe :-)  
(Version 1.6)

SANDRO NOEL  5016 Server is not responding.

5023 User authentication failed (usually, password is not correct).

in the developer documentation  
(Version 1.6)

WUFFE  Thx

since my system.log covers all day running both BM 1.6 and later BM 1.7 - my guess is that the -5016 code is from the time of running BM 1.6 - it chopped off the domain-part - leaving only a hostname impossible to resolve. The -5023 code is what it is - a wrong (empty) password.

Now everything is accounted for - thx for your explanation.

/Uffe :-)   
(Version 1.6)

SANDRO NOEL  You'll be happy with version 1.5 there is a ton of logging.

as far as usage sample, well,

0: click on the + sign to ass a mount.

1: select a file system type in the popup box.

2: either select a server from the list of servers or enter your own.

3: enter a share point from the server you selected.

4: your username.

5: your password.

6: click save.

7: go back to step 0 for the next mount.

Have fun.  
(Version 1.4)

SANDRO NOEL  The whole point of "mounting silently in the background"

keyword here being silent...  
(Version 1.4)