Hello all,
all features which have been proposed & approved for TigerVNC 1.1 are
commited in SVN so it's right time to create 1_1 branch and release
TigerVNC 1.1 beta.
There are some pending patches sent here and also in the "patch"
tracker, I will review and commit them. If you have any patches
I would love to be able to build with GNU TLS before this happens. Can
you please look at the problem I reported regarding the use of the older
GNU TLS version?
On 2/7/11 3:48 AM, Adam Tkac wrote:
> Hello all,
>
> all features which have been proposed & approved for TigerVNC 1.1 are
> commited
On Mon, 07 Feb 2011 11:41:14 -0600
DRC wrote:
> I would love to be able to build with GNU TLS before this happens. Can
> you please look at the problem I reported regarding the use of the older
> GNU TLS version?
>
You seem to have been hacking away at this and the other issues you
mentioned.
Uh, no. Precisely not. I'm still hacking. I will let you know.
On 2/9/11 2:28 AM, Pierre Ossman wrote:
> On Mon, 07 Feb 2011 11:41:14 -0600
> DRC wrote:
>
>> I would love to be able to build with GNU TLS before this happens. Can
>> you please look at the problem I reported regarding the use
Furthermore, Adam had said he had some patches to check in prior to beta.
I am working feverishly to finish this stuff before the end of this
week, but it's very difficult work. It's hard to appreciate how complex
our project has become until you really try to package a full-featured
version of i
On Wed, 09 Feb 2011 03:15:14 -0600
DRC wrote:
>
> I could write a book on the difficulties I've had with GnuTLS. I am
> ultimately finding that I have to pretty much build it from source on
> all of the platforms. Honestly, I don't really care about the
> encryption aspects of it at all, but t
We had one-- the Tight Security Extension. :) I signed off on removing
it before I fully understood the ramifications.
It's not an immediately critical issue. I mainly wanted to get GnuTLS
up and running so I could get it in the hands of users and figure out
its place in the universe. The user
On Thu, Feb 10, 2011 at 10:27:33AM +0100, Pierre Ossman wrote:
> On Wed, 09 Feb 2011 03:15:14 -0600
> DRC wrote:
>
> >
> > I could write a book on the difficulties I've had with GnuTLS. I am
> > ultimately finding that I have to pretty much build it from source on
> > all of the platforms. Hon
We could always port over an authentication method that supports
username/password without the full encryption framework. I don't have
any objections to that.
It's already present in the SVN version, but not enabled in the
default security type list:
On 2/10/11 3:35 PM, Martin Koegler wrote:
>> We could always port over an authentication method that supports
>> username/password without the full encryption framework. I don't have
>> any objections to that.
>
> It's already present in the SVN version, but not enabled in the
> default security t
On Thu, Feb 10, 2011 at 04:01:26AM -0600, DRC wrote:
> We had one-- the Tight Security Extension. :) I signed off on removing
> it before I fully understood the ramifications.
Please don't mix up Encryption with VeNCrypt. VeNCrypt consists of two
parts:
1) An extended chooser, which has enough
On Thu, Feb 10, 2011 at 03:46:17PM -0600, DRC wrote:
> On 2/10/11 3:35 PM, Martin Koegler wrote:
> >> We could always port over an authentication method that supports
> >> username/password without the full encryption framework. I don't have
> >> any objections to that.
> >
> > It's already presen
On 2/10/11 3:39 PM, Robert Goley wrote:
> What are the SecurityType options that must be passed to enable it?
> This would be useful in benchmarking differences between TLS and non TLS
> connections...
On the server:
-SecurityTypes=VeNCrypt,Plain -PlainUsers={comma-separated list of
allowed us
On 2/10/11 4:00 PM, Martin Koegler wrote:
> Please don't mix up Encryption with VeNCrypt. VeNCrypt consists of two
> parts:
>
> 1) An extended chooser, which has enough available security type
> numbers even for every hobby developer.
>
> 2) New security types (TLS encryption with/without certifi
First off, thanks to you and Martin on providing the condensed
security howto. I had been digging it up from older VNC lists when
you sent it. I knew options were available but was just not sure on
the correct syntax for passing them. I am now getting the right
prompt
I need VncAuth, because I use it to implement one-time password
authentication (yet another piece of functionality I'd like to
eventually get ported to TigerVNC.)
I also think that VncAuth is what users expect when they try to use VNC
"out of the box." However, the ability for SysAdmins to global
On Thu, Feb 10, 2011 at 04:11:08PM -0600, DRC wrote:
> On 2/10/11 3:39 PM, Robert Goley wrote:
> You also have to create a new PAM service called "vnc". I did this by
> copying /etc/pam.d/passwd to /etc/pam.d/vnc, but different systems do
> this differently. Some systems may use a pam.conf file,
On Thu, Feb 10, 2011 at 04:18:52PM -0600, DRC wrote:
> On 2/10/11 4:00 PM, Martin Koegler wrote:
> > Please don't mix up Encryption with VeNCrypt. VeNCrypt consists of two
> > parts:
> >
> > 1) An extended chooser, which has enough available security type
> > numbers even for every hobby developer
On 2/11/11 2:24 AM, Martin Koegler wrote:
> It should be possible (HAVE_GNUTLS not defined). In that case,
> VeNCrypt + Plain are still available.
Right you are. I built without GnuTLS, and Plain definitely does still
work. That makes me feel better about the feature, in general.
I guess the t
On Fri, Feb 11, 2011 at 12:09:17PM -0600, DRC wrote:
> On 2/11/11 2:24 AM, Martin Koegler wrote:
> > It should be possible (HAVE_GNUTLS not defined). In that case,
> > VeNCrypt + Plain are still available.
>
>
> Right you are. I built without GnuTLS, and Plain definitely does still
> work. That
20 matches
Mail list logo
