Re: padding check failed on cfengine-2.2.8

Mark Burgess <[email protected]>
Newsgroups gmane.comp.sysutils.cfengine.bugs
Message-ID <[email protected]>
This is an openssl error. It usually means there is something wrong with 
the keys or the data havent been corrupted in transit.
I would check the openssl lib versions or try regenerating the keys.

David Birdsong wrote:
> [resending to the non gnu lists]
>
> My apologies if this was covered well in this group, I'm not sure my
> google searches have combed what's in the non-gnu cfengine lists.
>
> I've saw references to this problem on this very list pertaining to
> 2.1.x from 2006, but no follow-up that it was remedied.  I have a
> client that cannot establish a connection to my new cfservd instance
> regardless of restarting the server or regenerating the keys on either
> end.
>
> The server is:
> Fedora 8 i686 running GNU cfengine-2.2.8
>
> The client is:
> CentOS 4.7 i686 running GNU cfengine-2.2.1
>
> ...though the combination seems irrelevant as I have many other
> instances of cfagent connecting just fine to the cfservd instance on
> this combination.
>
> Here's what debug 3, on the server shows.
> RecvSocketStream(8)
>     (Concatenated 8 from stream)
> Transaction Receive [t 280][]
> RecvSocketStream(280)
>     (Concatenated 280 from stream)
> Received: [SAUTH y 256 37] on socket 6
> Challenge encryption = y, nonce = 37, buf = 256
> cfservd: Private decrypt failed = padding check failed
> Transaction Send[t 59][Packed text]
>
> If change the cfagent to connect to my older cfservd instance on:
> Fedora 7 x86_64 running GNU cfengine-2.2.1
>
> ...the client connects without issue.
>
> Can anybody help out here?
> _______________________________________________
> Bug-cfengine mailing list
> [email protected]
> https://cfengine.org/mailman/listinfo/bug-cfengine
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.