|
|
Posted by C. on 09/05/07 12:50
On 5 Sep, 11:00, Sanders Kaufman <bu...@kaufman.net> wrote:
> coldwind2010 wrote:
> > Hi!
> > I want to post a form to a page,and get the output of the page.
> > But the post value includes a authentication code which is 13 figures
> > and change every time.
> > I use curl fuction to do so.
> > I try to get the authentication code at first time,and then post the
> > form with authentication code to the page.
> > But it's not help.
>
> > Do you have some good methods?
> > Thank you!
>
> It can be done, but it's a monumental task that duplicates processes
> already established in the industry.
>
> It's called Public Key Encryption.
>
1) that's not really the solution to the OP's problem - presumably he
doesn't control the remote end to get the authentication system re-
written. The only sensible reason for using a 13 digit single use
password is to prevent leeching - it should be *very* straightforward
to strip this from the responses - I don't understand why the OP
thinks it's a problem.
2) Client side certificates are *not* a monumental task - they're very
easy to implement - not least because of the likes of cacert.org
providing a free CA service.
C.
Navigation:
[Reply to this message]
|