On Sunday 30 April 2006 11:20, James Harper wrote:
> > No, that would not work very well. The solution, which you seem to
>
> imply
>
> > below is simply to send a different initial Hello "signon" that
>
> contains
>
> > all
> > the necessary information, plus the ability to extend it to different
> > hashes
> > in the future. The new handshake can be easily distinguished from the
> > old.
>
> There's probably an easy answer to this question, but what would be the
> response to a downlevel (say, 1.38.x) file daemon to a new level
> 'Hello'? Maybe any extra stuff on the Hello would be ignored by the
> downlevel client (which would just respond as normal) but noticed by a
> new one which would respond appropriately...
Well, we are probably saying the saem thing except that I have never heard the
word "downlevel" before so I can only guess at what it means.
The current authentication starting with Hello is designed to be upward
compatible. That is if you send a properly designed new Hello command to an
older component, it will ignore the new stuff. This isn't a problem. The
problem is someone needs to implement and test it.
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
