On Mon, Feb 11, 2013 at 11:44 AM, Eric Sorenson <[email protected]> wrote: > On Feb 10, 2013, at 8:37 PM, Alex Harvey wrote: > >> So, just wondering if anyone out there can think of anything else I can try? >> At worst, this is a showstopper that completely prevents the use of Puppet >> on AIX5.3 - which is an old release, I guess, but I suspect lots of people >> still use it. At the moment, I can't, at any rate, find a workaround. At >> best, it's certainly a showstopper for me. :-) > > Hi Alex, I've also seen this from other users -- would it be possible to get > a tcpdump that shows the negotiation? Doesn't have to be decrypted, the > thing I'm mostly curious about is available in the plaintext payload. I want > to see how far into the ssl negotiation this actually gets, and whether > there's a specific TLS Alert being returned. Feel free to email me directly > if you don't want to post it.
I suspect that others have said this, but because this often comes up, capturing the full packets to a file is the best thing to send: ] tcpdump -ni eth17 -s 65535 -w aix.tcpdump ... -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
