Re: [kphone-devel] Re No 2: Authentication issues

[<kgf...@t-...>]

Well things become clearer now! Once again, kphone behaves correctly so 
far, that 401 and 407 are answered corrrectly! Btw. kphone refuses to 
receive REGISTER and -believe me - never sends 401 and 407 itself! The 
reason for your trouble possibly  was at an completely different place, 
at least I found a way to reproduce your trouble:
1. If we do not enter the auth username into the SipIdentity panel, it 
will never be stored. Thus we end up with a correct password and a       
     wrong username. The authenticating proxy will never understand our 
challenge response!
2. The "bombarding" is formally correct but w.o. sense and bloodily annoing.

I'll correct No.1 tonight, 2. as I told you different times will take 
some time.

Klaus

P.S. Is there an instance of your server in the Internet, if I could use 
it for retesting your bug-reports could possibly be helpfull for both of us!

Fredrik Thulin wrote:
> On Monday 12 June 2006 17:34, Klaus Fleischmann wrote:
>   
>> Hi all,
>> I make the kphone in my free time (on weekends, after office ...)
>> because like to do so! I welcome everybody to inform me about
>> possible missbehaviours or errors. If I find the time, I'll correct
>> them. If someone tries to correct errors herself, I'll give any help,
>> I have time to spend for. BUT please do not try me to change the
>> behaviour of kphone just to fullfill someone's "experiments" needs.
>>
>> DEAR FREDERIK THULIN, I'm not sure, if my English is so bad? I'm
>> really tired to explain you things multiple times,
>>     
>
> Dear Klaus
>
> Let's first try to calm down, no need to get angry here.
>
> I am truly sorry that I obviously have upset you, that was never my 
> intention. I don't think your english is bad. Any problem in our 
> communication must be on my end, because I clearly have failed to make 
> you understand the problem, and thus what needs to be done.
>
>   
>> I'm tired to read 
>> your complaints without ANY proof of the correctness of your analysis
>> (I am still waiting for traces, if kphone internal or ethereal)
>>     
>
> Again, my apologies for being such a lousy bug reporter. Please find 
> attached a PCAP file that demonstrates two of my issues. After the 200 
> OK response to the REGISTER (successfull after I entered the correct 
> password in the authorization dialog box), KPhone starts bombarding my 
> server with SUBSCRIBEs. The reason these SUBSCRIBEs all receive 407 
> responses is that I have an incorrect password stored in my 
> ~/.qt/kphonesirc.
>
>   
>> and I'm absolutely tired to listen to your teachings! 
>>     
>
> Don't worry - I'll stop. I understand that we are now in a position 
> where I will not be able to convey anything at all to you. Too bad, 
> I'll try to learn from this experience in approaching an open source 
> developer with constructive critisism (I thought) about his or hers 
> project, and do better the next time.
>
>   
>> I have absolutely 
>> no obligation to explain my decisions to you, I have absolutely no
>> obligation to change code just to fullfill your needs. You forget one
>> thing, I am not your employee.
>>     
>
> Absolutely true, but no I never thought you were my employee. I thought 
> of you as a fellow open source developer, because that what I am too 
> even though I must admit that I don't do it on my own time. My employer 
> pays me to do it. More about my involvment in open source software 
> below.
>
> You have, as you say, every right to code whatever you wish. There is no 
> law saying you must follow RFC's, and everyone is free to ignore them. 
> What I found disturbing was that you appeared to not see that you were 
> ignoring standards, as opposed to realising that but still continuing 
> to ignore them.
>
>   
>> If we really want to continue our 
>> "cooperation" there are few basic conditions:
>> 1. Openness (tell me your plans and I decide if I am willing to give
>> support)
>>     
>
> I am working on an open source SIP stack/proxy in a programming language 
> called Erlang. The project is called YXA, and has it's home page at
>
> 	http://www.stacken.kth.se/project/yxa/
>
> The reason I started using KPhone was that it had almost the only open 
> source presence implementation I could find. I am currently finishing 
> the very first version of my RFC3265 SIP Event server, and will 
> probably commit it to the YXA subversion repository in a few hours. You 
> and everyone else is very welcome to test my presence server and tell 
> me everywhere where I have failed to follow the standards. I'm sure 
> there are plenty of issues to correct.
>
>   
>> 2. Honesty (PROOF your complaints)
>>     
>
> I hope you consider the attached PCAP file sufficient in this regard.
>
>   
>> 3. Fairness NEVER try to manipulate me (FT:"I've tried patiently and
>> exhaustively to explain to you the correct operations of a UAC that
>> want's to work in a typical open-internet, multi-domain world" Who
>> decides what that "open-internet, multi-domain world" is? You ??? And
>> I have to tremble, if I hear your words??? ROTFL!!!)
>>     
>
> I never tried to manipulate you, and I am truly sorry that you believe I 
> did. What I said about open internet, multi domain world was what I had 
> tried to explain with my weather forecast service. Of course everyone 
> has different perspective about a descriptive thing. Again, I'm sorry 
> that I upset you. Bye.
>
> /Fredrik
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> kphone-devel mailing list
> kph...@li...
> https://lists.sourceforge.net/lists/listinfo/kphone-devel
>