OpenSSL Client Certificates and Libevent-2.0.3-alphaFriday, December 4. 2009
Tom Pusateri reported success with using OpenSSL client certificates and libevent's builtin OpenSSL support. Here is what he wrote on the mailing list:
Posted by Niels Provos
in Libevent
at
18:02
| Comments (0)
| Trackbacks (0)
Defined tags for this entry: libevent
Libevent-2.0.3-alpha releaseFriday, November 20. 2009
It has been a while since the last alpha release of libevent-2.0. Yesterday, we released 2.0.3-alpha which can be downloaded from
http://monkey.org/~provos/libevent-2.0.3-alpha.tar.gz Please, give it a spin and let us know if you run into any problems. There have been a lot of changes since the last release, mostly due to Nick's hard work. Here are just some highlights, the ChangeLog contains the full story: - SSL/TLS support on bufferevents, using the OpenSSL library - Improved searching on evbuffer objects - Improved support for Windows - More efficient memory allocation for event_bases that use epoll - Improved thread-safety - The IOCP bufferevent backend is now exposed on Windows; many thanks to Christopher Davis for his work. Many thanks to everyone who helped with patches and bug reports including Rocco Carbone, Brodie Thiesfield, Caitlin Mercer, David Reiss, Alexander Pronchenkov, Jacek Masiulaniec, Ka-Hing Cheung, Christopher Davis, Ferenc Szalai, and Ryan Phillips. Edited to fix the link. Libevent 1.4.13-stable releasedTuesday, November 17. 2009
We just released a new stable version of Libevent that fixes the following problems:
A new alpha release of libevent 2.0 is on its way, too. Thanks to everyone who submitted patches and bug reports. The source code is available at http://www.monkey.org/~provos/libevent-1.4.13-stable.tar.gz. Don't forget to verify the signature. San Mai KnifeThursday, October 15. 2009 A while ago, I forged a San Mai billet with the hope to turn it into a tanto. Unfortunately, the forge I was using had a very oxygen rich atmosphere and the welds did not take very well. Over the last couple of days, I spent some time grinding and heat treating the remaining steel into a knife for practice purposes. The cable structure of the knife came out very nicely with repeated applications of lemon juice and metal polish to remove the oxides left by the lemon juice etch.I also figured out how to take decent pictures of the steel. The trick was to use direct light rather than diffused light that shines directly on the blade, and then have black surfaces inside the light box. The angle of the knife needs to be so that the black is reflected do the camera. Although, this is a failed knife due to all the welding flaws, it still was an interesting experiment.
Posted by Niels Provos
in Hacking
at
14:48
| Comments (0)
| Trackbacks (0)
Defined tags for this entry: bladesmithing
Forging a WakizashiMonday, September 14. 2009 I just finished taking the 5-day basic forging class taught by Michael Bell at Dragonfly Forge. The wakizashi in the picture is the result of it. The blade is about 18in long and was forged from forge-welded cable. The forge welding of the cable conducted by Michael and his son Gabriel took the better half of the first day. Afterward, the steel was forged into a sunobe which has the basic taper for the tang and point of the sword. We then forged in the ji and the shinogi ji. The remainder of the time was spent grinding in preparation for heat treatment. Before the clay was applied, we draw filed the blade so that all file marks were parallel with the edge rather than the perpendicular marks left by the belt grinder. Applying the clay was a three step process; a light coating of the whole blade, applying the ashi lines, and then coating everything that should remain soft. You can see the ashi and where the clay was applied on the middle picture. After heat treating, the blade took on a nice curve and it was back to the grinder. During the last day there was a little bit of time to polish on stones which showed hints of some very wild hamon as well as some mune yaki. The whole class was a great experience.
LEET '10 Call for PapersSaturday, August 29. 2009
The call for papers for the 3rd USENIX Workshop on Large-Scale Exploits and Emergent Threats (LEET '10) Botnets, Spyware, Worms, and More just went out. It will be held on April 27, 2010 in San Jose, CA.
LEET '10 will be co-located with the 7th USENIX Symposium on Networked Systems Design and Implementation (NSDI '10), which will take place April 28–30, 2010. Important Dates
Workshop Organizers Program Chair
Ask Google's Anti-Malware TeamSunday, August 16. 2009
Google's Anti-Malware team has prepared a moderator page where web masters and users can ask questions and vote which questions they would like to see answered. The voting period ends on Friday, August 28th at which point the Anti-Malware team will prepare answers for some of the top-rated questions.
Posted by Niels Provos
in Malware, News, SpyBye
at
16:42
| Comments (0)
| Trackbacks (0)
Defined tags for this entry: malware
New Libevent ReleasesTuesday, July 28. 2009
Nick just announced two new libevent releases. Here is his summary.
Libevent 1.4.12-stable: You can find the source in the usual place: http://monkey.org/~provos/libevent-1.4.12-stable.tar.gz This is a bugfix-only release, and some of the bugs were kind of nasty. I'd recommend that you upgrade, especially if you are writing code that uses epoll or evdns. Changes in 1.4.12-stable:
Libevent-2.0.2-alpha: The first alpha release in the long-promised Libevent 2.0 series is finally out. You can download Libevent 2.0.2-alpha from: http://monkey.org/~provos/libevent-2.0.2-alpha.tar.gz This is an alpha release. Libevent 2.0 is not finished. There will be bugs, and we make no promises about the stability of any APIs introduced in the 2.0.x-alpha releases. When you find bugs, please let us know. Libevent 2.0 is intended to be backward compatible with the Libevent 1.4 APIs[*]. Any program that worked with Libevent 1.4 should still work with Libevent 2.0, unless we screwed up. Please test your programs when you have a chance, so that if we did screw up, we can notice soon. [*] Unless you were messing around with the internals of internal structures. This release adds many new features to the previous alpha release, and fixes many bugs. See the ChangeLog for full details. Highlights include:
Special thanks to everybody who helped find bugs and improve the code, especially James Mansion, Zack Weinberg, and Joachim Bauch. Aikido in HamburgThursday, July 16. 2009
Yesterday, I managed to practice Aikido in Hamburg for the first time in almost twelve years. The dojo at Charlottenstraße was beautiful with windows to the outside and plenty of light. The training was interesting and very enjoyable. I even managed to practice with a few folks from university times. Next week, it's back to the US and Aikido practice in Mountain View.
Posted by Niels Provos
in News
at
02:53
| Comments (0)
| Trackbacks (0)
Defined tags for this entry: aikido
DirectShow Vulnerability Exploited EverywhereSaturday, July 11. 2009
The DirectShow vulnerabilities are being exploited all over the place now. Unfortunately, the second vulnerability in DirectShow is still unpatched and exploit sites seem to be jumping on this. There is even some evidence that it's possible to successfully exploit the vulnerability without even using JavaScript. New exploit domains are popping after every day. DirectShow now seems to be what Flash and PDF were earlier in the year.
Finn (1999 - 2009)Saturday, July 4. 2009Testing the Zowada Forced-Air ManifoldFriday, July 3. 2009
I had time to forge down the 2in pipe for the nozzle today which completed everything needed for the burner. Here is a video of the first test run. Propane and air can be mixed separately via the gate valves which should allow precise control over the atmosphere in the forge.
Posted by Niels Provos
in Hacking
at
21:21
| Comments (0)
| Trackbacks (0)
Defined tags for this entry: blacksmithing, forge
The Village BlacksmithThursday, July 2. 2009
The landlord visited today while I was working on some bolt jaw tongs. When he saw me blacksmithing, he told me that he used to turn the crank blower for a blacksmith when he was a boy and recited the following poem:
Under a spreading chestnut tree Continue reading "The Village Blacksmith" Cybercrime 2.0: When the Cloud Turns DarkWednesday, July 1. 2009
We recently published an article on web-based malware in ACM's Queue Magazine. It provides a short overview of some of the challenges with detecting malicious web sites such as social engineering and examples of techniques for compromising web sites, e.g. htaccess redirection on Apache, etc. This is the article on which my recent ISSNet talk was based.
Making A Monkey ToolSaturday, June 27. 2009 I learned how to make a monkey tool today. Monkey tools can be used for dressing tenons. The basic procedure is as follows. Take 1in square stock and chamfer the edges. Take a slot punch and move it about an 1in from the corner - this is the hammer end. Line the slot punch up very carefully, so that its straight and divides the stock in the middle. Hit it a couple times to get a registration. Now, get the stock nice and hot, align the slot punch with the registration, hit it hard three times, cool the slot punch in water, rotate it by 180 degrees and repeat. At some point, the slot punch is almost through, flip the stock over and use the slot punch to punch out the remaining piece of metal. Now, use a drift to open up the hole to the desired size. Start the drift from the other side of the slot. Doing this over the hardy hole is a good idea. With the slot still inserted, dress up the faces. Then chamfer the corners. Cut off the other side for the length of the tenon and drill a hole of the right size. That's it. Out of the four holes I drifted only two came out sort of in the middle
Posted by Niels Provos
in Hacking
at
14:23
| Comments (0)
| Trackbacks (0)
Defined tags for this entry: blacksmithing
(Page 1 of 5, totaling 69 entries)
» next page
|
QuicksearchSecure DNS?CategoriesShow tagged entriesSpyBye InstallationFollow these instructions to install SpyBye.
Proxy ConfigurationTo use SpyBye set your proxy to www.spybye.org:8080. Then visit http://spybye.org/.
The SwitchProxy Firefox extension might help. DisclaimerThis is my personal blog. The views expressed on these pages are mine alone and not those of my employer.
SpyBye's disclaimer can be found here. |



