Hi Roman No worry. Anyway regarding security. According to the academics definition of security it implies - Integrity - Confidentiality - Availability
What we may have a problem with here is the integrity. The confidentiality is usually lost anyway as vnc is not encrypted. With the harden patch applied we really had a problem with availability as it always crashed. Based on that the "harden" patch is definitely worse from a security point of view, unless the root cause is found and fixed. If anyone finds the root cause I'm happy to know about it. I will not have time to investigate it for a while. Cheers // Ola On Tue, Jun 14, 2016 at 2:31 PM, Roman Mamedov <r...@romanrm.net> wrote: > On Tue, 14 Jun 2016 14:21:47 +0200 > Ola Lundqvist <o...@inguza.com> wrote: > > > It was not Torsten who wrote the patch. > > > Just FYI. > > Apologies for assuming that he did. Guess I jumped to replying due to > facing > this attitude too often, that things must be ultra-hardened and > uber-secure, > without any concern if it's actually usable (SELinux comes to mind). > > Thanks! > > -- > With respect, > Roman > -- --- Inguza Technology AB --- MSc in Information Technology ---- / o...@inguza.com Folkebogatan 26 \ | o...@debian.org 654 68 KARLSTAD | | http://inguza.com/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---------------------------------------------------------------
