Am 31.10.2012 14:26, schrieb Dietmar Maurer:
applied, thanks.
The following is needed to automatically create the config on package update:
https://git.proxmox.com/?p=pve-cluster.git;a=commitdiff;h=c1eb6bdfa127ff548e7e83141336019c7e06f38f
Thx - please fix the blowfish cipher - it's blowfish-c
ost.ag]
> Sent: Mittwoch, 31. Oktober 2012 13:12
> To: Dietmar Maurer
> Cc: pve-devel@pve.proxmox.com
> Subject: Re: [pve-devel] PATH V1: central cipher config
>
>
> Am 31.10.2012 13:10, schrieb Dietmar Maurer:
> > AFAIK pve-cluster (package PVE::Cluster).
>
&g
Am 31.10.2012 13:10, schrieb Dietmar Maurer:
AFAIK pve-cluster (package PVE::Cluster).
Patches already sent ;-)
Stefan
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
AFAIK pve-cluster (package PVE::Cluster).
> -Original Message-
> From: Stefan Priebe - Profihost AG [mailto:s.pri...@profihost.ag]
> Sent: Mittwoch, 31. Oktober 2012 11:25
> To: Dietmar Maurer
> Cc: pve-devel@pve.proxmox.com
> Subject: Re: [pve-devel] PATH V1: cen
Am 31.10.2012 10:58, schrieb Dietmar Maurer:
Am 31.10.2012 10:39, schrieb Dietmar Maurer:
Sure but who knows / keeps in mind that pve has a custom config in
/root/.ssh/config instead of just passing with -F a path to a special
config unter pve's config path.
What is the problem? We already hav
> Am 31.10.2012 10:39, schrieb Dietmar Maurer:
> >> Sure but who knows / keeps in mind that pve has a custom config in
> >> /root/.ssh/config instead of just passing with -F a path to a special
> >> config unter pve's config path.
> >
> > What is the problem? We already have custom config in /root/
Am 31.10.2012 10:39, schrieb Dietmar Maurer:
Sure but who knows / keeps in mind that pve has a custom config in
/root/.ssh/config instead of just passing with -F a path to a special config
unter pve's config path.
What is the problem? We already have custom config in /root/.ssh/ (known hosts,
> Sure but who knows / keeps in mind that pve has a custom config in
> /root/.ssh/config instead of just passing with -F a path to a special config
> unter pve's config path.
What is the problem? We already have custom config in /root/.ssh/ (known hosts,
keys, ...)
__
Am 31.10.2012 10:34, schrieb Dietmar Maurer:
Good idea - i want to extent your idea. What about providing
/etc/pve/ssh_config and then pass -F /etc/pve/ssh_config to every ssh / scp
command?
So we have a custom default ssh config only for pve.
/root/.ssh/config is also used for 'root' account,
> Good idea - i want to extent your idea. What about providing
> /etc/pve/ssh_config and then pass -F /etc/pve/ssh_config to every ssh / scp
> command?
>
> So we have a custom default ssh config only for pve.
/root/.ssh/config is also used for 'root' account, which is quite convenient.
Note: roo
Am 31.10.2012 09:47, schrieb Dietmar Maurer:
Many thanks for that patch. But I am still unsure if we should go that way.
I just found another option - /root/.ssh/config
# man ssh_config
What if we simply create that file if it does not exist?
- create /.ssh/config with reasonable value for
chiphers
What do you think?
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [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
> Subject: [pve-devel] PATH V1: cen
Signed-off-by: Stefan Priebe
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
13 matches
Mail list logo
