Re: [discuss] Problems with Authoxy 3.2?
Dear Heath, I finally got around to testing the formal release version of authoxy on our system without success I'm afraid. Authoxy 3.1.2 works fine on G3's, G4' and G5's with 10.4.5 and 10.4.6 Authoxy 3.2.5 Final doesn't work at all with the same parameters. The System.log records are as follows... May 12 13:10:57 : Authoxy has started successfully May 12 13:11:11 : Ready to NTLM! May 12 13:11:11 : Entering Step 1 May 12 13:11:11 : Entering Step 2 May 12 13:11:11 : Waiting for Step 2 May 12 13:11:11 : Content Length of response: 2385 May 12 13:11:11 : Step 2 is complete May 12 13:11:11 : Entering Step 3 May 12 13:11:11 : Created Type 1 string of 72 characters May 12 13:11:11 : Pausing in Step 3 May 12 13:11:11 : Entering Step 4 May 12 13:11:11 : Content-Length: 0 May 12 13:11:11 : NTLM: Target length is 13 May 12 13:11:11 : NTLM: Target length 2 is 13 May 12 13:11:11 : NTLM: Target offset is 56 May 12 13:11:11 : NTLM Flag: Negotiate OEM May 12 13:11:11 : NTLM Flag: Request Target May 12 13:11:11 : NTLM Flag: Negotiate NTLM May 12 13:11:11 : NTLM Flag: Target Type Domain May 12 13:11:11 : NTLM Flag: Negotiate Target Info May 12 13:11:11 : NTLM Flag: UNKNOWN5 May 12 13:11:11 : NTLM: Target is: TOORAKCOLLEGE May 12 13:11:11 : NTLM: Target length is 180 May 12 13:11:11 : NTLM: Target length 2 is 180 May 12 13:11:11 : NTLM: Target offset is 69 May 12 13:11:11 : NTLM: TargetInfo is: ^B^^Z^T^O^O^R^A^K^C^O^L^L^E^G^E^^A^^R^P^R^O^X^Y^2^0^0^4^^D^0^t^o^o^r^a^k^c^o^l^l^e^g^e^.^v^i^c^.^e^d^u^.^a^u^^C^D^P^R^O^X^Y^2^0^0^4^.^t^o^o^r^a^k^c^o^l^l^e^g^e^.^v^i^c^.^e^d^u^.^a^u^ May 12 13:11:11 : The nonce is: ~8ã•œe‘â. May 12 13:11:11 : Finished Step 4 May 12 13:11:11 : Entering Step 5 May 12 13:11:11 : Got Type 3 msg of 184 characters. May 12 13:11:11 : Finished NTLM! May 12 13:11:11 : Server closed connection, killing session processes. May 12 13:11:11 : Ready to NTLM! May 12 13:11:11 : Entering Step 1 May 12 13:11:11 : Entering Step 2 May 12 13:11:11 : Waiting for Step 2 May 12 13:11:11 : Content Length of response: 0 May 12 13:11:11 : Step 2 is complete May 12 13:11:11 : Entering Step 3 May 12 13:11:11 : Created Type 1 string of 72 characters May 12 13:11:11 : Pausing in Step 3 May 12 13:11:11 : Entering Step 4 May 12 13:11:11 : Content-Length: 0 May 12 13:11:11 : NTLM: Target length is 26 May 12 13:11:11 : NTLM: Target length 2 is 26 May 12 13:11:11 : NTLM: Target offset is 56 May 12 13:11:11 : NTLM Flag: Negotiate Unicode May 12 13:11:11 : NTLM Flag: Request Target May 12 13:11:11 : NTLM Flag: Negotiate NTLM May 12 13:11:11 : NTLM Flag: Negotiate Always Sign May 12 13:11:11 : NTLM Flag: Target Type Domain May 12 13:11:11 : NTLM Flag: Negotiate NTLM2 Key May 12 13:11:11 : NTLM Flag: Negotiate Target Info May 12 13:11:11 : NTLM Flag: UNKNOWN5 May 12 13:11:11 : NTLM Flag: Negotiate 128 May 12 13:11:11 : NTLM: Target is: T^O^O^R^A^K^C^O^L^L^E^G^E^ May 12 13:11:11 : NTLM: Target length is 180 May 12 13:11:11 : NTLM: Target length 2 is 180 May 12 13:11:11 : NTLM: Target offset is 82 May 12 13:11:11 : NTLM: TargetInfo is: ^B^^Z^T^O^O^R^A^K^C^O^L^L^E^G^E^^A^^R^P^R^O^X^Y^2^0^0^4^^D^0^t^o^o^r^a^k^c^o^l^l^e^g^e^.^v^i^c^.^e^d^u^.^a^u^^C^D^P^R^O^X^Y^2^0^0^4^.^t^o^o^r^a^k^c^o^l^l^e^g^e^.^v^i^c^.^e^d^u^.^a^u^ May 12 13:11:11 : The nonce is: óèotÓ‹mô. May 12 13:11:11 : Finished Step 4 May 12 13:11:11 : Entering Step 5 May 12 13:11:11 : Got Type 3 msg of 184 characters. May 12 13:11:11 : Finished NTLM! May 12 13:11:11 : Server closed connection, killing session processes. May 12 13:11:11 : Ready to NTLM! May 12 13:11:11 : Entering Step 1 May 12 13:11:11 : Entering Step 2 May 12 13:11:11 : Waiting for Step 2 May 12 13:11:11 : Content Length of response: 0 May 12 13:11:11 : Step 2 is complete May 12 13:11:11 : Entering Step 3 May 12 13:11:11 : Created Type 1 string of 72 characters May 12 13:11:11 : Pausing in Step 3 May 12 13:11:11 : Entering Step 4 May 12 13:11:11 : Content-Length: 0 May 12 13:11:11 : NTLM: Target length is 26 May 12 13:11:11 : NTLM: Target length 2 is 26 May 12 13:11:11 : NTLM: Target offset is 56 May 12 13:11:11 : NTLM Flag: Negotiate Unicode May 12 13:11:11 : NTLM Flag: Request Target May 12 13:11:11 : NTLM Flag: Negotiate NTLM May 12 13:11:11 : NTLM Flag: Negotiate Always Sign May 12 13:11:11 : NTLM Flag: Target Type Domain May 12 13:11:11 : NTLM Flag: Negotiate NTLM2 Key May 12 13:11:11 : NTLM Flag: Negotiate Target Info May 12 13:11:11 : NTLM Flag: UNKNOWN5 May 12 13:11:11 : NTLM Flag: Negotiate 128 May 12 13:11:11 : NTLM: Target is: T^O^O^R^A^K^C^O^L^L^E^G^E^ May 12 13:11:11 : NTLM: Target length is 180 May 12 13:11:11 : NTLM: Target length 2 is 180 May 12 13:11:11 : NTLM: Target offset is 82 May 12 13:11:11 : NTLM: TargetInfo is: ^B^^Z^T^O^O^R^A^K^C^O^L^L^E^G^E^^A^^R^P^R^O^X^Y^2^0^0^4^^D^0^t^o^o^r^a^k^c^o^l^l^e^g^e^.^v^i^c^.^e^d^u^.^a^u^^C^D^P^R^O^X^Y^2^0^0^4^.^t^o^o^r^a^k^c^o^l^l^e^g^e^.^v^i^c^.^e^d^u^.^a^u^ May 12 13:11:11 : The nonce is: \4ÜWŒ^B7^W. May 12 13:11:11 : Finished Step 4 May
Re: [discuss] Problems with Authoxy 3.2?
on 08/03/06 22:10, Heath Raftery at [EMAIL PROTECTED] wrote: I've been doing a bunch of testing on 3.2 really trying to stress it hard. I'm afraid I simply cannot reproduce these issues. The odd thing is that basically very little has changed in the connection side of things, so this has got me beat at the moment. I have seen the unable to create new processes thing come up occasionally though and am considering some workarounds. In the mean time, you could try increasing the maximum number of processes allowed by the system using sysctl: To show the current limit: % sysctl kern.maxproc To change the limit: % sudo sysctl -w kern.maxproc=1000 And on my end I'll look into setrlimit and alternative ways to invoke processes (perhaps akin to Apache or Squid). Regards, Heath I have been running for about a week with a larger number of maximum processes and I have to report that Authoxy 3.2.5 hasn't given me any problem so far, none whatsoever. I followed the directions in at MacOSXHints.com to permanently increase those limits through a launchd config file. My soft limit is currently 512 and my hard limit is 2048. No problem so far. -Laurent. -- Laurent Daudelin AIM/iChat: LaurentDaudelinhttp://nemesys.dyndns.org Logiciels Nemesys Software mailto:[EMAIL PROTECTED] larval stage: n. Describes a period of monomaniacal concentration on coding apparently passed through by all fledgling hackers. Common symptoms include the perpetration of more than one 36-hour hacking run in a given week; neglect of all other activities including usual basics like food, sleep, and personal hygiene; and a chronic case of advanced bleary-eye. Can last from 6 months to 2 years, the apparent median being around 18 months. A few so afflicted never resume a more `normal' life, but the ordeal seems to be necessary to produce really wizardly (as opposed to merely competent) programmers. See also wannabee. A less protracted and intense version of larval stage (typically lasting about a month) may recur when one is learning a new OS or programming language.
Re: [discuss] Problems with Authoxy 3.2?
Thats interesting, can you please details the configuration that you are using... Also are you using 10.4.5 or 10.4.6... We are very interested in getting this version going but have had no such luck. At this stage we are trying to free up a powerBook on which I am going to reinstall a clean 10.4.6 system and nothing else. Then test Authoxy again... hopefully a machine will come free this week. Cheers, Bruce. Laurent Daudelin wrote: on 08/03/06 22:10, Heath Raftery at [EMAIL PROTECTED] wrote: I've been doing a bunch of testing on 3.2 really trying to stress it hard. I'm afraid I simply cannot reproduce these issues. The odd thing is that basically very little has changed in the connection side of things, so this has got me beat at the moment. I have seen the unable to create new processes thing come up occasionally though and am considering some workarounds. In the mean time, you could try increasing the maximum number of processes allowed by the system using sysctl: To show the current limit: % sysctl kern.maxproc To change the limit: % sudo sysctl -w kern.maxproc=1000 And on my end I'll look into setrlimit and alternative ways to invoke processes (perhaps akin to Apache or Squid). Regards, Heath I have been running for about a week with a larger number of maximum processes and I have to report that Authoxy 3.2.5 hasn't given me any problem so far, none whatsoever. I followed the directions in at MacOSXHints.com to permanently increase those limits through a launchd config file. My soft limit is currently 512 and my hard limit is 2048. No problem so far. -Laurent.
