search

wakatime / wakatime-cli

Command line interface used by all WakaTime text editor plugins
https://wakatime.com/plugins
BSD 3-Clause "New" or "Revised" License
262 stars 40 forks source link

Sign Windows binary with digital signature #817

Open IzStriker opened 1 year ago

IzStriker commented 1 year ago

I used to use WakaTime at work to track my programming time, however, the CLI tool kept getting flagged by security because it isn't signed. I would like to keep using the WakaTime service is it possible to sign the your CLI tool?

gandarez commented 1 year ago

What OS are you using? Would you share the report you got?

alanhamlett commented 1 year ago

Must be Windows.

Automatic Code-signing on Windows using GitHub Actions

IzStriker commented 1 year ago

Hi, yes it's Windows 11. I'll get you the full details when I'm at work tomorrow.

IzStriker commented 1 year ago

Hi, the exact reports I got from security were

hope you're well. We received an alert this morning that an unsigned software communicating externally to an api for a program called Wakatime. Is this regular behaviour for your device?

I'd expect that there may be other tools that could track this type of performance with the dev team, might be worth finding out if there is such a tool being used as our stance on unsigned Github software may change in the future.

Hi we have had an alert from your machine that "wakatime-cli-windows-amd64.exe" has been making connections to api.wakatime.com any idea what this is.  Many Thanks

IzStriker commented 1 year ago

Hi, is there a verdict on this request, are you willing you support this feature?

alanhamlett commented 1 year ago

Yes, we're working on getting a cert for signing Windows builds.

smladenoff commented 5 months ago

Hi all, I'd like to contribute to this issue as well. I'm on Win10 and AVG blocks wakatime-cli-windows-amd64.exe from running (stating "IDP.ARES.Generic") though does not detect when scanned, but here's the report from VT: https://www.virustotal.com/gui/file/f2d3bd662aaaa79abd5939cd5b20f0bfe982a6c97582762bc8e9de3d6d867bac (For the record, my other scanners: Immunet does not detect, nor does SpybotS&D, nor does Malwarebytes. EDIT: clarification)

I'm curious as to why some providers consider the file malicious. Any comments from the devs?