|
|
|
Author
| Message |
|---|
|
|
Let's wait and see. 
|
|
|
Fine! QA is alive!
|
|
|
ClivetheBeard, in relation to what you said earlier this topic, I understand your concern, but the hacker would need to make radical changes in QA to get infect the account or someone else's computer.
One thing is certain: the hacker must have changed Miguel's password, so he could not log in normally. However, how obviously he's the person who pays for the hosting, he can access the administrative console of the site in hosting server and change his credentials directly in the database.
So from the beginning I disagreed Raphael1985 that the QA was dead.
Well, remains unknown what happened to Miguel to delay to solve. Maybe he was on vacation or unable to do anything for a while, maybe sick. The good thing is that the QA survived on autopilot during this time, as Odie_Spud said, and now it seems that everything is resolved.
I'm also a developer. Miguel, you may need to revise the source code of your site, particularly SQL injection, to prevent further surprises. If you need, you can count on help.
Again, QA is alive forever!
================
ClivetheBeard, em relação ao que você falou no início deste tópico, entendo a sua preocupação, mas o hacker precisaria fazer alterações radicais no QA para conseguir infectar a conta ou o computador de alguém.
Uma coisa é certa: o hacker deve ter trocado a senha de Miguel, então ele não conseguiria logar normalmente. No entanto, como obviamente ele é a pessoa que paga pela hospedagem, pode acessar o console administrativo do site junto ao servidor e alterar as credenciais dele direto no banco de dados.
Portanto, desde o começo discordei de Raphael1985 que o QA estava morto.
Bom, permanece a incógnita do que aconteceu com Miguel para demorar a resolver. Talvez estivesse de férias ou impossibilitado de fazer qualquer coisa durante um tempo, talvez doente. O bom é que o QA sobreviveu no piloto automático durante este tempo, como disse Odie_Spud, e agora parece que tudo está resolvido.
Também sou desenvolvedor. Miguel, talvez você precise revisar o código fonte do seu site, em especial SQL injection, para evitar novas surpresas. Se precisar, pode contar com a ajuda.
De novo: QA está viva, para sempre!
|
|
|
Thanks RbSoft - I had worked out that the hacker was not really dangerous; just malicious - although they could have been dangerous too.
|
|
|
I had problems with my account and I lost several matches in time. Changed my password and did not allow access to password change. This was for about 4 to 5 months. I am now trying to recover this time.
|
| Previous 1 2 3 4 Next |
|
|
|
