Mochabomb

Found this here:

http://forum.doityourself.com/automotive-service-repairs/281894-alternator-wiring-diagram.html

You can find most of the diagrams on www.autozone.com

Log in with your vehicle info-

Click on Repair Info

Then Vehicle Repair Guides

Click Chassis Electrical (main screen, center)

Clcick on Wiring Diagrams to the right side of the page! Wala!

Had to fix some parts of the site today:
* mod security - body limit was gagging up phpmyadmin - vtiget with 300+ tables hitting the limit in modsecurity_crs_10_config.conf: SecResponseBodyLimit 524288 - changed to larger…

Also fixed some suphp stuff, and fixed the db names for the vtiger forms - things ought to be better now - pages are working.. Thanks for commenting - an sorry to everyone that visited a broken page..

Vtiger form demo here: http://mochabomb.com/Demo/cms/index.php?option=com_vtwebform&module=Lead

Anything else broken, please comment below - thanks!

Blocking bogon’s is good for you and your servers health - only because they are generally un-assigned by IANA or the RIR. These bogus IP blocks are perfect for spamming and criminal activity. Read more about them here.

To block these, I wrote this a while back and while hits may be low, in case they ever get routed or make it to my box. I do need to expand to allow updates if a block is now assigned.

#!/bin/sh
#
# Drop all these bad IP's
#
TMPFILE=/tmp/`apg -a 1 -M nc -n 1 -m 26`

touch $TMPFILE

curl -s http://www.spamhaus.org/drop/drop.lasso |grep ^[1-9]|cut -f 1 -d ' ' > $TMPFILE  

for IP in `cat $TMPFILE`; do
    /sbin/shorewall drop $IP
    sleep 5
done

Run this as a cron or in sync with reloading IP tables.

Had these errors recently on the exodus and genesis servers - been a lot of recent work on these…

pam_access(crond:account): access denied for user `someuser' from `cron'
crond[9985]: CRON (someuser) ERROR: failed to open PAM security session: Success
crond[9985]: CRON (someuser) ERROR: cannot set security context

This link solved it:

http://hostechs.com/2008/07/cron-error-failed-to-open-pam-security-session/

* /etc/cron.allow - add users to this file

* /etc/security/access.conf - comment out

# All other users should be denied to get access from all sources.
#- : ALL : ALL
# -:ALL EXCEPT root:LOCAL

Sorbs has been unresponsive to our requests to have our IP block (207.246.200.16/28) re-listed as a static IP block. Our IP block used to be a dynamic IP block, like those for DSL and dialup. Dynamic IP’s are good to block mail from - since most legitimate users have a real mail server with a static IP to connect and send from. Any home computer sending email - well most have no business reason to send email. It’s either a home server or a spam spitting zombie. If you do want to send email from a home system, one can set up smart hosting where outgoing mail is relayed via a real email server.

So, why Sorbs is still listing us - not sure. Any sysadmin’s that use SORBS for spam blocking will block email from these servers also. We only use Spamhaus for blocking, plus their LASSO list to deal with Bogons.