The script kiddies are active tonight.
Chain ssh-block (1 references) pkts bytes target prot opt in out source destination 17 1812 REJECT all -- * * 126.96.36.199 0.0.0.0/0 reject-with icmp-port-unreachable 38 2272 REJECT all -- * * 188.8.131.52 0.0.0.0/0 reject-with icmp-port-unreachable 4 348 REJECT all -- * * 184.108.40.206 0.0.0.0/0 reject-with icmp-port-unreachable 19 2080 REJECT all -- * * 220.127.116.11 0.0.0.0/0 reject-with icmp-port-unreachable 20 2316 REJECT all -- * * 18.104.22.168 0.0.0.0/0 reject-with icmp-port-unreachable 16 1796 REJECT all -- * * 22.214.171.124 0.0.0.0/0 reject-with icmp-port-unreachable 512 25388 REJECT all -- * * 126.96.36.199 0.0.0.0/0 reject-with icmp-port-unreachable 20 2248 REJECT all -- * * 188.8.131.52 0.0.0.0/0 reject-with icmp-port-unreachable 15 1800 REJECT all -- * * 184.108.40.206 0.0.0.0/0 reject-with icmp-port-unreachable 17 2032 REJECT all -- * * 220.127.116.11 0.0.0.0/0 reject-with icmp-port-unreachable 18 2048 REJECT all -- * * 18.104.22.168 0.0.0.0/0 reject-with icmp-port-unreachable 17 1964 REJECT all -- * * 22.214.171.124 0.0.0.0/0 reject-with icmp-port-unreachable
These are just the script kiddies caught trying to brute force a login to my home machine over the past hour (they're blocked after five attempts, and the block remains for an hour lest I end up with hundreds of entries). I wonder if there's a quota they have to meet?
Bunny and I just saw Jamie & Adam UNLEASHED at the Kravis Center.
What a fun show.
Adam and Jamie would select
crash test dummies victims volunteers
(and there were no shortage of thoses)
to come up on stage to help demonstrate some principle of physics,
such as a nine year old girl lifting two grown men a foot above the stage,
or arranging four men in a sitting position without chairs,
and other physics-based tricks.
They also talked about several myths they've done on their show Mythbusters which included lots of explosions. A lot of explosions. Including a several minute clip of various things they've exploded over the years (like water heaters, cars, buildings, cement trunks, more cars and in general, nearly every type of explosive device you can conceive of) that nearly brought down the house (literally, since they boosted the base so you could feel the explosions rattling the theater).
And to end the show, they shot a volunteer with a paintball gatling gun for what seemed like a solid minute (don't worry—the volunteer was wearing the suit of armor Adam wore to protect him underwater from sharks) leaving one paint covered volunteer and a volunteer shaped space on the wall behind him.
Very amusing stuff.
But I think the most amusing thing to happen at the show happened during intermission. I received the following text message:
I didn't recognize the number, and it took me a few moments to decide to even answer “Yes.” The response to my response was classic, and indeed, when I looked to my right, I saw my old roommate Rob, his wife Laura, Squeaky and his wife Tanya, sitting at the other end of the aisle.
'Tis a small world indeed.
Luacheck is a static analyzer and a linter for Lua. Luacheck detects various issues such as usage of undefined global variables, unused variables and values, accessing uninitialized variables, unreachable code and more.
The one real issue I have with Lua is its dynamic typing. Of all the bugs I fix in my own Lua code, I would say that the majority are due to typos (wrong variable name) or an unexpected type. So I was quite happy to come across and try out Luacheck. And fortunately, it's pretty straightforward to run.
I ran it over “Project: Sippy-Cup” and … wow.
The extensive regression test I have has already flushed out the typos and the unexpected type errors I tend to make.
But Luacheck found quite a few unused variables
(which is nice—it also found a bunch of unsused LPeg expressions)
and a ton of unintentional global variables (because I forgot to declare them with
The output is easy to read (here's a representative sample from some non-work related code I have):
Checking ptest-cr-select.lua Failure ptest-cr-select.lua:53:9: variable amount was previously defined as an argument on line 52 ptest-cr-select.lua:128:9: variable okay is never accessed ptest-cr-select.lua:193:40: unused argument event ptest-cr-select.lua:197:43: shadowing upvalue conn on line 194 ptest-cr-select.lua:213:21: shadowing upvalue argument event on line 193 ptest-cr-select.lua:215:15: unused variable rem ptest-cr-select.lua:215:15: shadowing upvalue rem on line 194 Total: 7 warnings / 0 errors in 1 file
About the only false positive it finds is this idiom:
function foo(param1,param2) local param1 = param1 or "default value" local param2 = param2 or 3 local a = ... -- ... end
where it will flag
param2 as shadowing an upvalue.
This idiom though,
is used to provide a default value if a parameter isn't given to a function.
It's easy enough to fix,
function foo(param1,param2) param1 = param1 or "default value" param2 = param2 or 3 local a = ... -- ... end
function foo(param1,param2) local param1 = param1 or "default value" -- luacheck: ignore local param2 = param2 or 3 -- luacheck: ignore local a = ... -- ... end
Overall, I'm glad I found this tool. It's been a real eye opener.
- "John" <firstname.lastname@example.org>
- business leads
- Thu, 23 Apr 2015 17:22:50 +0200
You are receiving this email because we wish you to use our email marketing service.
We wish to be your email marketing partner, we can grow your business 2-5 times than now.
If you would require more information please send us an email and we would be glad to discuss the project requirements with you soon. Looking forward to your positive response.
This e-mail message and its attachments (if any) are intended solely for the use of the addressee(s) hereof. In addition, this message and the attachments (if any) may contain information that is confidential, privileged and exempt from disclosure under applicable law. If you are not the intended recipient of this message, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. Delivery of this message to any person other than the intended recipient is not intended to waive any right or privilege. If you have received this message in error, please promptly notify the sender and immediately delete this message from your system.
If you don't wish our future news letter, pls send address to email@example.com for removal.
I'm only reproducing this because of the disclaimer. Really? You're fishing for clients, not giving legal, medical or confidential information. It doesn't mean a thing. Also, when I tried searching for this, Google helpfully mentioned:
Did you mean: This e-mail message and its attachments (if any) are intended solely for the use of the addressee(s) thereof. In addition, this message and the attachments (if any) may contain information that is confidential, privileged and exempt from disclosure under ap…
Also, that text shows up on a lot of emails. A lot.
I would like to note that this came from
a domain registered in China,
from a server in Williamsville, NY.
The email was from
which is from a domain registered to a company in Chesterbrook, PA and administered by a German company in Karlsruhe.
Reply-To: address is firstname.lastname@example.org,
which is from a copmany in China registered by what appears to be either a European or American.
And as you can see,
it doesn't match the “sender” address,
nor the address mentioned in the email itself.
I'm not worried about being sued by these jokers.
A couple of months ago, I was at a party somewhere, and a boy came up to me who was, like, 8 or 10 years old, and he said, “Oh, I really liked Airplane! I thought it was really funny!” And I said, “How was it that you came to see it?” And he said, “Well, my grandfather made me watch it.” [Laughs.] If you’d told us in 1980 that the grandkids of the audience would be the ones who’d keep the movie going, it would’ve been very gratifying. But I don’t think we ever anticipated it. And it’s one of the great thrills, I think, of all of our lives that it still remains well known.
It's an oral history of the making of “Airplane!” from many people who were involved in the making of one of the funniest movies to ever come out of Hollywood. And stop calling me Shirley.
“Okay, I copied down the new password.”
“Wait? I'm stuck with that password?”
“Oh, I can't change the password for ten days. Then I can change it to something less obvious.”
“Okay, fine. Now let me try logging into the site.”
“No, I don't have Internet Explorer.”
“No, I'm not running Windows 7, or any version of Windows for that matter.”
“No, I'm not running Google Chrome.”
“Is there a joke I didn't get?”
“Do you know how I get to the timesheet application?”
“Timesheet application? You want to apply for some vacation time?”
“Okay, first you need to log into the VPN.”
“But we're in the office, why do I need to log into the VPN?”
“No, you're thinkging of The Corpration VPN. You need to log into the Corporation Overlord Corporation VPN.”
“Oh. Where do I go to log into that?”
“Here, let me email you the location.”
“Thank you. Hmm … Ah, I use that account name … but I don't seem to know the password for that account. Is it the same as any other password you use?”
“No, it's a different password.”
“Sigh. … Okay it's not that password … and it's not that password. I'm afraid of trying it a third time lest I get locked out.”
“So once you reset your password and can log on, do not select the ‘Timesheet Application’ but instead select the ‘Monopolistic Database Corporation Application Suite’ instead.”
“Yeah, I can't make this stuff up even if I wanted to.”
“So skip ‘Timesheet Application’ and instead use the ‘Monopolistic Database Corporation Application Suite.’”
“I won't ask.”
“Good, beacuse I don't know the answer.”
Because a picture of a bunny with a pancake on its head is cliché.