CoreID Protection and Real Simple Syndication (RSS)

Question

We have recently been developing an instance of mediawiki such that it now sits behind a CoreID 7.04 protected server. In essence we are able to read the header information and to pass the credentials back to the application as expected. In this respect things look good and work as expected.
However whilst the protection ensures that any user is correctly authenticated using the secure cookie in a browser as designed we have an issue with any attempts using any RSS reader to connect to this newly protected server. It is this that I am looking in the first instance to you for help.
Naturally the RSS readers (examples include but are not limited to Newsgator, Attensa and rssreader.com) are generally client based and as such are not able to access the browser cookies (perhaps an incorrect assumption ?) meaning that the mechanism that individuals are increasingly relying upon inside the company (and I suspect elsewhere) are unable to surface poignant information from the mediawiki instance - once it is protected.
We have been experimenting with using server redirects and URL manipulation by examining the http header which in practise works (although given the inconsistency associated with this signature this process has it’s own issues) but can see that this increasing list will quickly become time consuming to manage.
I assume that as RSS becomes more the norm. is there a practice that anyone can recommend to allow these clients to successfully connect to a CoreID protected server – ideally without the need for the existing feeds to be adapted?
Any comment gratefully received
Edited by: vuv716g on 24-Nov-2008 03:17

Answer 1

Often times, considering how advanced malware has gotten, a System Restore will simply result in getting infected again. Most infections I've come across tend to occur months before they actually strike and are found. If they are one of those infections that slip in overnight (those JavaScript ones that slip in through Advertisements and infected search results), those tend to infect even the System Restore points. System Restore is a handy tool to have, but it isn't bulletproof.
When such issues happen, MalwareBytes Anti-Malware and SUPERAntiSpyware are wonderful, free pieces of software to have around. Best scanners out there for Malware that are updated daily. To be on the safe side before you start messing with the system anymore, download and install MalwareBytes (http://www.malwarebytes.org) along with SUPERAntiSpyware (http://www.superantispyware.com) and perform a full scan with both scanners. Clean out any infections found, reboot if needed, and then we can go from there to see why the Security Suite is acting up.
When you install the Verizon Internet Security Suite (McAfee under the hood), one of the first things it does is disables the built-in Windows Defender as well as the Windows Firewall, since the Security Suite includes a Firewall and a Spyware scanner with itself. Having two Firewalls and/or real-time scanners in operation can cause some rather nasty problems, besides dragging down system performace. So yes, if the security suite is installed, it's normal for Defender and Windows Firewall to be disabled. When the suite is removed, Defender and Windows Firewall should automatically be re-enabled.
========
The first to bring me 1Gbps Fiber for $30/m wins!