coolacid

    date {
        # May 08 10:18:18
        match => ["timestamp", "MMM dd HH:mm:ss"]
        # We don't have a timezone on the log, so we can define it.
        timezone => "America/Toronto"
        target => "timestamp"
    }

coolacid

#!/usr/bin/env python2

# Quick and dirty demonstration of CVE-2014-0160 by Jared Stafford ([email protected])
# The author disclaims copyright to this source code.

import sys
import struct
import socket
import time
import select

coolacid

BTC: 1G2bhiJxsuNzJzyCERPQssh1KEChTXgNY2
LTC: LaxvCQayvnL8mqJXVxqcZCtHo2HsLHMTxh
Doge: DHu7qGvaVw4jqYkpdHJj4KQF81RFxdvMN3


Gratipay: https://gratipay.com/coolacid/
Streamtip: https://streamtip.com/t/coolacid

coolacid

### Keybase proof

I hereby claim:

  * I am coolacid on github.
  * I am coolacid (https://keybase.io/coolacid) on keybase.
  * I have a public key whose fingerprint is D6A0 7736 D260 804B 9289  254B 7B72 7179 9E47 83CB

To claim this, I am signing this object:

coolacid

# Create a temp timestamp field from the dates field
mutate {
     add_field => [ "tmpts", "${dates}" ]
}

# Add the heure field to create an array of both fields
mutate { 
     merge => ["tmpts", "heure"]
}

coolacid

config t
interface range GigabitEthernet 0/2-48
snmp trap mac-notification added
snmp trap mac-notification removed
exit

coolacid

In my experience revealing what you really know about 
systems security is a guaranteed way to lose the job 
interview if you have any clue at all. The only way to 
help an organization get real operations security is to 
worm your way in under false pretenses and then gradually 
migrate them to a secure position. An MCSE cert helps here, 
as it drives away suspicion that you might actually know 
what you're doing. 

--  symbolset 

coolacid

for file in $(grep eval\(base64_decode -lir www); do
    sed -i 's/eval(base64_decode(.*));//' $file;
done;