Yes, it sounds like malware on your computer. I don't see anything suspicious on any pages here.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
There is nothing we can do about Google. Here at RHDN however, there is an equally effective and simpler solution than the one currently in place: http://www.captcha.net/Oh, the irony! The reCAPTCHA project is a Google project, you know. Although they currently claim to respect whether or not you choose to allow googlebots past it, I'm not sure that applies to their safe browsing bots. Regardless, they certainly have the abilities to bypass it when/if they want.
All downloads currently require being logged in to download. This is not RHDN's desire. We are forced to do this thanks to Google's Safe Browsing Service. Google falsely labeled our site as a malware site, and started blocking many areas of the site in Chrome, Firefox, and Safari browsers. This is entirely due to overly aggressive false positives on our downloads (they even scan inside compressed archive files such as zip). They do not allow any course of action against false positives. The only way to clear the site was making the downloads inaccessible, and requesting a rescan from Google.
Further information can be found in the following forum topics:
Site: Recent Malware Warnings
My browser detects malware in one of the hack's page.
I don't mean to sound rude or anything, but this seems like a rather foolish idea in my honest opinion. I'm just offering my opinion on this matter. Wouldn't it be better to contact the staff at Google and explain that this site is in fact safe, rather than resorting to requiring members to login so that they may download files here? I'm just saying...
Login authentication is not going to stop those warnings. Antivirus/Anti-malware suites are still going to report files scanned and where they came from. All you're doing is annoying your fanbase, especially without any warning. Posting it in big bold letters on the front page "WARNING: LOGIN NOW REQUIRED FOR ALL DOWNLOADS!" is likely a good idea.Yes it would, and it did stop the warnings. The problem comes from Google's Safe Browsing Service which is the cause of the blocking in Chrome, Firefox, and Safari. This is not a local antivirus software issue. This is a global Google issue. Since there is no recourse for false positives with Google, requiring authentication for the downloads allowed us to request a re-scan from Google, pass their scan, and they are removing the warnings.
There's also privacy and legal issues to consider. Logins require logging! Logs can be used in a court...Not really. There is no logging whatsoever associated with downloads. There's not even any logging associated logins in general beyond a temporary web server session so you can be logged into the site. The forum also stores a session id and the last time you logged in for the forum, but that's about it. SMF is used, and open source, so you can check the extent of sessions there yourself.
Wouldn't it be easier and more effective to simply require authors to enclose their projects in password protected container files such as zip, rar or 7z on the project page?I don't see how it would be easy to address the existing near 10,000 downloads available on the site.
Files can have more than one extension, and the order of the extensions is normally irrelevant. For example, if the file welcome.html.fr maps onto content type text/html and language French then the file welcome.fr.html will map onto exactly the same information. If more than one extension is given which maps onto the same type of meta-information, then the one to the right will be used, except for languages and content encodings. For example, if .gif maps to the MIME-type image/gif and .html maps to the MIME-type text/html, then the file welcome.gif.html will be associated with the MIME-type text/html.”
Actually, he popped in here for one post last year. Apparently, he deleted his account aftewards.
What is so damned 'sacred' about 'preserving the original archive' if it preserves all the worst aspects of the past rather than what the FOCUS should be on (the rom hack itself). We should not be so hardcore-focused on preserving the obtuse minutae and utility-wank of the past.
RHDN needs to update their submission rules to permit 'update' hacks to be uploaded that fix issues like requiring a header or special utilities to be patched.
If we can create a version of something like FuSoYa's Super Demo World that don't require jumping through hoops and only a simple BPS patch then that is something that should be permitted rather than immediately rejected.