I would like to know if you consider the UI and UX changes that come with Windows 10 and improve/change Adgaurd win 32 app Moreover will you convert your win 32 app to WinRT App ( Universal App of windows 10) to my knowledge Universal App can not open in start up but can be update regularly and uninstall and install without mass the system registery/drivers or have a conflict with other programs like win32 are
Notification center and such? We will use it eventually. Not until Windows 10 becomes popular enough.
yes also UI changes to match the new UI of App in windows 10 Moreover Me and my friends would like to see more organized UI with Hamburger menu (Hamburger Menu is part of windows 10) ohh kk Windows 10 is going to be free so it will probably will be success =)
@avatar I have installed AG using the installer from the link above believing that I've got beta version. I have stumbled upon AG forum that the beta assistant is in version 3.0.65 but in my AG installation it shows the assistant version 3.0.62. So my question, is the above link really beta installer? If so, how it could happen that my assistant is not in version 3.0.65? How should I know that I've got AG beta version if there is no sign in the GUI? My AG version is 5.10.2021.6301.
I don't use adguard (yet) but I can tell you I don't scan https traffic in ESET for similar reasons that very good article stated. HSTS support isn't present (in my case with ESET it stops firefox been able to load the page as firefox has higher restriction on HSTS host's.) No HPKP No OCSP Stapling No control over ciphers used (and as article stats ESET doesn't use 1.2) No human verification of certs as the security software takes over that role. I also have been not using even basic http malware scanning as I think http scanning has limited benefits at the absolute most, if you scanning on execution and write, then this should protect you, the difference is you catch it later, that's it really. Although 2 days ago I enabled http scanning in ESET for tests (not https). I see the merits of a cloud based domain blacklist system such as trend micro and what I do on my router (on my router I have a list of known bad domains updated 4 times a day loaded into dnsmasq, all my dhcp clients use the router as their dns server, and this list even gets used if using a vpn, in addition lighthttpd is used to intercept these requests so there is no timeouts causing problems).
@chrcol I know this is off topic, but just FYI: If you disable protocol filtering in ESET, you disable LiveGrid detections as well, because LiveGrid detection is only active during download.
Thanks, I wasn't aware of that, interesting protocol filtering is an independent setting of http/https scanning tho, but you are right its off topic so lets leave this for now and I will look for a nod32 thread to discuss it. Back on topic I plan to try this out on my android phones, as I find it has potential, and on at least one desktop machine. My suggestion to the devs of adguard is to implement the following for https. Some kind of interface for the end user to verify server certificate status, as well as cipher used between adguard and web site. A way to configure allowed ciphers, and even a cipher preference order. A way to view if HSTS, key pinning and ocsp stapling is in use, as well as some kind of CRL implementation. Whilst you have already stated you plan to fix tls 1.2, and some other issues people raised, I feel for users to have confidence in your app, you need to show this to the user that these things are implemented "and" been used.
For now AG Assistant beta should be installed manually (disable default assistant): https://cdn.adguard.com/public/Userscripts/Beta/AdguardAssistant/3.0/assistant.user.js
OK, I thought that this link https://dl.adguard.com/d/2/adguardInstallerBeta.exe gives beta builds but the version of installed build seemed me as the last official build. I want to keep the beta channel.
It gives you the latest beta, it's just happened so that the latest beta and stable are the same now In v6 branch we will make two independent update channels. But now it is different - we have one update channel, but your access to beta updates are managed by the type of the license key you use.
Hi all! We've just released an important update, version 5.10.2024. As you may have heard, SSL vulnerabilities are discovered literally every month. Poodle attack, Freak attack, and most recent – Logjam. Until now our reaction was not enough prompt. It’s time to change that. Lots of SSL issues were fixed: https://blog.adguard.com/en/adguard-news/important-update-adguard-for-windows-5-10-2024.html Full changelog: SSL private key is no more pinned to your computer hardware. Every clean installation you get fresh private key We now better handle TLS 1.2 connections All certs and private keys are now encrypted and stored in a single file SSL filter now checks certificate revocation and does not filter connection in case if certificate is revoked (revoked.grc.com test) What is coming soon: Fully disable SSL interception for the websites using “Extended Validation” certificates. This type of certificates is mostly used by financial companies, banks, etc. Fix Logjam vulnerability as soon as possible (right after it is fixed in popular browsers).
Cheers for the update... I was wondering, are there any special steps required to get AdGuard Assistant working in IE 9? I use IE 10 at the moment, but am not happy with the way it caches stuff (webcache directory over temporaryinternetfiles directory)... uninstalled v10 and installed v9, but no-show for AG Assistant. On the AG forum there are some threads about IE 9 and AG, most mentioning the fix for IE 9 was implemented in AG Assistant 3.0.3x (current version is 3.0.6x). The IE 9 and 10 installs were offline installers, not performed via Windows Updates. I've gone back to v10 for now so I don't need to abuse the backup/recovery requirements for my system. Just thought I'd throw this topic out there, see if anything worthwhile comes out... I am running a fresh install of Windows 7 Ultimate x64, Firefox v29, IE v10 (would like v9).
The latest update breaks my VPN functionality. I can connect, but no browsing is possible whatsoever... disabling the AG Windows Service restores net access. Internet Explorer throws up a message, asking to check my SSL TLS settings, while Firefox says nothing - just the usual cannot connect message. Any chance I can be provided with a standalone installer of the previous version, until I figure out how to handle this? If I reinstall my older version, still 5.10.xxx, it will update to newest, so thought I'd ask for a standalone. I think it was 5.10.2021
Ok, that's weird, does your VPN somehow intercepts your SSL? Try cleaning up SSL folder in %programdata%\Adguard\NetworkTemp\SSL and rebooting. You can download previous version MSI package from here: https://static.adguard.com/5/setup-5.10.2021.6301.msi Important notice: you should run it from cmd.exe with Administrator access.
Thanks for the previous version! I tried emptying the SSL directory and rebooted afterwards... no improvement. I can connect but not browse. Non-browser apps still function properly, such as virus updates etc... I will ask the VPN geeks about how they handle SSL... I must admit, they are pretty hardcore with this VPN stuff.
There's an update on this: for some reason update causes switching network driver from WFP to TDI. Switch it back manually in Adguard's network settings. Meanwhile we'll fix the updater.
