Hi Gabriel,
I can't reproduce that behavior -- just added a couple more keys to one of my lab configs, and each one of the keys just worked.
Any special chars in the new key, perhaps? I assume that "oldkey" and "newkey" aren't the real keys you're using.
Cheers,
Marc
--
You received this message because you are subscribed to the Google Groups "Event-Driven Servers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to event-driven-ser...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/event-driven-servers/dd5d48cd-3322-4640-a124-7b1b0c086cfan%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "Event-Driven Servers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/event-driven-servers/K7t4KgLy_zo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to event-driven-ser...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/event-driven-servers/73f5883f-c069-43c2-8647-90454cd21ead%40googlemail.com.
Hi Gabriel,
just tried the secondary-keys feature again, no issues, tested with varying key sizes.
Does Wireshark decoding confirm that the key the switch uses is one of your "oldkey"/"newkey" definitions, and does tac_plus-ng debug output show that the daemon tries all configured keys?
Cheers,
Marc
To view this discussion visit https://groups.google.com/d/msgid/event-driven-servers/CAAw9igD-ZvMYjT2HosDMaBbA7JfQg-8fZSXt_PjCMSjeQd91RQ%40mail.gmail.com.