"Alex Peshkov" <pes@...> wrote:

>
> That's are serious issues. What about the compromise? We let user
> specify trusted authentication flag in DPB, and if it is present -
> ignore environment, exactly like we do when there are explicit login /
> password in DPB.

Sounds good to me.

> Right now I suppose to:
> 1. Switch to PROTOCOL_VERSION11.
> 2. Add isc_wish_list() implementation for op_update_account_info and
> op_authenticate_user.
> 3. Move op_authenticate_user opcode to match vulcan's rules.
> 4. Add 'trusted' switch to isql and qli.
> 5. And I ask Jim to add minimal op_trusted_auth to vulcan.

Do you mean the experimental branch or HEAD? An official v2.0 neither
supports Vulcan calls nor trusted authentication, so it shouldn't have a new
protocol version. But the above looks correct to me if applied to the
authentication branch.

> And we should discuss protocol version protection in separate thread.

Of course.


Dmitry