tac_plus-ng Illegal packet about event-driven-servers HOT 14 CLOSED

Hi,

thanks, I've pushed a commit that should fix the PCRE(2) issue.

Regarding the "malformed packet" issue: That looks like a key mismatch. Did you configure the Testing123 key on your ASA without quotes?

Thanks,

Marc

from event-driven-servers.

Hi Marc,

Heres the config on the ASA

aaa-server testing protocol tacacs+
aaa-server testing (inside) host 192.168.1.116
key Testing123

I can also decrypt the tacacs request in wireshark using that key so I know it is good on that front, something in tac_plus-ng doesnt appear to like it though im struggling to see where else I can look

from event-driven-servers.

Also still go the same PCRE issue with the latest version

from event-driven-servers.

Hi,

thanks ... the "malformed packet" issue looks like a GCC bug. Please git pull, make clean and rebuild. I've removed the "-O2" optimization.

Regarding PCRE2: When building, do you see any "-DWITH_PCRE2" flag?

Thanks,

Marc

from event-driven-servers.

Just trying that now, and with regards to the PCRE question yes that flag is there " -DWITH_PCRE2 -DPCRE2_CODE_UNIT_WIDTH=8 -DHAVE_EXECINFO_H -"

from event-driven-servers.

INFO: Attempting Authentication test to IP address <192.168.1.116> (timeout: 12 seconds)
INFO: Authentication Successful
ciscoasa#

Thats better!

from event-driven-servers.

Hi,

great ... and the PCRE2 issue is in fact resolved too? No more "binary wasn't compiled with PCRE" messages?

Thanks,

Marc

from event-driven-servers.

Hi,

great ... and the PCRE2 issue is in fact resolved too? No more "binary wasn't compiled with PCRE" messages?

Thanks,

Marc

Unfortunately the PCRE issue still remains

default-config:35: You're using PCRE syntax, but this binary wasn't compiled with PCRE support.
54098: default-config:35: You're using PCRE syntax, but this binary wasn't compiled with PCRE support.
54098: Detected fatal configuration error. Exiting.

from event-driven-servers.

Hi,

that's weird. The relevant code snippet in tac_plus-ng/config.c reads

#ifdef WITH_PCRE
#else
#ifdef WITH_PCRE2
#else
 ... wasn't compiled with PCRE support ...
#endif
#endif

so you should never see that particular message with WITH_PCRE2 set.

I've no idea where that could come from. You did run "make clean" before building?

Thanks,

Marc

from event-driven-servers.

Yup ran make clean but still get

"./default:35: You're using PCRE syntax, but this binary wasn't compiled with PCRE support.
55125: ./default:35: You're using PCRE syntax, but this binary wasn't compiled with PCRE support.
55125: Detected fatal configuration error. Exiting."

When using the config file as is from here "https://www.pro-bono-publico.de/projects/unpacked/tac_plus-ng/sample/tac_plus-ng.cfg"

from event-driven-servers.

So jsut deployed another clean VM and started again, the PCRE issue is gone now, thanks for a speedy resolution of the above

There is one more issue with the default config that comes up now though and thats that pammavis module doesnt seem to exist though im not sure ill be needing this tbh was more an observation

./default:44: /usr/local/sbin/pammavis: No such file or directory
58829: ./default:44: /usr/local/sbin/pammavis: No such file or directory
58829: Detected fatal configuration error. Exiting.

from event-driven-servers.

Hi,

pammavis depends on the PAM development headers (libpam0g-dev on Ubuntu, IIRC, with probably similar names on other distributions). Are those available?

Thanks,

Marc

from event-driven-servers.

Ahh Thanks, installing that has resolved! Thanks again for a quick resolution to this much appreciated!

from event-driven-servers.

Hi,

great, thanks a lot!

Printing some info on what's auto-detected would likely make sense, I might have a look at that.

And it's really sad to see that GCC optimization doesn't work as expected ... I hadn't seen that coming, as there were no issues with clang at all ...

Thanks,

Marc

from event-driven-servers.