Thanks for the information.
no problem
I thought PF blocked programs and processes from running at the admin level. The reason I say so is because there is a behavior setting for each process called "Adjust Privilege".
beware about the name of features in products, sometimes they wmeans nothing but eyepowder.
The rest of the problem is with configurability. I can change the behaviors of processes on a PC here with PF in 3 clicks. I don't know where to start with UAC.
you don't have to start with UAC, when UAC ask for a Process to be elevated, if you launch that process yourself , and you know it is safe ; then just allow; if you didn't launch it; just deny the elevation. UAC is more like a basic anti-executable (deny/default approach aka "yes or no")
Windows firewall? It might be powerful, and I am seeing the light a little bit now that you mention it more and more over the last couple of days as I have been looking into Comodo Firewall and doing some research. I feel it's a good compliment for UAC, and the Trusted Installer and all of that are nice. I feel the problem with Windows Firewall is that making changes comes with limited information. I can see in PF what is connected and what is being blocked, all within a couple of clicks. Also, PF does have its own Trusted Publisher list that can be used and added to.
because you never really play with Windows Firewall and its
advanced settings, i have used Comodo for years , made plenty of guides about how to set it for max security, etc... and now what im using? Windows Firewall.
Windows Firewall is configured by default to be silent , but if you start playing with it , you can see its real power. Now as you said the only lacking feature of WF is there is not much alerts.
if we just talk about the inbound/outbound connection monitoring, WF is as good as other firewalls; the others just add features you seems to like (HIPS, etc...), but those features are not part of a firewall.
I feel like MS missed an opportunity with their firewall to be transparent with MS connections. If MS had chosen to somehow visually separate them from other connections, users could feel much more secure in knowing what is connecting that is NOT MS. Also, we could have a good discussion about which MS connections do what and which ones can be safely shut down and so on. For me, this creates a little bit of a shortfall of trust when it comes to the MS firewall in W7.
that is the only lack of WF. it is why we have some little softs like Binisoft Windows Firewall Control to do that. It is what i use.
I feel like I have the configurability I require from the single PF interface. That works for me. It could be better if there were more information available I feel, but after two years and with programs like GlassWire for information, I am feel like for now this is a better option than MS.
It is just a matter of taste; for me all the actual firewall (Comodo, Private, Zone Alarm, etc...) are not better than WF (about connections monitoring).
As for why not using UAC, anyway. That's a good question. I guess I feel like I have outgrown the need for it at this point. I don't mean any disrespect at all. I am basing my confidence largely on the belief that a process attempting to change its privileges will be blocked by PF and that PF does what it says it does otherwise. After 2 years of the pop ups, it does seem to be doing the job...
In fact you like HIPS/Behavior Blocker feature, which is totally different than UAC ; both works together, and do different jobs. I'm using anti-executables (more strict than HIPS).
Just for the record, I am curious to know how familiar you are with PFs behavior blocking capabilities. There are 21 behaviors monitored by PF, and each one can be set to ask, allow, block. In this way, I do feel like it is doing the job of UAC and more when it comes to kernel level and otherwise...
Tried it long time ago, i was not fan since we had better solutions like Comodo, more tweakable and secure to my taste. Now i use another approach : virtualization + anti-executable; which is stronger in term of security with less hassle (it block everything i dont allow myself, and if something manage to pass , it will not stay inmy system at the next boot); but this kind of setup is not for beginners.