Most simple, favourite snort test rule
Monday, June 7th, 2010alert tcp any any -> any any (msg:”My TEST rule”; flow:stateless; sid:66666;)
alert tcp any any -> any any (msg:”My TEST rule”; flow:stateless; sid:66666;)
Yesterday I ordered at the Jacob Elektronik online shop for the first time. Although I have a mixed history with those non-major online stores, the price for the Intel X18 SSD was pretty good.
Long story short: it’s actually no long story, they shipped it it just some hours after I ordered, and it arrived in just 24h, that is today!
Then you might be surprised that Apple now forbids using your language of choice, …
…but Sony indeed removed the OtherOS functionality with the v3.21 PS3 firmware update on April the 1st. So in order to use the primary function I purchased the 64bit PowerPC and Cell equipped small form factor workstation, I now have to carefully avoid to ever update the firmware again. Oh wait, there still is George Hotz to help out.
I’m crossing my fingers if that allows me to update to the more energy efficient PS3 Slim.
Certainly not the smartest move from Sony, to highly motivate some thousand, if not ten thousands, programmers -certainly some of the brightest minds, using it for super-computers in university labs- to regain access. Maybe even beyond the former restricted access, but now to the RSX, one more SPE, or Slim, as well.
Just my own quick notes for SSL cert generation for use wit CAcert. Mostly just because too many instructions on the web run over many pages with thousands of words, …
Generating the private key:
openssl genrsa -out key.key 2048
Generating the Certificate Signing Request, CSR:
openssl req -new -key key.key -subj /CN=example.com -out key.csr
The CSR is now provided to your signing authority, from which you get the resulting certificate, which you save to something like key.crt.
Some software require the key and the cert to resist in a single file, you can simple cat them together:
cat key.{key,crt} > key.pem
Heise is running a story, reminding us on the ten years anniversary of the burst of the .com bubble. Where about ten years ago the stock value of overrated, mostly internet related companies became penny stock overnight.
I can not stop, but think we will soon see history repeating itself with all those web 2.0 companies, such as Facebook or Twitter. I mean how many millions, and billions are they pumping into them without any reasonable revenue, or just even revenue model in sight?
Sure, at last they can all go down the advertising road. But is there really enough space for them to grab a multi billion share of the ad-market? And 2020 we will be all living from advertising?
Somehow, I do not really see this adding up.
Five years and the wait is finally over–Poker reduced the price to a tenths
For years the German flagship IT trade-shows loose visitors. The Systems is now even history. And last year the Embedded World and CeBIT managers were as stupid to use the same date for the shows???
Our company used to visit the Embedded World as guests. We always where considering to exhibit there, as we did on Linux shows, or the CeBIT. For our start-up every year it became more likely to join the Embedded World, however all abruptly stopped last year when (IIRC) the Embedded World for the first time happened to be the same days as the CeBIT.
It is certainly bad enough to loose visitors to competing shows overseas, such as the Computex or CES. But how can those regressing shows steal each other’s exhibitors and visitors? In the same country, week.
I doubt we are a single incident here. Like us certainly many more have partners at the other show or would like, or have to exhibit on both. There should be at least some days gab between the shows, to make it possible for more to attend both shows. This would still allow foreigners to optimize their travel schedule and visit both in one go. Another, I think even better, option would be to have half a year between both shows. For example move the Embedded World to the autumn. To better match product cycle and product placements.
But on exactly the same days?
With T2 r35579, I just added the required build system, configuration and glue to let the T2 SDE (System Development Environment) utilize clang and clang++ as the default C and C++ compiler. And I just successfully compiled the first packages on a x86-64/T2/Linux test build:
-rw-r–r– 1 root root 3949 Feb 16 15:41 9-atop.log
-rw-r–r– 1 root root 21444 Feb 16 15:45 9-libelf.log
-rw-r–r– 1 root root 55854 Feb 16 15:45 9-fontconfig.log
-rw-r–r– 1 root root 3827 Feb 16 15:45 9-renderproto.log
-rw-r–r– 1 root root 34883 Feb 16 15:46 9-libxext.log
-rw-r–r– 1 root root 12765 Feb 16 15:46 9-libice.log
-rw-r–r– 1 root root 22070 Feb 16 15:46 9-libsm.log
-rw-r–r– 1 root root 31354 Feb 16 15:47 9-libxt.log
-rw-r–r– 1 root root 15357 Feb 16 15:47 9-libxmu.log
-rw-r–r– 1 root root 15243 Feb 16 15:47 9-libxpm.log
-rw-r–r– 1 root root 12157 Feb 16 15:48 9-libxrender.log
-rw-r–r– 1 root root 13854 Feb 16 15:48 9-libxft.log
-rw-r–r– 1 root root 13782 Feb 16 15:48 9-libxkbfile.log
-rw-r–r– 1 root root 135931 Feb 16 16:00 9-openssh.log
-rw-r–r– 1 root root 344112 Feb 16 16:05 9-openssl.log
-rw-r–r– 1 root root 17024 Feb 16 16:06 9-screen.log
The resulting ssh and screen even worked as expected (so far, anyway).
ExactCODE just released another major ExactScan product family update: the new version 2.9 brings vast improvements all over the App. Most notably are excessive image processing performance improvements. For weeks we did nothing else but revisit our algorithms and fine tuned line of code that stood out.
With years of solid foundation code at ExactCODE, ExactScan already was pretty solid. However, even we received reports about issues. So likewise, for months, we where tracking every single stability issue brought to our attention. All of this contributes to making the version 2.9 the most performing and stable release, ever.
It even comes with new, built-in scanner drivers. For example the new Avision D2 models are now all supported, e.g. the AV220D2+, AV320D2+, and various other (yet unreleased) models, even various other vendors.
Of course work continues on the next planed updated, 2.10. For this next, of course free, update we even have another major surprise for you. Stay tuned, it’s just some weeks of QA away.
Read more: ExactScan homepage