1 vncterm (1.1-3) unstable; urgency=low
3 * re-enable javascript-events.patch (used for migrate/reload)
5 -- Proxmox Support Team <support@proxmox.com> Fri, 10 May 2013 07:56:35 +0200
7 vncterm (1.1-2) unstable; urgency=low
9 * recompile VnCViewer.jar with openJDK
11 * set trusted-lib to avoid security popup
13 * disable unused javascript-events.patch
15 -- Proxmox Support Team <support@proxmox.com> Sat, 20 Apr 2013 16:05:41 +0200
17 vncterm (1.1-1) unstable; urgency=low
19 * recompile for wheezy
21 -- Proxmox Support Team <support@proxmox.com> Fri, 15 Mar 2013 08:26:04 +0100
23 vncterm (1.0-3) unstable; urgency=low
27 -- Proxmox Support Team <support@proxmox.com> Tue, 21 Aug 2012 09:14:04 +0200
29 vncterm (1.0-2) unstable; urgency=low
31 * do not create a new process group (with setsid), so
32 we can kill the whole pve task if used inside fork_worker().
34 -- Proxmox Support Team <support@proxmox.com> Tue, 13 Sep 2011 10:49:32 +0200
36 vncterm (1.0-1) unstable; urgency=low
38 * use TigerVNC java sources
40 * implement TLS encryption and vencrypt password auth
42 * removed support for -passwdfile option
44 -- root <root@maui.maurer-it.com> Mon, 24 Jan 2011 10:46:25 +0100
46 vncterm (0.9-2) unstable; urgency=low
48 * compiled for debian etch
50 * use memmove instead of rfbDoCopyRect (avoid SIGSEGV when
51 called with negative dy)
53 -- Proxmox Support Team <support@proxmox.com> Wed, 22 Apr 2009 10:02:08 +0200
55 vncterm (0.9-1) stable; urgency=low
59 -- Proxmox Support Team <support@proxmox.com> Thu, 27 Dec 2007 05:57:17 +0100