Non critical error message in pptpd log when it starts up: Oct 2 13:23:03 inf-fw pptpd[15839]: CTRL: Client 10.215.144.48 control connection started Oct 2 13:23:03 inf-fw pptpd[15839]: CTRL: Starting call (launching pppd, opening GRE) Oct 2 13:23:03 inf-fw pppd[15840]: Plugin winbind.so loaded. Oct 2 13:23:03 inf-fw pppd[15840]: WINBIND plugin initialized. Oct 2 13:23:03 inf-fw pppd[15840]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded. Oct 2 13:23:03 inf-fw PPP generic driver version 2.4.2 Oct 2 13:23:03 inf-fw pppd[15840]: Created /dev/ppp device node Oct 2 13:23:03 inf-fw pppd[15840]: pppd 2.4.4 started by root, uid 0 Oct 2 13:23:03 inf-fw pppd[15840]: Using interface ppp0 Oct 2 13:23:03 inf-fw pppd[15840]: Connect: ppp0 <--> /dev/pts/1 Oct 2 13:23:03 inf-fw pptpd[15839]: CTRL: Ignored a SET LINK INFO packet with real ACCMs! Oct 2 13:23:03 inf-fw padlock: VIA PadLock Hash Engine not detected. Oct 2 13:23:03 inf-fw modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.30-gentoo-r4/kernel/drivers/crypto/padlock-sha.ko): No such device Oct 2 13:23:03 inf-fw PPP MPPE Compression module registered Oct 2 13:23:03 inf-fw pppd[15840]: MPPE 128-bit stateless compression enabled Reproducible: Always
more info at https://bugzilla.redhat.com/show_bug.cgi?id=519456 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464673
I don't see the problem here. ppp_mppe.ko initialization function checks cpu_has_hash("sha1", ...) return code and probably that function tries to load padlock-sha.ko. The padlock-sha initialization fails due to missing CPU feature, but ppp_mppe initializes successfully (apparently padlock-sha is optional), so cpu_has_hash() return must have been 1 aka success. If you want to eliminate these padlock-sha traces, just remove CONFIG_CRYPTO_DEV_PADLOCK_SHA from your kernel config file (your CPU doesn't seem to support it anyway). Closed as INVALID.
