First of all, you're site is very, very slow. Don't know why!
--- APPLE part ---
I finally got everything sorted vor eBlocker to work on my MacBook. For reasons onknown to me, under MacOS a certificate validity for eBlocker can't be greater then 2 years.
Everything worked fine yesterday, so this morning, problems again. Now what?
Well I did update my MAC OS yesterday, before going to bed. Today I wanted to install the certificates on my office MAC. eBloker shows only emply spaces for the dates of the certificate and it is not possible to generate a certificate. 😭 So what happened? I took me a while, but i figured it out.
I checked the certificate on my MAC, and the "SSL" settings had been reset. Does APPLE reset certificates when updating OS? Yes it does!!! 🤮
So I set the SSL back to "always trust" and rebooted eBlocker! Now it was possible to generate a new certificate. By the way, my office PC was not listed in the devices before the reboot! On my office PC I installed the certificate and all was well. Since I had not updated my office PC I did that after everything worked.
Result: New OS, certificate set back to defaults! That sucks!! But not your fault. Why does APPLE do that?
--- ANDROID part ---
I really appreciate the work you guys did and are doing. A "problem" I see, is that the eBloker is very "nerdy"! Not many "normal" people will be able to install it, especially the HTTPS part. Somewhere Bene wrote something about a "schischi interface" and he is right. Most users need eye candy and the eBloker interface is somewhat "unusual". I often get new tabs opening up on me when clicking on something and before I know it, I have 6 open eBlocker tabs. Also, there are problems with the "help" when trying to get HTTPS to work under ANDROID.
Since I finally got it to work under ANDROID, I want to share my ideas, if that is ok.
01) There should be a message that the certificate needs to be instaled twice. Once in the system, and again into browsers that don't support system certificates! The wording in your help message is not that clear to me.
02) Above is the help screen for FF and it shows how to install the certificate. Well imagine my surprise, FF does not support that anymore and hasn't in a long time. So why is that message still there? I thought I was doing something wrong! GOOGLE helped me after a while. FF on recent ANDROID devices does not support the import of certificates!
I found I nice work around, FIREFOX NIGHTLY. It has a "secret" setting, that allows the use of device certificates.
Got to go now, lunch is ready! 🤣
First of all, you're site is very, very slow. Don't know why!
Thanks for mentioning. We are currently working on the site and this can yield to slower response times. Please take my apologies for any inconvenience this might cause.
On topic:
I‘ve moved your post to the general eBlocker discussion forum as it‘s not a bug report but rather an experience discussion about Android & macOS behavior.
THX for sharing!
I often get new tabs opening up on me when clicking on something and before I know it, I have 6 open eBlocker tabs. Also, there are problems with the "help" when trying to get HTTPS to work under ANDROID.
We appreciate your feedback very much @robertocravallo.
Well imagine my surprise, FF does not support that anymore and hasn't in a long time. So why is that message still there?
As eBlocker is volunteer run, there has been no volunteer to change this. I hope someone picks up your thoughts and comes up with a concrete idea like better (https) instructions, optimized screen workflows, etc. Until then, I fear, there will be no change.
You are highly invited to take that role, specify how eBlocker can get better (on a text/screen/detailed level) and then chances are very high this will get implemented.
Thanks very much for your contribution.👍
You are highly invited to take that role,
I don't believe, that I have the knowledge for anything like that. Last programming I did was with DELPHI and that was quite some time ago.
It‘s not about „programming“ at all - but it‘s about specification only. So if you feel some text is outdated, for instance - come up with a text that is up-to-date and we will change it. It‘s that easy.
Same with user guidance. If you feel XYZ can be improved, come up with a concrete suggestion how XYZ can be improved.
Thanks very much.
Does APPLE reset certificates when updating OS? Yes it does!!! 🤮
Complete nonsense. You have no idea what you’r talking.
I run macOS Monterey and all installed certificates stayed untouched after updating.
Probably your certificate was never granted trust at the first place!
Complete nonsense. You have no idea what you’r talking.
Thank you for that @subscriber, I guess you where at my house and I just didn't see you!!
I had it happen on TWO of my MACs. I actually took a before and after screen shot, but that is no big help, as there is only the SSL disabled after the update.
What else could be causing that? Bitdefender or something else? I am not hallucinating! If I wasn't looking for it on the second update, I would probably not have noticed it.
Everything was ok and I started the update of OS X. Went right to the certificate manager after the update and the SSL trust was back to off????
It was the update to "macOS 12.0 (21A5284e)".
Does APPLE reset certificates when updating OS? Yes it does!!! 🤮
If this would be the case, I guess there would be millions of mac users having the same bad experience. Then I conclude someone must have posted this bad experience somewhere already. I tried searching. Nothing came up. Strange.🤔
Can you please point us to other sources where users report this behavior?
Please consider: If you are the only user with this issue, it’s probably not Apple’s fault but something else very special in your environment is causing hick-ups with your certificates 🤔
And to underline @Benne‘s invitation:
It would be great if you’d post text/screenshots „how to install the eBlocker certificate under android“. Then we can change the text in the app and could add this to the knowledge base too. Unfortunately we have nobody taking care of documentation and can not compile our own text from the various sources without you. So you are welcome to help improve, no programming skills needed 😉
THX!
It would be great if you’d post text/screenshots „how to install the eBlocker certificate under android“. Then we can change the text in the app and could add this to the knowledge base too. Unfortunately we have nobody taking care of documentation and can not compile our own text from the various sources without you. So you are welcome to help improve, no programming skills needed 😉
I will have a look at that in the future. For now, just a small fix, that I think is more logical and fitting.
That should not be "Day" but "24 hrs" and "24 Std.". In my understanding, "Day" is = to today.
I guess you where at my house and I just didn't see you!!
Get the facts, bro: there is no other report about „Apple changing certificate trust“ but your‘s. 🤔
You seriously remind me of a car driver, who calls the cops reporting hundreds of ghost drivers approaching him. Of course, in his believe he‘s the only one right… all others must be wrong. Sure!
Get the facts, bro: there is no other report about „Apple changing certificate trust“ but your‘s.
Thank you for your valuable input, "bro"! So I guess I am just hallucinating.
And you remind me of the inquisition: I am right, so everyone else is wrong!!! Perfect!
Aren't you just taking this a bit personal? I have (let us maybe say "had") no beef with you! I just reported what happened on TWO of my systems, period!! So why get so aggressive?
Sorry bro, you are right.
@subscriber I see your point. It‘s rather difficult to deal with users who claim bugs but fail to proof they really exist. Of course, as technicians we try to reproduce bugs first before we post them. At least we try to look up infos if others reported the same issue.
Now with @robertocravallo we have a user who‘s obviously not a technician, articulating himself rude and loud. A habit I personally don‘t appreciate, but supporting the forum I’ve learned to ignore these „tones“ patiently. And yes, he comes up with bug claims that lack any reality, failing to proof but rather repeats himself in his special „tone“. That‘s life. Deal with it 😉
BUT @subscriber there is no reason turning into sarcasm and getting personal. I kindly ask you to stop your offenses. Thanks!
I still hope @robertocravallo gets the message and comes up with some proof for his „findings“. Personally I have decided not to reply unless there is hard evidence brought to the table.
At the end I feel @robertocravallo has meanwhile understood there is no bug but it’s his human error. Unfortunately admitting an error is impossible for some people, which I personally find rather sad. But again: that‘s life, we have no choice - let‘s deal with it… 🤪
THX!
At least we try to look up infos if others reported the same issue.
And sometimes, someone is just the first to have / notice a bug. I tried to communicate the problem with the certificate resetting. I was looking for it to happen, as on my other mac. And it did! Why you just put if off as "human error", I don't know! Sorry to say, is that I can't figure out why it is resetting. Let's see what happens with the next beta update...
Now with @robertocravallo we have a user who‘s obviously not a technician
Ok, that is completely wrong, as I was already putting together PCs in the 1980s. I just might not be able to articulate my problem with eBlocker, so a "technician" can understand it. Very frustrating for me.
articulating himself rude and loud
That was never my intention! Sorry!
And yes, he comes up with bug claims that lack any reality,
So great to report them and then be taken seriously. It's not even a bug in your application I reported and never faulted you for it.
I still hope @robertocravallo gets the message and comes up with some proof for his „findings“.
I did take a before and after screen shot, you can gladly have. All it shows though, is that the trust was reset, after I updated. But since you don't believe that happened, what good is my "proof"? I realize of course that it is not a big help, as I probably manipulated it.
At the end I feel @robertocravallo has meanwhile understood there is no bug but it’s his human error.
Nope, no human error on my side.
Unfortunately admitting an error is impossible for some people, which I personally find rather sad.
Ain't that the truth though! And for some reason, it is always the other party that can't admit to it.
I for one have absolutely no problem with admitting to errors made by me, I just never make any!!! 🤣 (Sarcasm!!)
I will now write feedback to APPLE and see what they have to say about this, if anything! I did maybe hallucinate once, but not twice!!!
Thanks for your thoughts. Life also shows: not everyone is reasonable... 😉
I will now write feedback to APPLE and see what they have to say about this
I agree it's better you address your "findings" to Apple and come back here with a confirmation from them.
To sum up, you need to proof:
- "root certificates of 36 month validity do not work with macOS" and
- "macOS resets root certificates after OS updates."
Until then we have no evidence for any change as eBlocker certificates work fine for everyone else. Of course in case you are willing and able to reproduce the issue, we are here to listen to facts and will improve accordingly.
Thanks & all the best!