Re: [Cvs-dev] cvs-passwd patch: weird problem

[Prasad J Pandit]

On Sun, 20 Aug 2006, Mark D. Baushke wrote:
> Let me be more explicit. The sanity.sh tests will never require a user
> to put a test version of cvs onto the net to see if it works without
> some regression tests that exercise to the extent possible both the
> client and pserver code paths in isolation.
>
> The point is that your new 'passwd' sanity.sh test assumes that there
> exists a repository that is running :pserver: that you can use as a part
> of the test. This will never be true in our standard regression test
> beds. So, if you don't provide stand-alone tests, this feature will not
> go into the canonical source base.
>
> I hope you understand.

  Oh, surely Mark, I understand your concern! But you know, to be honest, 
I'm yet to acquaint myself with sanity.sh stuff, I've not spent much time 
with it; And so far, I understand only that, it works by creating 
repository and other directories in /tmp for every test it performs.

But the way it handles user input, I don't know. Let's take, for example, 
test to change the password, now it requires three strings(current 
password, new password, confirmed new password) to be entered by user.
so, how do I supply any such information to sanity.sh?

I'm entirely banking on you guys for all guidance & help required in this 
regard. And hope you won't mind. :)


> You should also pay attention to Larry's suggestions regarding the
> improper use of the crypt() function.

  Yes, I saw that page. So, I should copy the ecrypted password from 
crypts static buffer to some other place, and use that pointer, that's it, 
right?

I did that, still problem sustains.

Thank you!
--
regards
   -Prasad
PS: Please don't send me html/attachment/Fwd mails