Jump to content

puff-m-d

ESET Insiders
  • Posts

    281
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by puff-m-d

  1. Hello, From your scan log, the operating memory, C drive and boot sector are being scanned. A total of 144143 files are being scanned in 41 seconds. The number of files seems a bit low as does the scan speed seems abnormally fast. Are you scanning with a default scan profile or have you set up a custom profile? The only reason I can think of is a custom scan profile is being used. You can set the scan to default if you wish by going to advanced settings > computer > antivirus and antispyware > on-demand computer scan, selecting which profile you use then selecting threatsense engine parameter setup and clicking on default. Other than this I do not know. The amd files you see are part of windows and are present whether your system actually are using them or not. If this does not help you, then hopefully someone with a bit more knowledge than me (or someone from ESET) will be along and help you further. I wish I could have been of more help.
  2. Hello hentaixen, The screenshot you posted only shows the very beginning of that scan log. Could you please post another screenshot of that log where you have scrolled down to the end of the log (where it shows the scan results). This will give more information as to what the scan actually did. Thanks...
  3. Hello hentaixen, Judging from your attached screen capture, you have nothing to worry about and NOD32 is scanning normally. The "error opening" that you are seeing in the log are all files that are locked by the operating system and therefore cannot be scanned. This is normal, ESET is one of the few (if not the only) AV that list these files in the log so most people are not used to seeing this. No AV can scan a file that is being locked by the operating system. As long as the scan is finishing and showing no infected/cleaned files, you are OK. Do not worry.
  4. Same issue here - application update hanging/endless loop - ESS 7.0.104.0 on Windows 8 Pro x64.
  5. Hello, Glad that solved your "Blocking of Https URLs" issues and good to see you found the password protection options. Good luck!
  6. Hello, Have you enabled SSL protocol filtering by navigating the Advanced Setup GUI to: Advanced setup > Web and email > Protocol filtering > SSL and checking the "Always scan SSL protocol" box?
  7. Hello, Thanks Aryeh! I had just noticed over the past few weeks random VSD's having no information when clicking on them. Thanks for notifying the appropriate people.
  8. Hello, What exactly is an ESET VSD for Android when no signatures are listed? See example at this link: hxxp://www.virusradar.com/en/update/android/3.1063 I notice this fairly often on Virus Radar for Android...
  9. Hello, I just wanted to post an update on my issues. The US government help me with my issues with TheBat! email client due to the closing of lavabit. After lavabit's closing, I had to look at my email providers. Obviously, my lavabit accounts have been closed. I have been thinking seriously about closing all of my gmail accounts also and decided to do so at this time. This means that the two email providers that had the issues I no longer use. All of my accounts are now through my ISP (A T & T/yahoo) which have never had any issues with ESS7 and TheBat! So, even though my issues were never actually solved, I am no longer having problems with TheBat! and SSL protocol filtering. However, the issues with Trillian instant messenger remains and I have implemented a workaround by excluding the certificates for the accounts with connection problems. This workaround by excluding certificates is not ideal, but it works and I can live with it. In summary, TheBat! issues resolved by changing of email providers and Trillian issues have been workaround by excluding relevant certificates. Thanks for the feedback from everyone! As always, I am open to a fix if and when it may be available for the Trillian so I may remove the certificates that I have placed on the exclusion list. Thanks again!
  10. Hello, Try KB Solution ID: SOLN333 "I cannot access the settings—I'm being asked for a password. What should I do?" here: hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN333
  11. Hello Marcus, As you can see by my above posts, the advice did not help. I do have a question Is it necessary to export the private key associated with the ess ssl certificate to import it into TheBat!? Also with Trillian, there is no way to import/export keys into it, so I am not sure if it uses its own certificate store or windows. It is just strange to me that both with TheBat! and Trillian, some of the SSL protocol filtering works fine while with others I have to exclude certificates or have random handshake errors. It is not a clear cut "it is working" or "it is not working" as some with each program does fine and others have issues. Thanks for everyone's help...
  12. Hello, I have now tried the above suggestions as to exporting and importing the certificate but issue still remains afterwards. I was able to import into TheBat! but with Trillian there is no such option. Also, when I did the export of the certificate, there was an option to export the associated private key along with the certificate, but the option was greyed put and I could not select it. I do not know if the private key is required on the export and then the import or not, but thought I needed to mention it for the more knowledgeable than me to advise.
  13. Hello, I had previously tried that option but I went back and tried it again (both checked and unchecked) to reverify my results. That setting makes no difference as the issue persists either way. I am not familiar with the terminology (public/known or private/masked) but my e-mail providers are just standard one that anyone may go to and sign up for (so I would assume public). One thing has changed since my original post, the accounts with lavabit and A t & T (through Yahoo) are both working without any errors. The errors are with the Gmail (Google) accounts. Gmail works fine with ssl protocol filtering disabled and fails with the "TLS handshake failure. An existing connection was forcibly closed by the remote host' with the failure rate being about 50 to 60 %.
  14. Hello, Thanks everyone for the replies! I am extremely busy at the moment and it will probably be a day or two before I can try them out. As soon as I am able, I will post back here with my results. Thanks again...
  15. Hello, With SSL Protocol Filtering disabled in ESS, I never get any errors of any kind either in TheBat! e-mail client and Trillian Instant Messenger. It is only with the SSL Protocol filtering enabled in ESS that I get the error scenario listed in my first post. This is telling me that both are set-up properly as they do work error free with ESS's SSL Protocol Filtering disabled. I would then think that I have some setting wrong in ESS or there is some conflict/issue between the two. Additionally, if I had some setting wrong with my e-mail client, then one would think I would always get errors, not randomly as I am. Just for testing purposes, I toggled through the different encryption methods in my e-mail client but whatever I changed the too resulted in failures 100% of the time. The issues on appear when trying to enable the SSL protocol Filtering in ESS. My theory is that both TheBat! and Trillian are not fully compatible (only partially compatible) with the SSL Protocol Filtering in ESS.
  16. Hello, Do not feel bad as when I saw the post about EMS 2 beta above, I searched very thoroughly both the ESET site and the Play Store but could not find it...
  17. Hello, I have seen the above attached image numerous times myself when opening the GUI on my Android phone. I also would like to know what it means...
  18. Hello, I have two questions about how the ESS 7.0.104.0 beta SSL protocol filtering works with two of my apps. The questions are for me to determine if that feature is working correctly on my system or am I doing something wrong. The first question is concerning SSL protocol filtering with Trillian Instant Messenger (multi-client messaging system). I have Trillian set-up with ten different messaging clients/apis/protocols and they are all set-up to use SSL. The following work with no issues at all: Trillian, Facebook, MSN, Skype, Linked-In, and Twitter. However with the following I have to make certificate exclusions in order for them to work: Google, AIM, ICQ, and Yahoo. One would think I would need to make exclusions for either all in the case it was not working or none in the case of it was working. Why do six protocols work with no issues while 4 have to have their certificates excluded? Is there something I am missing or doing wrong? I have tried everything within my limited knowledge but cannot get all ten protocols to work. My second question deals with SSL protocol filtering with TheBat! E-mail Client. I have three different e-mail providers that I use all set-up to use SSL and the results are different for all three. My first provider is A T & T (A T & T contracts Yahoo Mail to provide the service). I never get any errors with this provider and all works perfectly. My second e-mail provider is Lavabit and I also have it set-up to use SSL. About ten to twenty per cent of the time, I get a "TLS Handshake Failure". With my third provider Google set-up for SSL, I get the same as Lavabit "TLS Handshake Failure" except it occurs way more frequently, about fifty to sixty per cent of the time. All three provider are set-up identically to receive e-mail using POP3S (I do not use IMAP). Again a similar question as above: Why does one provider have no issues while another has an occasional issue, and lastly one have frequent issues? Again am I missing something or doing something wrong? Sample error log from # 2 above: 7/26/2013, 13:45:43: FETCH - receiving mail messages 7/26/2013, 13:45:43: FETCH - Connecting to POP3 server pop.gmail.com on port 995 7/26/2013, 13:45:43: FETCH - Couldn't connect to 2607:f8b0:400d:c00::6d trying subsequent addresses... 7/26/2013, 13:45:43: FETCH - Connecting to 173.194.76.108... 7/26/2013, 13:45:43: FETCH - Initiating TLS handshake !7/26/2013, 13:45:44: FETCH - TLS handshake failure. An existing connection was forcibly closed by the remote host I imagine that the above issues are due to a combination of both lack of knowledge and understanding as to exactly how the SSL protocol feature works within ESS 7.0.104.0 beta. Any instruction and/or knowledge concerning this that could be passed along to me will be greatly appreciated...
  19. Hello, Let me add my congratulations to Arakasi!!! I guess that means also that all the winners of the one year ESS licenses have been determined and notified ...
  20. Thanks Janus, I was not sure that option was in ESS 6 as I do not have access to that version at the moment. Your link shows that it is (slightly different location than in ESS 7). I guess that option was omitted from the first beta release of ESS 7 and was added again with the second beta ESS 7 release... Note to myself: I need to remember to search the kb articles more often to find answers ...
  21. Hello, I am not sure that ESS 6 has this option as it was just added to the latest ESS 7.0.104.0 beta that was released this week. In the ESS 7 beta, you can find the option here: Advanced setup > Computer > Removable media. You can see if that setting is in ESS 6, but I do not believe it is although I may be wrong as I am not running version 6 on any of my machines. I would think since the option was just added in the last beta 7 release that version 6 does not have it.
  22. Hello, I have not noticed any speed issues with updates here on my end, but I can verify your issue going to the Virusradar page. When on the Updates tab in the ESET GUI, I click on the update version number (currently 8592 according to the GUI) and am taken to the Virusradar page, with a version number of 8511 dated July 1st, 2013. It seems that indeed the Virusradar page is not up to date and/or is having issues.
  23. Hello Marcos, Thanks Marcos. Actually, I just got around to trying to import the ESET certificate into Opera 15 this morning and discovered that the Windows TRCA was used. I then came here to post my findings to find out that you had already posted that fact. Thanks for verifying my findings (or me verifying yours )...
  24. Hello Marcos, As always, thanks for your response!
  25. Hello, Just wanted to add: From running ESS 7 beta on my Windows 8 Pro x64 system, SSL protocol filtering is mostly compatible with Opera 15 but some incompatibilities do exist. Most of the time there seems to be no issues, but occasionally there are some sites that I cannot get to load. The issue is inconsistent as the sites vary and it is not the same sites each time. For example, this session I cannot load abc.com and xyz.com, but after reboot those two sites will load fine. The one consistent thing is the error on each boot/logon as shown in the first post.
×
×
  • Create New...