Greetings,
- Original Message -
> Is there any acceptable reason to use 'blowfish' cipher in vzmigrate?
> We are deny any incoming connection which doesn't use one of the
> following cipher:
>
> aes256-ctr,aes192-ctr,aes128-ctr
>
> This is a security rule our company. When we upgrade vzc
From now on, OpenVZ wiki web site policy has changed to pre-moderate
all new
user accounts. If you want to register (to be able to edit the wiki),
you need
to provide some evidence you are somehow related to the project. All
requests
for new accounts are then moderated. This is to combat the wi
On 10/10/2013 02:03 AM, Mihály Árva-Tóth wrote:
Hello,
Is there any acceptable reason to use 'blowfish' cipher in vzmigrate?
We are deny any incoming connection which doesn't use one of the
following cipher:
aes256-ctr,aes192-ctr,aes128-ctr
This is a security rule our company. When we upgr
Noticing that the write counter is not incrementing in the beancounter file,
nor is it allowing the cgroups to limit the writes either (guessing since the
counter isn't changing the cgroup isn't being applied since its not seeing a
change).
This is what I am setting for a test:
echo "9:1 10485
