>>>>> On Mon, 23 Nov 1998 13:26:26 +0100, Petter Reinholdtsen <pere@hungry.com> said:
Petter> 5.2.8 SANE_NET_START
Petter> If the reply value byte_order contains the byte order, there
Petter> should be no need for the data record to start with length
Petter> spesified as unsigned integer in big-endian format. Why is
Petter> this inconsistency there?
Petter> Big endian format is the same as network order. The text
Petter> should make a comment about that.
No, the byte order applies to the _image data_. The RPCs
requests/replies (sans image data) are always in big-endian order.
Petter> 5.2.10 SANE_NET_AUTHORIZE
Petter> Must the protocol be changed to handle encrypted network
Petter> communications when it comes to username/password?
Petter> This network request should contain which encryption method
Petter> is used to hide the password. Maybe there also should be a
Petter> new message type to get a challenge/public key from the
Petter> server to use when encrypting the password.
I suppose one option would be to run the SANE network protocol over
SSL. But I'm not opposed to changing the protocol to allow encryption
of the password alone---if someone volunteers to prototype an
implementation of the proposed changes.
--david
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com