Your JoeDog fixed more bugs, you guys. We’d like to thank all contributors for their Issue reports and their patch submissions. Good job!
This release fixes two issues. The parser could blow up and segfault on some less than exemplary HTML formatting. And while we own every segfault, we encourage better HTML. We’re all in this together! This release also fixes a compile issue on some platforms. All siege users are encouraged to update to 4.0.8
Your JoeDog is pleased to announce the release of siege-4.0.7 This release fixes several issues with cookies, namely issues with expiry and persistence. We recommend that all siege users update to this release.
Your JoeDog is pleased to announce the release of siege-4.0.6 This release fixes a bug that caused siege to hang when it was invoked for time-based testing (-t/–time). Your JoeDog ran this version over 5000 times without it hanging.
Your JoeDog would like to thank GitHub user ks1322 for a detailed bug report complete with back traces which helped us pinpoint the problem
Your JoeDog is pleased to announce the release of siege-4.0.5. Exciting!
This release includes several bug fixes and minor corrections. It also includes support for IPv6. It allows you to override content-type at the command line and it provides an option for outputting the results in JSON.
You can turn on JSON output with -j/–json-output
$ siege --no-parser -j -c5 -r5 http://www.joedog.org
{
"transactions": 50,
"availability": 100.00,
"elapsed_time": 7.34,
"data_transferred": 0.86,
"response_time": 0.67,
"transaction_rate": 6.81,
"throughput": 0.12,
"concurrency": 4.54,
"successful_transactions": 50,
"failed_transactions": 0,
"longest_transaction": 2.21,
"shortest_transaction": 0.14
}
This is why our emails and sensitive documents are all over Wikileaks. Stop clicking shit. (Geekish)
Talos recently analyzed an interesting malware sample that made use of DNS TXT record queries and responses to create a bidirectional Command and Control (C2) channel. This allows the attacker to use DNS communications to submit new commands to be run on infected machines and return the results of the command execution to the attacker. This is an extremely uncommon and evasive way of administering a RAT. The use of multiple stages of Powershell with various stages being completely fileless indicates an attacker who has taken significant measures to avoid detection.
If I was Snowden, I wouldn’t hold my breath waiting for that pardon….
From the article: “As became clear during my investigation over the past three years, nearly every element of the narrative Mr. Snowden has provided … is demonstrably false.”
Source: www.wsj.com/articles/the-fable-of-edward-snowden-1483143143
I don’t think 2017 is going to be much better….
A dog named Scarface attacked his owners after they tried to put a sweater on him.
Well Your Linux distributors should be happy now. For years they’ve been bugging Your JoeDog to eliminate his convenience library. Linux distributors don’t like convenience libraries which is odd because they’re very convenient. With this release, we move that code from lib/joedog into src.
Valery Levental fixed and improved issues involving the data URI scheme, chunked transfers and zero-length content.
Danylo Hlynskyi improved the man page documentation.
[SIEGE: 4.0.2]
Your JoeDog is pleased to announce a new utility for your fun and games. This is a full-featured version of a perl script we wrote and which is now implemented in C. Introducing AJPing.
This program began life as a snippet which should pave the way for Apache JServ Protocol (AJP) support for siege. Since it’s very useful for checking connectivity and/or measuring the health of a servlet engine, we decided to release it as a fully functional utility.
AJPing supports both IPv4 (default) and IPv6. You can invoke the latter with a command line switch. Let’s take a look at this puppy in action, mmmkay?
Bully $ ajping -i6 -r5 ajp://ip6-localhost:8009/
--- ajping v1.0.1 to ip6-localhost:8009 ---
5 bytes from ip6-localhost (::1): seq=1 time=979 ms
5 bytes from ip6-localhost (::1): seq=2 time=257 ms
5 bytes from ip6-localhost (::1): seq=3 time=199 ms
5 bytes from ip6-localhost (::1): seq=4 time=235 ms
5 bytes from ip6-localhost (::1): seq=5 time=239 ms
--- ip6-localhost:8009 ajping statistics ---
5 packets sent, 5 received, 0% packet loss, time: 1909 ms
rtt min/avg/max = 199/381/979 ms
The first thing you’ll notice is the output looks a lot like ping. That was by design. AJPing sends and receives 5 byte packets and measures the round trip time in milliseconds. When the run is complete, it summarizes the transaction stats in the statistics section of the output.
[AJPing: Initial Public Release]
