TigerVNC

TigerVNC
Initial release February 27, 2009 (2009-02-27)
Stable release
1.7.0 / September 8, 2016 (2016-09-08)
Written in C, C++, Java
Operating system MS Windows (32-bit/64-bit) (NT/2000/XP), POSIX (Linux/BSD/OS X/UNIX-like OSes), MinGW/MSYS (MS Windows)
Available in English
Type Remote desktop, Remote administration, Distributed computing
License GNU General Public License
Website tigervnc.org

TigerVNC is VNC server and client software, started as a fork of TightVNC in 2009.[1]

Red Hat, Cendio AB, and TurboVNC maintainers started this fork because RealVNC had focused on their enterprise non-open VNC and no TightVNC update had appeared since 2006.[1] The past few years however, Cendio AB who use it for their product ThinLinc is the main contributor to the project. TigerVNC is fully open-source, with development and discussion done via publicly accessible mailing lists and repositories.

Compared to TightVNC, TigerVNC adds encryption for all supported operating systems (not just Linux), but it removes scaling the remote display into the client window, file transfer, and changing options while connected.

TigerVNC focuses on performance and on remote display functionality.[2]

TigerVNC became the default VNC implementation in Fedora shortly after its creation.[3]

A 2010 reviewer found the TigerVNC product "much faster than Vinagre, but not quite as responsive as Remmina".[4]

See also

References

  1. 1 2 Peter Åstrand (2009-02-27). "Open Letter: Leaving TightVNC, Founding TigerVNC". TightVNC mailing list. Retrieved 2014-02-10.
  2. "Review of TigerVNC". Podnova Windows Library. 2013-03-22. Retrieved 2013-12-02.
  3. Adam Tkac (2009-03-04). "TightVNC feature has been renamed to TigerVNC". fedora-devel-list, Development discussions related to Fedora. Retrieved 2013-12-02.
  4. Veitch, Nick (2010-09-17). "TeamViewer, TigerVNC, Vinagre and NoMachine NX". Reviews. Linux Format (136). ISSN 1470-4234. Retrieved 2014-02-10.
This article is issued from Wikipedia - version of the 11/2/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.