Author Topic: Norton keeps dumping esptool.exe on extraction  (Read 2544 times)

exeng

  • Sr. Member
  • ****
  • Posts: 454
Norton keeps dumping esptool.exe on extraction
« on: August 09, 2016, 12:33:47 pm »
Trying to make sure my tool chain is the latest and greatest. When I extract files from OakRestore-master Norton scans an deletes esptool.exe because it thinks it's a Trojan. I'm trying to solve another upload problem and want to be sure I have the latest restore files from github.

Is this file safe?

kh

  • Jr. Member
  • **
  • Posts: 64
  • OakTerm developer
Re: Norton keeps dumping esptool.exe on extraction
« Reply #1 on: August 09, 2016, 04:12:49 pm »
Here are the checksums for my copy, also downloaded from github:

Code: [Select]
$ md5sum esptool.exe
dc22f4eba1c32676a1d2b16132d0552c *esptool.exe

$ sha1sum esptool.exe
957aa8fa64f99be977eedf1b75f4bcab67392872 *esptool.exe

Without analyzing the code and compiling it yourself, it's impossible to be certain it's clean, but I haven't had a problem, and Windows Defender has not flagged it.

exeng

  • Sr. Member
  • ****
  • Posts: 454
Re: Norton keeps dumping esptool.exe on extraction
« Reply #2 on: August 09, 2016, 04:56:23 pm »
kh, Thanks. Matches and I went ahead and used it. Now if I could just figure out why I can't seem to get 1.0.5 (see my other recent thread) to work.

PeterF

  • Hero Member
  • *****
  • Posts: 881
Re: Norton keeps dumping esptool.exe on extraction
« Reply #3 on: August 09, 2016, 11:37:45 pm »
hm... looks like I need to update my esptool.exe ... mine is from Feb 2016 (making it the pre "32-bit compatible windows exe" and "fix missing serial module in esptool.exe" builds), so it has a different MD5/SHA checksum.

23/FEB/2016
MD5: daf40dd03c798c302f9b09fc968bf393
SHA1: 9593821b091113dacf91f3cdc946b874a65649e5

Edit: I just updated to the current version, and I get the same MD5 and SHA checksums. i.e.

8/APR/2016
MD5: dc22f4eba1c32676a1d2b16132d0552c
SHA1: 957aa8fa64f99be977eedf1b75f4bcab67392872
« Last Edit: August 09, 2016, 11:45:49 pm by PeterF »