× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Password Validation API
  • From: Douglas Handy <dhandy1@xxxxxxxxxxxxx>
  • Date: Fri, 05 Jan 2001 14:35:29 -0500

Ed,

>It may be possible to modify the logic as Doug suggests 

I wouldn't go so far as to say I "suggested" it.  My main point was that you
couldn't simply compare the entire return value.

>but it would be
>very difficult because the user-id and the password are used as a pair. One
>is used to encrypt the other. 

In terms of being very difficult to make it work, that actually isn't true at
least up through V4R5.  I don't think it serves a useful purpose to describe the
technique here though.  At any rate, there is no guarantee it would continue to
work beyond V4R5.  In fact, I was surprised it *didn't* change at V4R5...

Even though what you do need to compare (through V4R5) is "simple", the rest of
the process was going around the block to cross the street.  Unless you work for
Rube Goldberg, the other alternatives mentioned are better.

Doug
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.