Chrissie, one more thing.

And I also suppose that the key is read only one time at the start-up of
the Corosync.
In other words there is no any check for the presence of the key or its
update, while Corosync is working.
Am I right?

Thank you,
Kostya

On Thu, Feb 5, 2015 at 2:42 PM, Kostiantyn Ponomarenko <
konstantin.ponomare...@gmail.com> wrote:

> Hi Chrissie,
>
> On Thu, Jan 29, 2015 at 11:44 AM, Christine Caulfield <ccaul...@redhat.com
> > wrote:
>
>> as corosync rejects the messages
>> with the wrong authkey
>>
>
> And I suppose that it is enough just to use "crypto_hash" option.
> I am right?
>
> Thank you,
> Kostya
>
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to