From: Stefan Priebe
Signed-off-by: root
---
PVE/API2/OpenVZ.pm |9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/PVE/API2/OpenVZ.pm b/PVE/API2/OpenVZ.pm
index 846021a..47d7d70 100644
--- a/PVE/API2/OpenVZ.pm
+++ b/PVE/API2/OpenVZ.pm
@@ -859,10 +859,13 @@ __PACKAG
oot; Stefan Priebe
> Subject: [pve-devel] [PATCH 2/3] PVE::API2::OpenVZ: use build_ssh_opt
> instead of static blowfish encryption
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[mailto:pve-devel-
boun...@pve.proxmox.com] On Behalf Of Stefan Priebe
Sent: Dienstag, 30. Oktober 2012 15:44
To: pve-devel@pve.proxmox.com
Cc: root; Stefan Priebe
Subject: [pve-devel] [PATCH 2/3] PVE::API2::OpenVZ: use build_ssh_opt
instead of static blowfish encryption
> You mean for VNC Stuff - OpenVZ and Qemu? Yes we can as it is already TLS
> but otherwise the overhead is low for VNC stuff.
Yes, I guess it is not worth to optimize that now.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com
Am 31.10.2012 05:59, schrieb Dietmar Maurer:
You mean for VNC Stuff - OpenVZ and Qemu? Yes we can as it is already TLS
but otherwise the overhead is low for VNC stuff.
Yes, I guess it is not worth to optimize that now.
The bad thing is that we can't just fire one command. We've to create
two
> The bad thing is that we can't just fire one command. We've to create two
> processes. One listener and one remote sender. This adds at least some
> complex code to pve. Are you sure we need that?
No, you are right - we do not really need that.
___
pv
