Comments (12)
Apologies for my ignorance, but what would be the point of adding a proxy if the emails are already disposable?
Some of my thoughts (I am not the dev) and several reasons that are quite straightforward:
- most obvious - anonymity (masking ip) against tracking by various endpoints related to eset and email providers. Maybe also for google/firefox telemetry, github (?), python telemetry (?)
- internet connections that work only through some proxy (eg. corporate/ school). though obviously, running such code through these networks could have consequences
- protection against isp filtering or state censorship
- protection against having your IP marked as spam/malicious by eset/ email providers
Now, if you run the code instead via github actions, you don't normally need to pass proxy to the keygen since MS IPs will be exposed instead. However, github/MS, ISP and even state actors including security organizations (3rd parties/ state sponsored/ state security) will (theoretically and if really determined) be able to track down that you run this code under your github account and under your specific IP provided by your ISP (with or without proxy in keygen). You'd have to always connect to github via proxy/vpn anonymously if you would really want to preserve your anonymity in this case.
A worthy note is that after applying the generated license in eset, your IP basically will be exposed to ESET with or without using a proxy anyway when generating the license (unless you mask your IP at Windows OS level through VPN/proxy). They could probably know that that particular generated trial license using disposable emails (even identified to be generated by this keygen by the way the eset account creation was performed) is used by your eset installation and will eventually be able to track and leak data to them about you (as an AV it has full admin permission and since it is not open source you cannot guarantee what exactly leaks about you). Theoretically they could also mark your installation as abusing (and maybe illegal or even contact police/ISP) and prevent you to use more trial licenses. I actually wonder why they don't have such mechanism in place, for a reputable AV they claim they are.
Ironically, another key point is that this project itself, will eventually force eset to use a more aggressive way of detecting abuse in the future, especially since they hold the advantage of them having proprietary code while the keygen being opensourced and more easily counterattacked.
The only way GitHub can track your keygen is using your Actions history in your account, cause IP addresses are common for all accounts. GitHub actions runners use dynamic IP addresses. So, VPN on GitHub won't do anything. So for true anonymity, use VPN on a real machine.
from eset-keygen.
Apologies for my ignorance, but what would be the point of adding a proxy if the emails are already disposable?
Some of my thoughts (I am not the dev) and several reasons that are quite straightforward:
- most obvious - anonymity (masking ip) against tracking by various endpoints related to eset and email providers. Maybe also for google/firefox telemetry, github (?), python telemetry (?)
- internet connections that work only through some proxy (eg. corporate/ school). though obviously, running such code through these networks could have consequences
- protection against isp filtering or state censorship
- protection against having your IP marked as spam/malicious by eset/ email providers
Now, if you run the code instead via github actions, you don't normally need to pass proxy to the keygen since MS IPs will be exposed instead. However, github/MS, ISP and even state actors including security organizations (3rd parties/ state sponsored/ state security) will (theoretically and if really determined) be able to track down that you run this code under your github account and under your specific IP provided by your ISP (with or without proxy in keygen). You'd have to always connect to github via proxy/vpn anonymously if you would really want to preserve your anonymity in this case.
A worthy note is that after applying the generated license in eset, your IP basically will be exposed to ESET with or without using a proxy anyway when generating the license (unless you mask your IP at Windows OS level through VPN/proxy). They could probably know that that particular generated trial license using disposable emails (even identified to be generated by this keygen by the way the eset account creation was performed) is used by your eset installation and will eventually be able to track and leak data to them about you (as an AV it has full admin permission and since it is not open source you cannot guarantee what exactly leaks about you). Theoretically they could also mark your installation as abusing (and maybe illegal or even contact police/ISP) and prevent you to use more trial licenses. I actually wonder why they don't have such mechanism in place, for a reputable AV they claim they are.
Ironically, another key point is that this project itself, will eventually force eset to use a more aggressive way of detecting abuse in the future, especially since they hold the advantage of them having proprietary code while the keygen being opensourced and more easily counterattacked.
from eset-keygen.
Yes, it makes perfect sense. In my view, it would be more sensible for the person executing the code to use a VPN. For instance, I use SoftEther on both my phone and PC, and I have other alternatives like TunnelBear and Proton. My point is, I believe it's the individual who uses the code that should take precautions. If they're already using such means to obtain passwords, it's obvious they engage in other activities. Therefore, it's the individual who should be cautious instead of incorporating it into the code. Does what I'm saying make sense?
ABSOLUTELY!!! And because of people's laziness I have to suffer)))))
from eset-keygen.
Могу попробовать добавить поддержку прокси без авторизации
from eset-keygen.
Не получается никак. С авторизацией - не работает, без нее тоже.
from eset-keygen.
Хм... я конечно не очень разбираюсь, но может это оно? https://www.zenrows.com/blog/selenium-proxy#proxy-authentication или тут https://pythonturbo.ru/selenium-with-proxy/
from eset-keygen.
Я это и пробовал делать. Но прокси листы в интернете какие-то странные у меня из всех никто не заработал. Вечно то ошибка туннелирования то сертификаты то ещё что-то
from eset-keygen.
you can use tor as proxy (tor expert bundle), no need to use public shitty proxies. this way you'll get real anonymity
https://www.torproject.org/download/tor/
create torrcProxy config file under TorExpertBundle\Data\
add to the new torrc config the lines:
DataDirectory FULL PATH TO TorExpertBundle\Data\ # should work relatively as well
SocksPort 50000
TorExpertBundle\Tor\tor.exe -f TorExpertBundle\Data\torrcProxy
in firefox set socks proxy localhost:50000 by whatever means (maybe with selenium proxy)
all traffic in firefox will go through tor network
Both eset and mailprovider seem to be allowed on tor
from eset-keygen.
Apologies for my ignorance, but what would be the point of adding a proxy if the emails are already disposable?
from eset-keygen.
Apologies for my ignorance, but what would be the point of adding a proxy if the emails are already disposable?
The eset website is blocked in some countries
from eset-keygen.
Apologies for my ignorance, but what would be the point of adding a proxy if the emails are already disposable?
Some of my thoughts (I am not the dev) and several reasons that are quite straightforward:
- most obvious - anonymity (masking ip) against tracking by various endpoints related to eset and email providers. Maybe also for google/firefox telemetry, github (?), python telemetry (?)
- internet connections that work only through some proxy (eg. corporate/ school). though obviously, running such code through these networks could have consequences
- protection against isp filtering or state censorship
- protection against having your IP marked as spam/malicious by eset/ email providers
Now, if you run the code instead via github actions, you don't normally need to pass proxy to the keygen since MS IPs will be exposed instead. However, github/MS, ISP and even state actors including security organizations (3rd parties/ state sponsored/ state security) will (theoretically and if really determined) be able to track down that you run this code under your github account and under your specific IP provided by your ISP (with or without proxy in keygen). You'd have to always connect to github via proxy/vpn anonymously if you would really want to preserve your anonymity in this case.
A worthy note is that after applying the generated license in eset, your IP basically will be exposed to ESET with or without using a proxy anyway when generating the license (unless you mask your IP at Windows OS level through VPN/proxy). They could probably know that that particular generated trial license using disposable emails (even identified to be generated by this keygen by the way the eset account creation was performed) is used by your eset installation and will eventually be able to track and leak data to them about you (as an AV it has full admin permission and since it is not open source you cannot guarantee what exactly leaks about you). Theoretically they could also mark your installation as abusing (and maybe illegal or even contact police/ISP) and prevent you to use more trial licenses. I actually wonder why they don't have such mechanism in place, for a reputable AV they claim they are.
Ironically, another key point is that this project itself, will eventually force eset to use a more aggressive way of detecting abuse in the future, especially since they hold the advantage of them having proprietary code while the keygen being opensourced and more easily counterattacked.
absolutely correct
from eset-keygen.
Yes, it makes perfect sense. In my view, it would be more sensible for the person executing the code to use a VPN. For instance, I use SoftEther on both my phone and PC, and I have other alternatives like TunnelBear and Proton. My point is, I believe it's the individual who uses the code that should take precautions. If they're already using such means to obtain passwords, it's obvious they engage in other activities. Therefore, it's the individual who should be cautious instead of incorporating it into the code. Does what I'm saying make sense?
from eset-keygen.
Related Issues (20)
- ESET-KeyGen_v1.4.3.0f4_win64.exe: error: one of the arguments --chrome --firefox --edge is required HOT 1
- error: one of the arguments --chrome --firefox --edge is required HOT 5
- error HOT 8
- GOOD JOB HOT 1
- doesn't work HOT 3
- pyperclip issue HOT 8
- процесс завершён с кодом выхода 100 HOT 10
- Eset small business security ? HOT 1
- Gmail HOT 2
- Firefox method error! HOT 9
- Obtaining the key and data from the account (login/pass) in which it was created HOT 6
- Test the project and update the test-date HOT 2
- Error HOT 17
- Doesn't work on Linux HOT 44
- привет Артём, форк ошибку 255 выдаёт HOT 14
- failing to run exe file HOT 12
- Implementing actions HOT 2
- error HOT 17
- Ошибка HOT 11
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eset-keygen.