This post provides links to some articles I found last week. The posts might be interesting in various fields of expertise, for either system administrators or developers. Topics include web security, WordPress performance, ASP.NET MVC caching, partial trust, view state MAC, and fixing IIS website hangs.
After not using Windows Live Mail for quite some time, It gave me an error code 0×80041161. This error code can have several different reasons, like corrupt files or services which aren’t started. Read on to learn how to fix this Windows Live Mail error 0×80041161.
Error 0x80041161: Windows Live Mail could not be started
Make sure that your disk is not full or that you are not out of memory. (0x80041161)
Nothing much sysadmin about this I guess, but:
This Windows Live Mail error 0×80041161 just occurred on one of my workstations. Just when I wanted to test something… Great… No idea where the error came from. It looks like:
Turns out I’m not the first one to encounter this Windows Live Mail error 0x80041161, as posted on a Microsoft Outlook.com, SkyDrive community forum. And that’s where I also found the answer.
Assuming this Live Mail error could occur more often for whatever reason, I post the solution here for reference. Somehow, something of Windows Live Mail became corrupted and is thus unwillingly to start. Going through my Application Log, it could be related to SignInAssistant which was unwilling to start around the same time (StartService failed with hr = 0x80070422 – could have been disabled), but I’m not sure.
Fix Windows Live Mail error 0x80041161
Luckily the Live Mail error 0×80041161 is quite easy to fix. Microsoft provides a repair tool called wlarp.exe in the C:\Program Files (x86)\Windows Live\Installer (64-bit) or C:\Program Files\Windows Live\Installer (32-bit) folder. Just run it from the command line and it does the trick for you as you can see in the following screenshots.
How to create a Content Delivery Network (CDN) using IIS Outbound Rules, to offload your content and speed up your website with these tips.
Saotn.Org now running PHP 5.5.4 with WinCache
Good day ‘all!
Today I set up PHP 5.5.4 on one of our webservers @Vevida. Customers who would like to, can now test with this PHP version. Of course I’m also one of those testers Saotn.org now runs PHP 5.5.4, with WinCache as opcode(*) and user cache, on IIS 8.0.
Everything seem to run smooth.
(*) PHP 5.5 comes with its own OPcache donated by Zend, I know.
team Hack.ERS first, Pruts.ERS second and KPN SectorC third
The Global Cyberlympics is an international online cyber security (ethical hacking) competition, dedicated to finding the top computer network defense teams. It tests the skills of information assurance professionals, in teams of 4 to 6 people in the areas of ethical hacking, computer network defense and computer forensics. Each round serves as an elimination round until only winning teams remain. The top winning teams from every continent get invited to play the game live in person at the world finals.
For the third time in a row, this competition is won by a Dutch team. Team Hack.ERS won, team Pruts.ERS came in second, SectorC third. Congrats, great job!
Bash: Grep through a large number of files – argument list too long
Overcoming Bash error ‘/bin/grep: Argument list too long’
The other day I was searching for a particular e-mail in a Maildir on one of our mail servers. Knowing only the From address, I thought I’d use grep. Unfortunately it failed and gave me “Argument list too long“:
# grep -r "example\.com" * -bash: /bin/grep: Argument list too long
This was no wonder, since there are over 190500 files in that Maildir:
# ls -1 | wc -l 190516
There are several ways of overcoming this error message. One, for instance is:
Web monitory and malware clean up company Sucuri writes about (massive) Joomla Media Manager attacks in the wild. The recent discovered and patched vulnerability in Joomla’s Media Manager is actively exploited.
If you are using Joomla and didn’t update your site recently, you better stop doing whatever you are doing, and update it now. There is a very serious vulnerability in Joomla’s Media Manager component (included by default), that can allow malicious files to be uploaded to your site.
The only two safe versions of Joomla are 3.1.5 and 2.5.14. If you are not using either of them, you are at risk.
Read on at Sucuri’s blog: