Re: [Inkscape-devel] Status of inkboard feature

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Denis Leroy wrote:
> What is the status of the inkboard feature ? Is it considered stable ?
The version in Inkscape trunk is not yet stable. The .44 Inkboard had a
number of stability fixes applied to it, but it is still disabled by
default (partly because of security concerns).
> More importantly, is it considered safe (from a security standpoint) ?
Inkboard's security status is probably best labeled as unknown.
Although there haven't been any major security flaws shown to exist in
Inkboard (.44 or trunk), neither Inkboard codebase has been audited for
security, and a rewrite certainly doesn't help us insofar as security is
concerned.
> We had requests in Fedora to have the feature enabled and so am doing
> some testing on my side. It was originally turned off because it was
> pretty unstable and would often crash in the loudmouth library, but that
> was a while ago...
A number of crash bugs (and some rather silly mistakes) were fixed in
the .44 release; you might want to give that a try. If you encounter
problems, please let us know.
As Dale pointed out, some Inkboard features -- such as multi-user
conferences -- don't work across all Jabber servers, due to deviations
from behaviors specified in the JEPs.
>
> thx!
> -denis
- - David
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@...
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>
>
* Reasons for rewrite in Inkscape trunk:
(1) A whiteboarding JEP has been drafted as part of another SoC project,
sponsored by the Jabber Software Foundation. (Dale Harvey, one of
Inkscape's SoC students, also had a hand in forming the JEP draft.)
Dale and I (and others, I suspect) feel that it is important for
Inkscape to be able to interoperate with other Jabber SVG whiteboarding
clients.
This JEP, while influenced by .44's Inkboard protocols, defines slightly
different protocols for session initiation, transmitting document
changes, and (very) different protocols for conflict resolution. A
draft is available at http://mya.el-tramo.be/psi-wb/jeps/tmp_wb/wb.xml.
(2) Implementing a new protocol (obviously) does not require a rewrite.
The version in Inkscape trunk, however, is using a new Jabber library
written by Bob Jamison, called Pedro. One large factor in favor of this
move is that Pedro runs stably on Windows, whereas Loudmouth is still
somewhat unstable on Windows.
Pedro exposes a simpler, but very different, interface for receiving and
sending Jabber events. A lot of the Loudmouth code in the original
Inkboard -- and the structure built around that code -- thus ended up
being gutted.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE9EVeC+LlyKjktFMRAhoWAJ9pacxegiMMyxg8UGikYalDqYtFdwCeJihR
Mfip4Xua+QcT4kjhhOgqvzA=
=4r20
-----END PGP SIGNATURE-----