Re: [rfbproto] VeNCrypt security type specification

2011-11-04 Thread Adam Tkac
On 05/19/2011 11:39 AM, Pierre Ossman wrote: > On Tue, 20 Jul 2010 10:31:09 +0200 > Adam Tkac wrote: > >> Next revision of VeNCrypt spec is attached. >> > Any chance of getting this documentation effort restarted/finished? > Would be nice to have things finalised as th

Re: [rfbproto] Fwd: pseudo encoding request

2011-06-08 Thread Adam Tkac
On 06/07/2011 02:02 PM, Brian Hinz wrote: > Has anyone dealt with IANA yet? Are they not responsive? I would have > thought that having the specification controlled by someone that doesn't > necessarily have a vested interest in the protocol would be a good thing. > Assuming that IANA RFC's hav

Re: [rfbproto] VeNCrypt security type specification

2010-07-20 Thread Adam Tkac
On Mon, Jul 19, 2010 at 05:40:14PM +0100, Daniel P. Berrange wrote: > On Mon, Jul 19, 2010 at 02:08:30PM +0200, Adam Tkac wrote: > > +VeNCrypt > > + > > > +Following VeNCrypt subtypes are

Re: [rfbproto] SASL security type specification

2010-07-19 Thread Adam Tkac
be passed through > ``sasl_decode``. > + > +The client now proceeds to wait for the ``SecurityResult`` message, to > +determine whether the server considers the negotiation successful. > + > +SASL server result check > + > + > +At this point the clie

Re: [rfbproto] VeNCrypt security type specification

2010-07-19 Thread Adam Tkac
On Thu, Jul 15, 2010 at 04:09:59PM +0100, Daniel P. Berrange wrote: Hello Dan, thanks for your input. > On Thu, Jul 15, 2010 at 04:45:40PM +0200, Adam Tkac wrote: > > +Following VeNCrypt subtypes are defined in this

[rfbproto] VeNCrypt security type specification

2010-07-15 Thread Adam Tkac
ur comments are welcomed. Regards, Adam -- Adam Tkac, Red Hat, Inc. VeNCrypt security type specification. VeNCrypt security type specification was obtained directly from code of the original implementation, the VeNCrypt project (http://sourceforge.net/projects/vencrypt). Signed-off-by: A

Re: [rfbproto] FYI: new proposed Tight encoding using PNG instead of JPEG

2010-07-08 Thread Adam Tkac
m wondering why the integration into an existing encoding though? > This extra layer of tight encodings on top of the normal encodings is > just extra overhead and is not something that we should be promoting > going forward. +1 I also think it would be better (and easier for implemen

Re: [rfbproto] RFB client file access proposal

2010-06-25 Thread Adam Tkac
tion, about your goal. In the end, would you like to have possibility to mount remote directory hierarchy to local filesystem (on UNIX) or to create something like network disk on Windows? If yes, it will be really great. Regards, Adam -- Adam Tkac, Red Hat, Inc.

Re: [rfbproto] RFB client file access proposal

2010-06-24 Thread Adam Tkac
l that NFS is too cumbersome? If I know NFS implementation well, at least on GNU/Linux it is not possible to export and/or mount NFS filesystem without root privileges. I see this as a major drawback of NFS. Regards, Adam -- Adam Tkac, Red Hat, Inc.

Re: [rfbproto] Internet-Draft

2009-09-07 Thread Adam Tkac
t;our" version will be no longer valid. For example the draft still have vague specification of string encodings, it should be fixed. Regards, Adam -- Adam Tkac, Red Hat, Inc. -- Let Crystal Reports handle the repor

Re: [rfbproto] [PATCH] Specify UTF-8 for strings (v2)

2009-09-01 Thread Adam Tkac
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-j

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

2009-08-20 Thread Adam Tkac
has been modified, e.g. by appending a notice to > the string. > > -- > Pierre OssmanOpenSource-based Thin Client Technology > System Developer Telephone: +46-13-21 46 00 > Cendio ABWeb: http://www.cendio.com -- Adam Tkac, Red Hat, Inc.

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

2009-08-17 Thread Adam Tkac
On Mon, Aug 17, 2009 at 11:20:08AM +0200, Peter Rosin wrote: > Den 2009-08-17 10:59 skrev Adam Tkac: >> On Mon, Aug 17, 2009 at 10:22:56AM +0200, Peter Rosin wrote: >>>>> If it is so natural with UTF-8 and if it really is the only sane choise >>>>> (I thi

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

2009-08-17 Thread Adam Tkac
e page 1252. > + Hm, it is easy to say "invalid portions of UTF-8" string but it is _very_ hard to create an algorithm which will determine if a part of string is valid or invalid. If you are using UTF-8 users might create strings with "obscure"

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

2009-08-12 Thread Adam Tkac
On Wed, Aug 12, 2009 at 01:49:53PM +0200, Peter Åstrand wrote: > On Wed, 12 Aug 2009, Adam Tkac wrote: > >> If I watch this thread correctly there are two points of view: >> >> 1. one side would like to fire away all non-UTF-8 strings, which means >> the older sof

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

2009-08-12 Thread Adam Tkac
the problem will be never solved (bad) In my opinion the best solution will be to create new pseudo encoding called "UTF-8". If one side doesn't support UTF-8 strings it means that strings will be in old format (which effectivelly means unspecified encoding). If both sides declare

Re: [rfbproto] [PATCH] Don't spell out General Input Interface in every heading.

2009-05-28 Thread Adam Tkac
i" if this shortcut already exists in other documents. Regards, Adam -- Adam Tkac, Red Hat, Inc. -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers &