Brie Gordon
I'm Brie, a 22 year-old graduate of Slippery Rock University's Computer Science department. My interests include Linux (generally and Ubuntu), networking, BSD-style operating systems including my own, BrieSD, translating English-Spanish-English for open source projects and LAMP configuration. Aside from that, I enjoy photography, making short films and soccer.
Posterous is one of my favorite new(ish) web sites!
brie@briegordon.com
Search
Tags
- comcast (3)
- advanced (2)
- custom (2)
- customization (2)
- google (2)
- ISP (2)
- linux (2)
- network (2)
- network latency (2)
- posterous (2)
- View all 92 tags
- programming (2)
- python (2)
- Apache (1)
- auth (1)
- backbone (1)
- backgrounds (1)
- backup (1)
- bash (1)
- bash script (1)
- bin (1)
- brainstorm (1)
- calculator (1)
- capacity (1)
- client (1)
- collatz (1)
- collatz conjecture (1)
- compliant (1)
- contract (1)
- core (1)
- crawl (1)
- crawler (1)
- cron (1)
- css (1)
- customer service (1)
- default (1)
- dropbox (1)
- email (1)
- favicon (1)
- fios (1)
- folder (1)
- friends (1)
- gmail (1)
- googlebot (1)
- google wave (1)
- grep (1)
- host (1)
- hosting (1)
- image (1)
- imgur (1)
- interview (1)
- invites (1)
- IP (1)
- latency (1)
- logs (1)
- lonely (1)
- mailing lists (1)
- math (1)
- mathematics (1)
- newbie (1)
- NIX (1)
- open source (1)
- packet (1)
- packet loss (1)
- php (1)
- ping (1)
- provider (1)
- python development (1)
- reality (1)
- reddit (1)
- RFC (1)
- rfc822 (1)
- robots (1)
- robots.txt (1)
- routing (1)
- rsync (1)
- sales tax (1)
- script (1)
- security (1)
- SEO (1)
- server (1)
- ssh (1)
- technician (1)
- throttling (1)
- tweet (1)
- twitter (1)
- ubuntu (1)
- unix (1)
- verizon (1)
- virtue (1)
- wave (1)
- web (1)
- windows7 (1)
February 24th, 5:01am
2 comments
Easily monitor your computer security via Twitter
This was written for Ubuntu users but most *NIX-based people should be able to follow along. You'll need the basic set up described here.Then place the following in a file called something like /etc/cron.hourly/auths:
Here is an example of what you'll see. It basically tells you about the last time someone tried to authenticate to your computer using the wrong password, their IP address and what username they tried. You may see duplicates but for something quick and dirty...it works. I'll do what needs to be done to eliminate the duplicates very soon. :-).
--Brie
#!/bin/bashTWEET=`/bin/grep "Failed password" /var/log/auth.log | /usr/bin/tail -n1 | /usr/bin/cut -d"]" -f2` echo $TWEET | /root/tweet.pl
Here is an example of what you'll see. It basically tells you about the last time someone tried to authenticate to your computer using the wrong password, their IP address and what username they tried. You may see duplicates but for something quick and dirty...it works. I'll do what needs to be done to eliminate the duplicates very soon. :-).
--Brie
Posted 5 months ago
Comments (2)
Monitoring for success is as easy as grepping for "Successful su" or "Accepted password" in addition or instead.
:+).
--
Brie
Leave a comment...