Archive for May 2003
Cenzic Hailstorm Protocol Modeler
NWC | Review | Security | Arming Your Top Security Guns | | May 1, 2003:
«
If you’ve found yourself in one of these situations–and using raw tools to generate network security testing traffic seems perfectly normal to you–there’s a good chance you could have cranked out your testing tool quickly using Hailstorm Protocol Modeler, the flagship product from Cenzic, a company co-founded by famous hacker and security expert Greg Hoglund. (We use the term hacker here in the proper sense: an extremely clever programmer.)
»
Internet2 NetFlow Weekly and Daily Reports Available
Internet2 NetFlow Weekly Reports:
NetFlow data from all core routers of the Abilene network are analyzed
to produce weekly reports of use of the network. In essence, this is a weekly
version of the “Bulk TCP Use
and Performance on Internet2” by
Stanislav Shalunov andBenjamin Teitelbaum
(note, however, that the paper used one day of data while the reports
use a week of data each and that the paper used data from the busiest
router while the reports present a network-wide view).The reports are produced automatically using programs written by
Anatoly Karp and
Stanislav Shalunov.
The CWEB programnfstat.w
reads large daily files and produces intermediate results that are
further digested by a collection of Perl programs.
Tim Bray: Modern Character String Processing
Tim Bray:
Characters vs. Bytes:
«
This is the first of a three-part essay on modern character string processing for computer programmers. Here I explain and illustrate the methods for storing Unicode characters in byte sequences in computers, and discuss their advantages and disadvantages. These methods have well-known names like UTF-8 and UTF-16.
The next essay will consider string handling in the Java, and to a lesser extent C#, computer languages and argue that it is significantly broken, both in terms of efficiency and correctness. The third essay will propose a new approach to string handling in Java.
»
Tim Bray:Programming Languages and Text:
«
Welcome to another installment in ongoing‘s ongoing tour through
text-processing issues.
This one is about programming-language support, and while it makes specific
reference to Java, tries to be generally applicable to modern software
environments.
The conclusion is that Java is OK for some kinds of text processing, but
has real problems when the lifting gets heavy.
Last time out I said this
was going to be a three-part essay, but now I realize I’d already written
two other text-processing-centric pieces before that, one an
intro to Unicode, and the
other entitled
On Character Strings.
The present essay will recapitulate some of the material in that second note,
but no matter how you cut it, we’re already (to quote Douglas Adams) on
volume four of the trilogy.
To make it worse, I’m gestating some essays on full-text-search,
so we’ll just call it a continuing series.
»
