JazzGuitarGimp wrote:- If, by chance, the password is still the one Omar set before he gave up control, and
- Does Omar still remember it?
Here's what I can glean from the posts:
Allynmey wrote:Posted: Wed Jul 22, 2015 4:43 am
Hi All, I am aware of the issue with Chrome and firefox. It seems the host was attacked over a month ago and we have a had a few site attacks that were quickly reversed. The AmpGarage was listed in Google's Spamblocker engine and that is why you are getting those messages. We haven't been hit in weeks and when scans are done on the site, it comes up clean. However, having Google release the site from their spam index is another story. It's not the site that is infected, it was our host that was attacked and Google listed all the sites hosted their with the same warning. I am working with Google and the host to remove the warning from our site.
Allynmey wrote:Posted: Sun Nov 29, 2015 5:59 am Post subject: ****Site Problems Update**** Reply with quote
As you all know, the site was attacked in June of 2015 with a spam bot.
[...]
Making things a little tougher is that Omar's original database password was forgotten by him and is making it more difficult to upgrade to the newer version. I'm working with Omar and a PHP engineer to try to get the site updated in the near future.
Bottom line...I have to be very careful with the upgrade so we don't lose what we've built over 13 years! Thank you for your patience. I'm sure it will be a very short time until Google removes the site alert.
Omar wrote:Posted: Tue Dec 01, 2015 9:29 pm
I feel really bad about this but I dug around some old backups and may have found something. I sent Allyn PM with the info. <fingers crossed>
These posts and a few others seem to imply but not clearly state that:
- the google warning cannot be cleared without updating the website's operating software
- the website software is out of date
- it can't be fixed without a password from Omar
- Omar had some hints, sent to Allynmey
- Allynmey is/was/has worked with Omar and a PHP engineer (?) to update the site
- those haven't panned out for one reason or another
- there is some danger of losing the whole site if this is done wrong
@Martin Manning: I am not an expert at PHP websites, but I'm assuming that there is not an alternate way in, otherwise in a year it would have been taken, not simply ignored.
@Groove1: We get little explicit information on who owns what, and I haven't done the detective work. So I don't know. I'm assuming, based on Allynmey's post that him working with Omar and the PHP engineer would have included who owned what pieces and who had (or didn't!) what password. The site is on shared hosting on a server, not its own server.
I did another capture pass. This one completed, but is one level shy of what was needed and misses some attachments to files buried down in the bottoms of threads. I'll do one more to try to get them all.
There is a problem with this approach, though. I found that Scrapbook builds its own non-standard index, not an HTML index. So it may be useful for capturing the content, but not the structure. Or the apparent structure, since I think the actual structure in a PHP site is MySQL. But I am not a web site expert.