PHX2600 retweeted
📢 Tomorrow, Fri 06/05, don’t miss the @2600Meetings by @2600! ☎
Hosted by @Philly2600 @PHX2600 @LA2600 @Roc2600 @RTP2600 @2600Boston @Bournemouth2600 @ATX2600 @2600Stockholm @2600Lbk @hyannis2600 @2600Nj & others.
Explore all 2600 groups!
➡️ infosecmap.com/explore-map/?…
#InfoSec
PHX2600 retweeted
📢 Today, Fri 05/01, don’t miss the @2600Meetings by @2600! ☎
Hosted by @Philly2600 @PHX2600 @LA2600 @Roc2600 @RTP2600 @2600Boston @Bournemouth2600 @ATX2600 @2600Stockholm @2600Lbk @hyannis2600 @2600Nj & others.
Explore all 2600 groups!
➡️ infosecmap.com/explore-map/?…
#InfoSec
Southern and McClintock
6pm
see you tonight.
maps.app.goo.gl/g63AKJmB72Jk…
92
Whoa there, we screwed up. Our next meeting is NOT this Friday. Because of observation of the 4th, the next meeting will be the following Friday on the 11th.
Apologies for the mix up.
1
139
Awww yisss, meeting this Friday. We expect a talk. Same place, Tempe Escalante Community Center. See ya there.
122
PHX2600 retweeted
A long process start to finish reverse engineering a router, pulling its firmware via UART and netcat, binwalk, IDA pro bug hunting, vuln identifying and finally locating a remote RCE stack smasher and verifying via a qemu MIPS emulator. I started this in August on a whim.
















