We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
By default, most of our servers are disallowed to connect to internet. In that case, Yara rules update can't take place as required.
Could it be possible to include a fall back solution like the folling one to make the updater to point to an internal server:
static public void Main(String[] args) { var contentsUrl = $"https://api.github.com/repos/Neo23x0/Raccine/contents/yara?ref=main"; if(args.Length > 0) { contentsUrl = args[0]; } SyncContentFromUrl(contentsUrl, ""); }
This will allow us to specify an alternative URL directly on the command line
Probalbly an adaptation of the installation script will be required to ask for a value if required.
A better option will probably to rely on a config file with something like this :
if (File.Exists(appDir + @"\update.url")) { contentsUrl = File.ReadAllLines(appDir + @"\update.url")[0]; }
This file could then simply included in the folder while deploying.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
By default, most of our servers are disallowed to connect to internet. In that case, Yara rules update can't take place as required.
Could it be possible to include a fall back solution like the folling one to make the updater to point to an internal server:
This will allow us to specify an alternative URL directly on the command line
Probalbly an adaptation of the installation script will be required to ask for a value if required.
A better option will probably to rely on a config file with something like this :
This file could then simply included in the folder while deploying.
The text was updated successfully, but these errors were encountered: