Certificate issues "new ESET forum"

Thanks djackino for confirming it.

=====

I have been several days off home, taking care of a friend who returned home from Hospital.
Not so long ago I lost a very dear Buddy.
These things make you realize that there are more important things in life than "Certificates". I guess that I'm trying to say that I used too hard words in this thread and that I want to say sorry for that.

I'm kind of exhausted now and need sleep.

 

Does anyone running IE 8 on an IPBoard Forum, see the certs flag ? MalwareBytes does as well, as do many others - test those first or again and come back and tell us about it.

The IP board Team can be contacted directly as I see that ESET have exhausted their resources in fixing the certificate flag.

 

Via announcement:
https://forum.eset.com/topic/355-forumesetcom-moving-to-ssl/
For those concerned -

 

MalwareBytes forums come up clean. My workaround is to use Firefox for
the new ESET forums until this is fixed.

 

The situation has now been explained at the new Eset forum:
https://forum.eset.com/topic/355-forumesetcom-moving-to-ssl/

Thanks to siljaline for posting the question over there.

The answer from MS-adm over there:

 

Glad to have this finally explained and closed out as an outstanding issue on the new Forum. https://forum.eset.com/

 

I think the certificate is a self-signed certificate. I am not 100 % sure about that, but I think it is. It is up to ESET to confirm or deny that.
If it is, a big part of this whole "discussion" could have been avoided if ESET has told so right from the start. Why they didn't, keeps puzzling me... Just be open and honest!
I don't have numbers about users worldwide still using XP and IE8. But I guess that there must be a lot of them. Those users simply cannot read the new ESET forum when they follow the very clear and strong warning from their Windows XP and browser IE8 about the certificate.
There is a work-around for it for users on XP and IE8. They have to import (install) the certificate. Why ESET didn't tell that, is also something puzzling me. Maybe ESET should make a kb-article about that with step-by-step instructions. But that is up to them.

On the Wilders board you usually use http. But you can use https. LowWaterMark has made for a few years now a self-signed certificate for that. He has been very open about that.
If you want to use https on Wilders, do you also get a warning on XP/IE8? Yes, you do. But you can import (install) that certificate on XP/IE8, and after a reboot you don't get that warning anymore. I just did it and it works. I could give screenshots, but I'm using the Dutch version of XP and I guess that it would be better to have them in English.

One of the differences between the certificate for https here on Wilders and the one for the new ESET forum is, as I noticed, the way the public key is set up. Wilders uses RSA (2048 Bits); the new ESET forum uses RSA (1024 Bits).

 

Hello,

FanJ, first off, thanks for all your detailed feedback in reporting this problem.

While ESET has been providing support through the Wilders Security Forums for many years, we are somewhat newer at hosting our own forums, and it's inevitable that not everything is going to go as smoothly as we wished.

ESET is in the process of addressing the issues reported with the SSL certs on the new forum.

Again, thanks for your help.

Regards,

Aryeh Goretsky

 

I still have this problem/warning using IE 10 and Windows 7 64 when trying to open the first page of the forum. Irritating that this issue was closed in the "new forum".

 

Hello Aryeh,

You're welcome.

Regards,
Jan

 

If you do require assistance - please let us know what your exact issue is within this thread and we shall attempt to replicate or fix whatever you are seeing forthwith.