27 dec 2001 Status report ----------------------------- >combining of all data into a single "steel tube" --if we could >accomplish this in the short term without adopting a whole new >protocol such as SSH, we'd have a releasable piece of software
Follow the link below: http://www.geocrawler.com/lists/3/SourceForge/16728/0/7371519/ . Here, in section "III. LONG-TERM PLANS", we suggest option A or B of Kaboodle further development. A: without adopting SSH, B: with SSH. We need to hear about your choice as upon this depends our January schedule. We believe option A is quite reasonable as in 2.5 -3 months (your new key scheme is not accounted) we'll have a workable product. >described in thee spec. The shortcoming which I see in the this piece >is that, right now, a partnership cannot be created "in privacy". Both Igor and I support your point that two Kaboodle users should be able to create a partnership certificate with no mediation from a third side. >Please let me know if details of those interactions affects >your "steel tube" design decisions and scheduling and I'll finish In case of the abovementioned variant A, your new key exchange procedure will not affect the current steel tube design; and as for variant B, I am afraid the answer cannot be given right away. At present, the VNC steel tube applies encryption with EncryptDecrypt Kaboodle method on a given key. So, key exchange and encryption are independent process. _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
