From 34f9ff3f83dcab4a69955d4c6206230eb573729d Mon Sep 17 00:00:00 2001 From: Daniel Date: Thu, 27 Oct 2022 15:39:48 +0200 Subject: [PATCH] Add and improve data fetching and processing --- .gitignore | 24 +- _data/Makefile | 38 + _data/README.md | 29 +- _data/faq/all.json | 444 +++++++++++ _data/{faq-config.yml => faq/config.yml} | 2 + _data/{faq-data.json => faq/data.json} | 28 +- _data/releases/all.json | 902 +++++++++++++++++++++++ _data/releases/config.yml | 18 + _data/versions/beta.json | 39 + _data/versions/stable.json | 54 ++ 10 files changed, 1544 insertions(+), 34 deletions(-) create mode 100644 _data/Makefile create mode 100644 _data/faq/all.json rename _data/{faq-config.yml => faq/config.yml} (83%) rename _data/{faq-data.json => faq/data.json} (87%) create mode 100644 _data/releases/all.json create mode 100644 _data/releases/config.yml create mode 100644 _data/versions/beta.json create mode 100644 _data/versions/stable.json diff --git a/.gitignore b/.gitignore index 764ca05..a0a8e44 100644 --- a/.gitignore +++ b/.gitignore @@ -1,3 +1,17 @@ +# Custom + +!.gitkeep + +.rbenv-version +.rvmrc +.bundle +vendor/bundle +*.plist +.jekyll-cache/ + +_data/faq/src +_data/releases/src + # ---> macOS *.DS_Store .AppleDouble @@ -6,7 +20,6 @@ # Icon must end with two \r Icon - # Thumbnails ._* @@ -54,12 +67,3 @@ _theme_packages _res Thumbs.db - -!.gitkeep - -.rbenv-version -.rvmrc -.bundle -vendor/bundle -*.plist -.jekyll-cache/ diff --git a/_data/Makefile b/_data/Makefile new file mode 100644 index 0000000..5d65d5a --- /dev/null +++ b/_data/Makefile @@ -0,0 +1,38 @@ +# Fetch and process FAQs, releases and versions. + +.PHONY: faq-data releases-data versions-data clean + +all: faq/all.json releases/all.json versions-data + +update: clean all + +faq/all.json: faq-data + jq -s 'add | map({title, url, body}) | map(.keywords = (.body | capture("Keywords: (?[^\r\n]+)").c | split(", "))) | map(.categories = (.body | capture("Categories: (?[^\r\n]+)").c | split(", "))) | sort_by(.title)' faq/src/* > $@ + +faq-data: faq/src/portmaster.json faq/src/portmaster-ui.json faq/src/spn.json faq/src/faqs.json + +faq/src/%.json: + mkdir -p faq/src + cd faq/src + wget -O $@ "https://api.github.com/repos/safing/$*/issues?labels=faq&per_page=100" + +releases/all.json: releases-data + jq -s 'add | map({name, tag_name, body, prerelease, html_url, created_at}) | map(.date = .created_at[:10]) | map(.body = (.body | gsub("Changelog:"; "") | gsub("[a-f0-9]{40}"; "-"))) | map(.repo = (.html_url | capture("github.com/safing/(?[^/]+)/").repo)) | sort_by(.created_at) | reverse' releases/src/* > $@ + +releases-data: releases/src/portmaster.json releases/src/portmaster-ui.json releases/src/spn.json + +releases/src/%.json: + mkdir -p releases/src + cd faq/src + wget -O $@ "https://api.github.com/repos/safing/$*/releases" + +versions-data: versions/stable.json versions/beta.json + +versions/%.json: + cd versions + wget -O $@ "https://updates.safing.io/$*.v2.json" + +clean: + rm -f faq/src/* + rm -f releases/src/* + rm -f versions/* diff --git a/_data/README.md b/_data/README.md index d66cfa5..639c2fe 100644 --- a/_data/README.md +++ b/_data/README.md @@ -1,36 +1,25 @@ -# Data +# Sourced Data -### Update faq-data.json - -1. Check if the current list has new entries - - https://github.com/issues?q=archived%3Afalse+user%3Asafing+sort%3Aupdated-desc+label%3Afaq - -2. Get the current list with these commands (you might need to add new ones for additional repos) +### Update all data ``` -gh issue list --label faq --repo safing/portmaster --json title,url,body > faq-data.json -gh issue list --label faq --repo safing/portmaster-ui --json title,url,body >> faq-data.json +make update ``` -3. Fix JSON format. +### Create faq/all.json ``` -sed -i ':a;N;$!ba;s/\]\n\[/,/g;s/},{/},\n{/g;s/\[{/\[\n{/g;s/}\]/}\n\]/g' faq-data.json +make faq/all.json ``` -4. Sort and make pretty +### Create releases/all.json ``` -cat faq-data.json | jq 'sort_by(.title)' | tee faq-data.json +make releases/all.json ``` -Here is everything together: +### Create versions/* ``` -gh issue list --label faq --repo safing/portmaster --json title,url,body > faq-data.json && \ -gh issue list --label faq --repo safing/portmaster-ui --json title,url,body >> faq-data.json && \ -gh issue list --label faq --repo safing/spn --json title,url,body >> faq-data.json && \ -sed -i ':a;N;$!ba;s/\]\n\[/,/g;s/},{/},\n{/g;s/\[{/\[\n{/g;s/}\]/}\n\]/g' faq-data.json && \ -cat faq-data.json | jq 'sort_by(.title)' | tee faq-data.json +make versions-data ``` diff --git a/_data/faq/all.json b/_data/faq/all.json new file mode 100644 index 0000000..3276be3 --- /dev/null +++ b/_data/faq/all.json @@ -0,0 +1,444 @@ +[ + { + "title": "FAQ: Can I run Portmaster on a server?", + "url": "https://api.github.com/repos/safing/portmaster/issues/707", + "body": "Portmaster is currently built for desktops that have a physical graphical interface. That said, you can run Portmaster on a server if done correctly.\r\n\r\n### Backup Access\r\n\r\nIf in any way possible make sure and _test_ your backup access to the server in case you lock yourself out.\r\n\r\n### Prepare Config File\r\n\r\nWe'll need to write our config file ourselves and place it on the server before we install Portmaster so that we don't lock ourselves out. You can either use an existing Portmaster instance to configure your settings and then copy the `config.json` file from the data directory, or you can build it from scratch. Below is a template as a starting point. Now, let's go though the settings you want to change:\r\n\r\n- [API Listen Address](https://docs.safing.io/portmaster/settings#core/listenAddress)\r\n - By default, Portmaster only listens on localhost, change this to `0.0.0.0:817` to enable connections from anywhere.\r\n- [Incoming Rules](https://docs.safing.io/portmaster/settings#filter/serviceEndpoints)\r\n - You need to additionally allow from where connections to the Portmaster API are allowed. Scope this a narrow as possible.\r\n - We can't configure rules for applications in `config.json`, so we add only global rules for now and can switch to per-app after install.\r\n - (First add app rule, test, and then remove the global rule!)\r\n - Also, allow other management protocols so you can still access your server, such as SSH or RDP.\r\n- [Development Mode](https://docs.safing.io/portmaster/settings#core/devMode)\r\n - ⚠️ While Portmaster has support for [API Keys](https://docs.safing.io/portmaster/settings#core/apiKeys), these are not yet supported for logging into the UI. This means you will need to activate [Development Mode](https://docs.safing.io/portmaster/settings#core/devMode) for now, to allow access the the UI.\r\n- [Automatic Updates](https://docs.safing.io/portmaster/settings#core/automaticUpdates)\r\n - Portmaster uses automatic updates to stay up to date. Depending on your use case, this might not be what you want.\r\n - We haven't yet split the automatic update system into binaries and intelligence data, so disabling this will cut you off from intelligence data updates.\r\n - Until we have support for splitting this, you should manually update regularly by pressing the \"Download Updates\" button in tools menu.\r\n\r\nIf you run Portmaster on a private network you have access to, then this might be enough. If you want to access Portmaster via a public network, more caution and work is needed.\r\n\r\n⚠️ Portmaster does not support HTTPS for the UI. You will need to take care of this yourself. We recommend using something like [Traefik](https://traefik.io/) or [Caddy](https://caddyserver.com/) as a reverse proxy for automatic HTTPS.\r\n\r\n`config.json` template with multiple options - delete the ones you don't need:\r\n```\r\n{\r\n \"core\": {\r\n \"automaticUpdates\": false,\r\n \"devMode\": true,\r\n \"expertiseLevel\": \"developer\",\r\n \"listenAddress\": \"0.0.0.0:817\"\r\n },\r\n \"filter\": {\r\n \"serviceEndpoints\": [\r\n \"+ Localhost\",\r\n \"+ * TCP/SSH # Allow remote SSH access from anywhere\",\r\n \"+ * */3389 # Allow remote RDP access from anywhere\",\r\n \"+ * TCP/817 # Allow remote access to Portmaster from anywhere\",\r\n \"+ LAN TCP/817 # Allow remote access to Portmaster from LAN only\"\r\n ]\r\n }\r\n}\r\n```\r\n\r\nYou may also want to validate the json before using your config.\r\n\r\n### Place Config File\r\n\r\n_Before_ installing we need to place to config file:\r\n\r\n- Windows: `C:\\ProgramData\\Safing\\Portmaster\\config.json`\r\n- Linux: `/opt/safing/portmaster/config.json`\r\n\r\n### Install Portmaster\r\n\r\nThen, run the installer for Portmaster on the server. If everything went well, then you should still have access to your server and to the Portmaster UI in the way you configured.\r\n\r\n----\r\n\r\nKeywords: server, automatic updates, production, remote access, API, HTTP, authentication\r\n\r\nCategories: Compatibility", + "keywords": [ + "server", + "automatic updates", + "production", + "remote access", + "API", + "HTTP", + "authentication" + ], + "categories": [ + "Compatibility" + ] + }, + { + "title": "FAQ: Can community nodes see my traffic?", + "url": "https://api.github.com/repos/safing/spn/issues/108", + "body": "Community Nodes are servers not hosted by Safing, but by the Portmaster and SPN community. Except for one aspect, community nodes are treated exactly the same as nodes operated by Safing.\r\n\r\nThe only difference is, that network connections that are not encrypted by themselves, like plain HTTP, will never exit the network at community nodes. Instead, they exit the network at specially trusted servers, which are a subset of the servers operated by Safing.\r\n\r\nCommunity nodes will therefore never see any connection contents, as the connections are always encrypted for the destination server. This makes community nodes safe to use. Not only are they safe to use, but they are recommended, as they provide even better privacy due to more diverse server ownership in the nodes you use.\r\n\r\n---\r\n\r\nKeywords: exit node, traffic sniffing, connections\r\n\r\nCategories: SPN", + "keywords": [ + "exit node", + "traffic sniffing", + "connections" + ], + "categories": [ + "SPN" + ] + }, + { + "title": "FAQ: Default Settings for Incoming Connections CHANGED in v0.9.6", + "url": "https://api.github.com/repos/safing/portmaster/issues/886", + "body": "We have updated some default values for settings to make allowing incoming connections a lot easier:\r\n\r\nThe [Incoming Rules](https://docs.safing.io/portmaster/settings#filter/serviceEndpoints) now follow the [Default Network Action](https://docs.safing.io/portmaster/settings#filter/defaultAction) (default: allow), making them work the same as [Outgoing Rules](https://docs.safing.io/portmaster/settings#filter/endpoints). To still block incoming connections, [Force Block Incoming Connections](https://docs.safing.io/portmaster/settings#filter/blockInbound) is now enabled globally by default. You can easily create exceptions in app settings to allow incoming connections! Please review your settings.\r\n\r\nPreviously, you had to add a rule to the [Incoming Rules](https://docs.safing.io/portmaster/settings#filter/serviceEndpoints) in order to allow incoming connections, but this is non-trivial, as you had to first understand how rules work and written.\r\nIf you used rules in the past to allow incoming connections, these might now be blocked because of this change. In order to allow your incoming connections again, just head to the affected app and disable [Force Block Incoming Connections](https://docs.safing.io/portmaster/settings#filter/blockInbound) and everything should work as before.\r\n\r\nIf that happens to you, please also review your existing [Incoming Rules](https://docs.safing.io/portmaster/settings#filter/serviceEndpoints) and possibly restrict them by selecting \"Block everything else\" from the \"Quick Settings\" dropdown at the setting.\r\nAlternatively, you can easily block the network scopes that your app does not need with [Force Block Internet Access](https://docs.safing.io/portmaster/settings#filter/blockInternet) and [Force Block LAN](https://docs.safing.io/portmaster/settings#filter/blockLAN), which also apply to outgoing connections.\r\n\r\nPortmaster will also warn you once a week if you have disabled [Force Block Incoming Connections](https://docs.safing.io/portmaster/settings#filter/blockInbound) globally. So, just in case you configure Portmaster in a bad way, it will warn you about it.\r\n\r\n---\r\n\r\nKeywords: incoming, blocked, broken after update, as of version, inbound\r\n\r\nCategories: Privacy Filter\r\n", + "keywords": [ + "incoming", + "blocked", + "broken after update", + "as of version", + "inbound" + ], + "categories": [ + "Privacy Filter" + ] + }, + { + "title": "FAQ: Does Portmaster protect on startup?", + "url": "https://api.github.com/repos/safing/portmaster/issues/701", + "body": "Portmaster is registered as a system service and starts immediately at boot - even _before_ you log into your user account. This means that it generally starts before any other of your programs.\r\nPlease note that the tray icon / app indicator is a separate process and is _no indication_ for the Portmaster has started, as it is only started _after_ login.\r\n\r\nBesides that, there are some subtle differences depending your operating system:\r\n\r\n#### Windows\r\n\r\nThe Windows system service of Portmaster is started as a regular service. The service then initialized the kernel driver / extension to integrate into the network stack. This means that Portmaster is currently started after the boot process of the Window Kernel is completed.\r\n\r\nThis means that, currently, some Windows services have a short head start before Portmaster. Tests on Windows 11 have shown these services to be able to communicate before Portmaster is ready:\r\n- NetBIOS querying the network with a connection to `255.255.255.255 UDP/137`.\r\n- Connectivity check with a connection to `‎www.msftconnecttest.com`.\r\n\r\nFuture Improvement: After Portmaster has started for the first time, there will be an option to \"persist\" the Portmaster kernel driver, so that it is started with the kernel and blocks _all connectivity_ until the Portmaster is fully ready. This is tricky as it can _easily_ break your network connectivity or lead to a BSOD.\r\n\r\n#### Linux\r\n\r\nThe systemd service of the Portmaster is configured to be started before the network and name resolution. This means that the protection is started before the network connectivity is enabled:\r\n\r\n```\r\nBefore=nss-lookup.target network.target\r\n```\r\n\r\nFuture Improvement: After we have implemented direct support for systemd, we will be able to use the `WantedBy` configuration option, which will make systemd properly wait until the Portmaster has fully started before continuing with other services, mitigating any possibility of race conditions.\r\n\r\n---\r\n\r\nKeywords: boot, reboot, start, first, before, early, not yet, protect, enabled, started, everything else, anything else, block everything\r\n\r\nCategories: Starting and Stopping", + "keywords": [ + "boot", + "reboot", + "start", + "first", + "before", + "early", + "not yet", + "protect", + "enabled", + "started", + "everything else", + "anything else", + "block everything" + ], + "categories": [ + "Starting and Stopping" + ] + }, + { + "title": "FAQ: Does Portmaster support IPv6?", + "url": "https://api.github.com/repos/safing/portmaster/issues/778", + "body": "Portmaster has full IPv6 support.\r\n\r\n### Using IPv6 only\r\n\r\nIf you plan to use only IPv6 without IPv4, you'll need to configure IPv6 [DNS Servers](https://docs.safing.io/portmaster/settings#dns/nameservers) with the [DNS Configuration Guide](https://docs.safing.io/portmaster/guides/dns-configuration).\r\n\r\n### Disabling IPv6\r\n\r\n- Windows\r\n - Disabling IPv6 on the system is currently not supported on Windows, as the Portmaster Kernel Driver will try to interact with the IPv6 network stack.\r\n - You can block all IPv6 connections instead.\r\n- Linux\r\n - You can disable IPv6 in the network stack and restart Portmaster.\r\n - If Portmaster detects no IPv6 addresses at all, it will disable IPv6 integration.\r\n - Careful: DO NOT enable IPv6 again without also restarting Portmaster! You will NOT be protected!\r\n\r\n### Block all IPv6\r\n\r\nIn order to block all IPv6 connections, just add `Block ::/0` to both [Outgoing Rules](https://docs.safing.io/portmaster/settings#filter/endpoints) and [Incoming Rules](https://docs.safing.io/portmaster/settings#filter/serviceEndpoints).\r\n\r\n---\r\n\r\nKeywords: IP version 6, ip6, ipv6, network adapter, disabled, grub, configuration, break\r\n\r\nCategories: Compatibility", + "keywords": [ + "IP version 6", + "ip6", + "ipv6", + "network adapter", + "disabled", + "grub", + "configuration", + "break" + ], + "categories": [ + "Compatibility" + ] + }, + { + "title": "FAQ: How can I add my Discord ID to my Portmaster Account?", + "url": "https://api.github.com/repos/safing/portmaster/issues/936", + "body": "You can link your Discord ID to your Portmaster account in order to gain access to private channels as well as gaining the sweet user flair on all your posts:\r\n![image](https://user-images.githubusercontent.com/11504285/195292347-c895c904-f999-428a-b4f1-72776ac8cb57.png)\r\n\r\n### Get your Discord ID\r\nYour discord ID is NOT your user name, and most people have never seen it.\r\nWe might update the bot in the future to retrieve this ID automatically, but for now you will have to jump through some hoops to get your ID.\r\n**1. Go to settings**\r\n![image](https://user-images.githubusercontent.com/11504285/195293428-66ba2648-40d4-4d7c-b636-b1cd92b00b59.png)\r\n**2. Open Advanced**\r\n![image](https://user-images.githubusercontent.com/11504285/195293524-a40225f6-1199-4d0c-b7cc-7f550fe3d7c2.png)\r\n**3. Activate \"Developer Mode\"**\r\n![image](https://user-images.githubusercontent.com/11504285/195293614-f6515c35-bc55-4008-865c-5f7d33fa81bd.png)\r\n**4. \"Copy ID\" from your \"My Account\" Page**\r\n![image](https://user-images.githubusercontent.com/11504285/195293877-317257d1-442c-405a-9628-f72412db45b2.png)\r\n\r\n### Add your ID to your Portmaster Account\r\n\r\nAfter logging into your Portmaster Account at https://account.safing.io/:\r\n\r\n**1. Go to \"Account and Password**\r\n![image](https://user-images.githubusercontent.com/11504285/195294507-9de25198-7257-4924-acf0-6c5c0043b765.png)\r\n**2. Enter your Discord ID**\r\n![image](https://user-images.githubusercontent.com/11504285/195294778-1570d97b-d40a-4fda-805e-a4ec788d2b69.png)\r\n**3. Confirm Change with Password**\r\n![image](https://user-images.githubusercontent.com/11504285/195294941-1a25dc88-f4a5-44a8-be91-544ba1b6799d.png)\r\n\r\nThe update in Discord should be immediate.\r\nNote that Reddit can be filled out already but this feature is not available yet. \r\n\r\n---\r\n\r\nKeywords: Discord, Account, Flair, User,\r\n\r\nCategories: Guides, Account", + "keywords": [ + "Discord", + "Account", + "Flair", + "User," + ], + "categories": [ + "Guides", + "Account" + ] + }, + { + "title": "FAQ: How can I allow a blocked connection?", + "url": "https://api.github.com/repos/safing/portmaster/issues/706", + "body": "Portmaster is all about protecting your privacy. This also means that it may block something that you want to allow. Here's how you do it:\r\n\r\n## 1. Find the blocked connection in the Network Monitor\r\n\r\nBefore we can try to fix anything, we need to find the connection that is blocked in the Network Monitor. To do this, open the Portmaster App, which will start with the Network Monitor already open.\r\n\r\nThen, find the application that you are having trouble with. Sometimes applications are split into multiple sub-parts, so you might need to click around. If you see an application that has at least a little bit of a grey bar, it means that at least one connection is blocked:\r\n![image](https://user-images.githubusercontent.com/18184155/175247736-9961ea93-be13-4624-9278-76beba26f80d.png)\r\n\r\nIf you have found the application, open it and search for the blocked connection, which are marked with a red dot:\r\n![image](https://user-images.githubusercontent.com/18184155/175248225-5842969e-d603-4e0f-8d7a-815c115ee9ed.png)\r\n\r\nIf your connections are grouped in some way, again look out for the grey parts of the bar:\r\n![image](https://user-images.githubusercontent.com/18184155/175247736-9961ea93-be13-4624-9278-76beba26f80d.png)\r\n\r\nIf you found a connection that was blocked and looks like the one that you'd rather allow, continue to the next step:\r\n\r\n## 2. Find out why it is blocked\r\n\r\nTo get more information about the blocked connection, click on it to open the details:\r\n![image](https://user-images.githubusercontent.com/18184155/175249877-db0c0ff7-ec4e-41ad-916a-7c78f60f4544.png)\r\n\r\nIn addition to many other details (also depending on your [User Interface Mode](https://docs.safing.io/portmaster/settings#core/expertiseLevel)), you can see \"Applied Setting\" in the bottom left of this section.\r\nThis tells you which setting was responsible for blocking this connection.\r\n\r\n## 3. Allow the connection\r\n\r\nIn order to allow this connection, you now have two options:\r\n1. Add an exception for this connection (recommended), or\r\n2. Change the responsible setting\r\n\r\n### 3.1. Add an exception for this connection\r\n\r\nIn order to add an exception for this domain, just press the button at the bottom left of the connection section:\r\n![image](https://user-images.githubusercontent.com/18184155/175252873-b246c6a9-c326-4526-a946-537bca8c2d7a.png)\r\n\r\nIf you then go to the settings of the application, you will see that a new rule was added:\r\n![image](https://user-images.githubusercontent.com/18184155/175253147-4a692177-1de3-4cf5-90c6-7f4b6938ee66.png)\r\n\r\nIf the \"Allow Domain\" or \"Allow IP\" button is disabled, this means that an exception is not possible and that you must change the responsible setting:\r\n\r\n### 3.2. Change the responsible setting\r\n\r\nBefore you change the setting, you must decide whether you want to change the settings for this app only (recommended) or globally for all apps (which don't have this setting configured differently).\r\n\r\nPressing the corresponding button will take you to the responsible setting:\r\n![image](https://user-images.githubusercontent.com/18184155/175252694-7676ed7e-f356-46ff-a6fb-3847d857c0ef.png)\r\n\r\nHow to change the setting heavily depends on the setting itself, so the best way to go forward is to read the description by clicking on the (i) icon:\r\n![image](https://user-images.githubusercontent.com/18184155/175254095-1fc018b1-5451-4f71-a2b3-1113b9beec86.png)\r\n\r\nGenerally, we try to make all settings provide more protection by turning them \"on\", so in most cases turning off a setting will allow the connection.\r\n\r\nIn case there are multiple settings that block a connection, you might need to repeat this process.\r\n\r\n---\r\n\r\nKeywords: allow, exception, unbreak, unblock, not block, stop blocking, deny, denied, dropped, permit, connection, DNS request\r\n\r\nCategories: Guides, Privacy Filter", + "keywords": [ + "allow", + "exception", + "unbreak", + "unblock", + "not block", + "stop blocking", + "deny", + "denied", + "dropped", + "permit", + "connection", + "DNS request" + ], + "categories": [ + "Guides", + "Privacy Filter" + ] + }, + { + "title": "FAQ: How can I enable or disable the SPN for just one application?", + "url": "https://api.github.com/repos/safing/spn/issues/105", + "body": "Applications can easily be excluded from the SPN by either using the quick setting in the app page header, or in the settings:\r\n\r\n![image](https://user-images.githubusercontent.com/18184155/187927360-3f1290d2-a4da-45d9-aa33-3f65f46bd1cf.png)\r\n\r\nor\r\n\r\n![image](https://user-images.githubusercontent.com/18184155/187927728-3197860c-f04d-45d8-ad96-70d642f0f8e4.png)\r\n\r\n---\r\n\r\nKeywords: route, routing, not go through, enable, disable, exclude, include, decide, connection, tunnel\r\n\r\nCategories: SPN", + "keywords": [ + "route", + "routing", + "not go through", + "enable", + "disable", + "exclude", + "include", + "decide", + "connection", + "tunnel" + ], + "categories": [ + "SPN" + ] + }, + { + "title": "FAQ: How can I exclude a Domain or IP address from the SPN?", + "url": "https://api.github.com/repos/safing/spn/issues/104", + "body": "You can easily exclude any Domain or IP address from the SPN by using the [SPN Rules](https://docs.safing.io/portmaster/settings#spn/usagePolicy). It is a rule list similar to the others and applies the first entry that matches.\r\n\r\n![image](https://user-images.githubusercontent.com/18184155/187923583-c5392177-9ffa-4ad8-a53a-fd4061237878.png)\r\n\r\n---\r\n\r\nKeywords: route, routing, not go through, enable, disable, exclude, include, decide, connection, tunnel\r\n\r\nCategories: SPN", + "keywords": [ + "route", + "routing", + "not go through", + "enable", + "disable", + "exclude", + "include", + "decide", + "connection", + "tunnel" + ], + "categories": [ + "SPN" + ] + }, + { + "title": "FAQ: How can I exclude the Local Network (LAN) from the SPN?", + "url": "https://api.github.com/repos/safing/spn/issues/106", + "body": "The Local Network (LAN) is always excluded from the SPN, as servers in the SPN cannot access your local network.\r\n\r\nVPNs do not differentiate between networks without special configuration.\r\n\r\n---\r\n\r\nKeywords: route, routing, not go through, enable, disable, exclude, include, decide, connection, tunnel\r\n\r\nCategories: SPN", + "keywords": [ + "route", + "routing", + "not go through", + "enable", + "disable", + "exclude", + "include", + "decide", + "connection", + "tunnel" + ], + "categories": [ + "SPN" + ] + }, + { + "title": "FAQ: How can I host a community node?", + "url": "https://api.github.com/repos/safing/spn/issues/109", + "body": "Have a look at this guide: [Hosting a Community Node](https://docs.safing.io/spn/hosting-a-community-node)\r\n\r\n---\r\n\r\nKeywords: community, node, server, hosting, run, share\r\n\r\nCategories: SPN\r\n", + "keywords": [ + "community", + "node", + "server", + "hosting", + "run", + "share" + ], + "categories": [ + "SPN" + ] + }, + { + "title": "FAQ: How do Broadcast Notifications work?", + "url": "https://api.github.com/repos/safing/portmaster/issues/703", + "body": "Broadcast Notifications are messages broadcasted by the Portmaster Developers and Team to all Portmaster users. We use this to alert users of important updates, breaking feature changes, privacy related issues, among others.\r\n\r\nAll notifications are publicly added to [the source file](https://github.com/safing/intel-data/blob/master/portmaster/notifications.yaml) and then distributed to all Portmaster instances via our update system. Safing (the company behind Portmaster) learns nothing about the Portmaster instances themselves. No data is ever sent.\r\n\r\nRather, when your Portmaster downloads the newest broadcast notifications - alongside the filter list updates, for example - it checks if there are any broadcast notifications that were not shown yet _and_ that match certain criteria. This way we can show notifications only to those who are affected by a situation and keep the noise low for all others. The matching is always done locally and the matching data is never sent anywhere.\r\n\r\n---\r\n\r\n#### Deep Dive\r\n\r\nIf you really want to get into it, you can check out which data we use to match broadcast notifications on your device.\r\nEnable the [Development Mode](https://docs.safing.io/portmaster/settings#core/devMode) and then open http://127.0.0.1:817/api/v1/broadcasts/matching-data in your browser. This is exactly the same information as the broadcast notifications use.\r\n\r\n---\r\n\r\nKeywords: matching, information, sharing, leak, sending, privacy, private, data\r\n\r\nCategories: Other", + "keywords": [ + "matching", + "information", + "sharing", + "leak", + "sending", + "privacy", + "private", + "data" + ], + "categories": [ + "Other" + ] + }, + { + "title": "FAQ: How do I make my VPN or other software compatible with Portmaster?", + "url": "https://api.github.com/repos/safing/portmaster/issues/708", + "body": "Portmaster deeply integrations into the network stack of your operating system in order to protect your privacy. Sometimes this can lead to problems with other software, especially VPNs.\r\n\r\nIn addition to this guide, we also [maintain a list of compatible VPNs](https://docs.safing.io/portmaster/install/status/vpn-compatibility) and [other software](https://docs.safing.io/portmaster/install/status/software-compatibility) that you can check. Some also have dedicated instructions to get them to work.\r\n\r\nNot every VPN or software will be able to work with Portmaster. See the _Limits_ section below for details on this.\r\n\r\n## Allow Connections\r\n\r\nFirst, find the VPN software in the Network Monitor in the Portmaster App and make sure all connections it makes are allowed. If you get it working, you can still block connections again to see if it can work without them.\r\n\r\nIf you don't know how to allow blocked connections, please follow this guide: https://github.com/safing/portmaster/issues/706\r\n\r\nBefore you continue, please check if your VPN or software works now. Only continue, if it does not.\r\n\r\n## Disable Seamless DNS Integration\r\n\r\nPortmaster takes great care not to break your system and as such does not make permanent changes to the network stack of your system: https://github.com/safing/portmaster/issues/702\r\n\r\nRather, in order to still seamlessly integrate, Portmaster redirects connections - mostly DNS queries - where they need to go. This can interfere with VPNs or other software that tries to do the same.\r\n\r\nIf you can disable your VPN's behavior of this, then this is recommended. If that is not possible, you can disable [Seamless DNS Integration](https://docs.safing.io/portmaster/settings#filter/dnsQueryInterception) in Portmaster. To do this, you have to:\r\n\r\n- enter the Development Interface through the [UI Mode](https://docs.safing.io/portmaster/settings#core/expertiseLevel) in the settings\r\n- set your [Feature Stability](https://docs.safing.io/portmaster/settings#core/releaseLevel) to \"Experimental\"\r\n\r\n---\r\n\r\n⚠️ If you disable [Seamless DNS Integration](https://docs.safing.io/portmaster/settings#filter/dnsQueryInterception) in Portmaster, you will need to take care of the system integration yourself!\r\n\r\n---\r\n\r\nThis means that you will need to configure the DNS server in your operating system **AND** the VPN to point to the Portmaster:\r\n- Windows: `127.0.0.1`\r\n- Linux: `127.0.0.17`\r\n\r\nPortmaster does periodic self-checks and will warn you when the integration is broken. Checks are not done so often, so they take a while to appear and to disappear.\r\n \r\nIf you want faster results for the self-check and you're experienced with computers, you can:\r\n\r\n- enter the Development Interface through the [UI Mode](https://docs.safing.io/portmaster/settings#core/expertiseLevel) in the settings\r\n- enable the [Development Mode](https://docs.safing.io/portmaster/settings#core/devMode) \r\n- open this page in your browser: http://127.0.0.1:817/api/v1/compat/self-check\r\n\r\n## Workaround\r\n\r\nIf the previous steps have not worked - or you were not confident enough to attempt them - you can try to use a generic VPN client instead of the custom application by the VPN provider.\r\n\r\nWe suggest you check if you can download an [OpenVPN client configuration or connection profile](https://openvpn.net/faq/what-is-a-client-configuration-or-connection-profile/) from your VPN. Then, [install OpenVPN](https://openvpn.net/vpn-client/) and load the supplied profile.\r\n\r\n## Report Findings\r\n\r\nIf you followed this guide and either succeeded or failed in making your VPN or software compatible, it would be great if you could report this [using this GitHub Issue template](https://github.com/safing/portmaster/issues/new?assignees=&labels=in%2Fcompatibility&template=report-compatibility.md)!\r\n\r\n## Limits\r\n\r\n### Windows\r\n\r\nPortmaster on Windows uses a kernel driver / extension in order to integrate into the network stack. Depending on how other software integrates into the network stack, there might be an unavoidable collision. Please open an issue.\r\n\r\n### Linux\r\n\r\nPortmaster on Linux uses packet and connection marks to save decisions to the network state. Other software using the same will interfere and it and Portmaster will break each other. This can only be fixed if the other software can be made to not use packet and connection marks.\r\n\r\n---\r\n\r\nKeywords: VPN, Anti-Virus, protection, kernel, extension, no internet, broken, OpenVPN, profile, configuration\r\n\r\nCategories: Compatibility", + "keywords": [ + "VPN", + "Anti-Virus", + "protection", + "kernel", + "extension", + "no internet", + "broken", + "OpenVPN", + "profile", + "configuration" + ], + "categories": [ + "Compatibility" + ] + }, + { + "title": "FAQ: How do I share debug information and logs?", + "url": "https://api.github.com/repos/safing/portmaster/issues/705", + "body": "First of all, thanks a lot for contributing! You're probably reading this because you've been directed here and were asked to provide one of the following:\r\n\r\n- Debug Info\r\n- Logs\r\n- (Debug Logs)\r\n\r\n## Debug Info\r\n\r\nThe debug information is a collection of helpful snippets of information that Portmaster produces itself.\r\nOften, you will be asked to collect this information _while_ the reported issue is occurring. This is important, as the data is gathered live from the current state of Portmaster and will help us to see what the problem is.\r\n\r\nIf you're experiencing a problem with a certain application, it can be very helpful to copy the application-specific version of the Debug Info. This is only (easily) possible using the \"Application Page\" method explained later.\r\n\r\nWe've taken care to include as little personal information as possible in the Debug Info. You can further reduce this information by restarting the Portmaster before copying the data - if you can reproduce the issue that way too.\r\nYou are of course also free to delete parts of the data before submitting - in that case please mark the areas you have deleted with `[DELETED]`, so we know that information is missing.\r\n\r\nThere are multiple ways to acquire and share the Debug Info:\r\n\r\n### Settings Page\r\n\r\nJust click on \"Copy Debug Information\" button on the top right of the settings page.\r\nThis copies the Debug Info to your clipboard. You can paste this directly into a Github Issue - it is automatically formatted using sections. It looks ugly in text format, but if you click on the \"Preview\" tab of your comment, you will see it nicely rendered.\r\n\r\n![image](https://user-images.githubusercontent.com/18184155/175050614-1b30d836-39e5-463c-9a37-8dae978d9f6a.png) >>> ![image](https://user-images.githubusercontent.com/18184155/175055501-f8aea6bc-41b5-4856-90b4-315596c262a4.png)\r\n\r\n\r\n### Application Page\r\n\r\nFind the affected application in the Portmaster App, then go to the \"Details\" tab and click on \"Copy Debug Information\" at the end of the page.\r\nThis copies the Debug Info to your clipboard. You can paste this directly into a Github Issue - it is automatically formatted using section. It looks ugly in text format, but if you click on the \"Preview\" tab of your comment, you will see it nicely rendered.\r\n\r\n![image](https://user-images.githubusercontent.com/18184155/175054075-0e803c67-fc54-405e-9d54-3890e7e1980a.png)\r\n\r\n### Privately Via Ticket\r\n\r\nAlternatively, you can submit the Debug Info privately via a support ticket. To do this:\r\n\r\n- Open the Portmaster App\r\n- Go to the Get Help page using the question mark button on the navigation bar on the left\r\n- Then, click on \"__Report Bug__\", and enter the following information:\r\n - Title: \"__Debug Info for Issue__\"\r\n - What Happend: Enter the __Ticket ID or Github Issue URL__.\r\n- Then click on \"Send Private Ticket\" on the bottom of the page.\r\n - You don't need to provide an email.\r\n- Notify the thread where you were asked to send the Debug Info that you've sent it.\r\n\r\n### Using cURL\r\n\r\nIf you're a Linux user, you might want to get this data directly to your terminal. You can do this with the following command - and maybe pipe it to your clipboard to a file.\r\n\r\n```\r\ncurl http://127.0.0.1:817/api/v1/debug/core\r\n```\r\n\r\nYou can find the documentation of the API endpoints here:\r\n- [Get Debug Information](https://docs.safing.io/portmaster/api#v1/debug/core)\r\n- [Get Network Debug Information](https://docs.safing.io/portmaster/api#v1/debug/network)\r\n\r\n## Logs\r\n\r\nPortmaster writes logs for all components. Logs are written in different levels to reduce sensitive information in logs and keep them in a manageable size. They are also automatically deleted after some time. \r\nYou may have been asked to change the [Log Level](https://docs.safing.io/portmaster/settings#core/log/level) before submitting the logs.\r\n\r\nPlease always provide the newest `.log` and `.error.log` files during which the reported issues occurred. \r\nYou can find the log files here:\r\n\r\nDefault Log File Locations:\r\n- Windows\r\n - Core Logs: `C:\\ProgramData\\Safing\\Portmaster\\logs\\core`\r\n - App Logs: `C:\\ProgramData\\Safing\\Portmaster\\logs\\app`\r\n - Notifier Logs: `C:\\ProgramData\\Safing\\Portmaster\\logs\\notifier`\r\n - Start Logs: `C:\\ProgramData\\Safing\\Portmaster\\logs\\start`\r\n- Linux\r\n - Core Logs: `/opt/safing/portmaster/logs/core`\r\n - App Logs: `/opt/safing/portmaster/logs/app`\r\n - Notifier Logs: `/opt/safing/portmaster/logs/notifier`\r\n - Start Logs: `/opt/safing/portmaster/logs/start`\r\n\r\nWe recommend that you upload these files to your favorite [pastebin/privatebin](https://privatebin.info/directory/) or use [our instance](https://support.safing.io/privatebin/) and add a 1-3 months expiration.\r\n\r\n## (Debug Logs)\r\n\r\nIn the past, \"Debug Logs\" has sometimes been used in conversations, but it does not clearly specify what is meant. If you are asked for this, please ask what exactly you should provide.\r\n\r\n---\r\n\r\nKeywords: collect, get, copy, extract, debugging, debug-info, debug-data, investigating, logging, logs, log-lines, record\r\n\r\nCategories: Guides", + "keywords": [ + "collect", + "get", + "copy", + "extract", + "debugging", + "debug-info", + "debug-data", + "investigating", + "logging", + "logs", + "log-lines", + "record" + ], + "categories": [ + "Guides" + ] + }, + { + "title": "FAQ: Notifications not available on Windows 7 and 8", + "url": "https://api.github.com/repos/safing/portmaster-ui/issues/361", + "body": "We use the notification system that was added in Windows 10, as it supports actions (ie. has buttons). Windows 7 and 8 do not have any support for these buttons.\r\n\r\nNotifications may still work to some extent, but prompts will not. Please disable [Prompt Desktop Notifications](https://docs.safing.io/portmaster/settings#filter/askWithSystemNotifications).\r\n\r\n---\r\n\r\nKeywords: broken, cannot click, can't press, missing button, Microsoft\r\n\r\nCategories: Windows", + "keywords": [ + "broken", + "cannot click", + "can't press", + "missing button", + "Microsoft" + ], + "categories": [ + "Windows" + ] + }, + { + "title": "FAQ: Portmaster Core Does Not Start at Boot", + "url": "https://api.github.com/repos/safing/portmaster/issues/956", + "body": "Some users report that the Portmaster Core Service will not start at boot, although it is configured to do so. If that is the case, you can check its status in the \"Services\" Desktop App. There, search for the Service \"Portmaster Core\" and inspect and start it as needed.\r\n\r\n---\r\n\r\nKeywords: starting, boot, startup, automatic\r\n\r\nCategories: Windows, Starting and Stopping\r\n", + "keywords": [ + "starting", + "boot", + "startup", + "automatic" + ], + "categories": [ + "Windows", + "Starting and Stopping" + ] + }, + { + "title": "FAQ: Portmaster Fails to Restart", + "url": "https://api.github.com/repos/safing/portmaster/issues/955", + "body": "In some cases the Portmaster will fail to restart, because the Portmaster Kernel Extensions cannot be loaded and returns the error code `0x422`.\r\nThis stems from a known issue in Windows, where system services are not completely removed when something is monitoring the system services.\r\nWhen the Portmaster restarts, it is then unable to initialize the Kernel Extension, because the system thinks it is still unloading.\r\n\r\nIf you experience this issue, please follow this workaround:\r\n\r\n_Quoting from _\r\n\r\n> There may be several causes which lead to the service being stuck in “marked for deletion”.\r\n>\r\n> 1. [SysInternals' Process Explorer is opened](http://blog.cyotec.com/2011/05/specified-service-has-been-marked-for.html). Closing it should lead to automatic removal of the service.\r\n>\r\n> 1. [Task Manager is opened](https://stackoverflow.com/questions/20561990/how-to-solve-the-specified-service-has-been-marked-for-deletion-error/21310096#comment32672750_20565337).\r\n>\r\n> 1. [Microsoft Management Console (MMC) is opened](https://stackoverflow.com/a/8529760/240613). To ensure all instances are closed, run `taskkill /F /IM mmc.exe`.\r\n>\r\n> 1. [Services console is opened](https://stackoverflow.com/a/21310096/240613). This is the same as the previous point, since Services console is hosted by MMC.\r\n>\r\n> 1. [Event Viewer is opened](https://stackoverflow.com/a/18467128/240613). Again, this is the same as the third point.\r\n> \r\n> 1. [The key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\\\{service name} exists](https://stackoverflow.com/a/2804099/240613).\r\n>\r\n> 1. [Someone else is logged into the server](https://stackoverflow.com/a/28632820/240613) and has one of the previously mentioned applications opened.\r\n>\r\n> 1. An instance of Visual Studio *used to debug the service* is open.\r\n\r\n---\r\n\r\nKeywords: error code, restarting, boot\r\n\r\nCategories: Windows, Starting and Stopping\r\n", + "keywords": [ + "error code", + "restarting", + "boot" + ], + "categories": [ + "Windows", + "Starting and Stopping" + ] + }, + { + "title": "FAQ: What changes does Portmaster make to my system?", + "url": "https://api.github.com/repos/safing/portmaster/issues/702", + "body": "#### Most Important\r\n\r\n- Portmaster does not do any permanent changes to your network configuration:\r\n - No network interfaces are added or changed.\r\n - No routing entries are added or changed.\r\n - No DNS server configuration is added or changed.\r\n- Required integration is done \"on-the-fly\" by redirecting packets.\r\n- When Portmaster is shut down or uninstalled, all (volatile) network integration is removed automatically.\r\n - When you still experience issues, check out #699.\r\n\r\nBesides that, changes vary depending on your operating system:\r\n\r\n#### Windows\r\n\r\n- All data is saved to `C:\\ProgramData\\Safing\\Portmaster` by default.\r\n- A system service is registered and marked to start automatically at boot.\r\n- Application entry for the Portmaster UI is added.\r\n- Application entry for the Portmaster Tray Notifiier is added and marked to start automatically at login.\r\n- Uninstall information is placed in the registry.\r\n- Read more at [Docs: Install on Windows](https://docs.safing.io/portmaster/install/windows)\r\n\r\n#### Linux\r\n\r\n- All data is saved to `/opt/safing/portmaster` by default.\r\n- Portmaster adds iptables entries on start and removes them when stopped.\r\n - This integration makes use of packet and connection marks, which likely makes Portmaster incompatible with other software attempting the same.\r\n- A systemd service file is placed at `/etc/systemd/system/portmaster.service`.\r\n- `.desktop` files are placed in `/usr/share/applications/`.\r\n- Icon is placed in `/usr/share/pixmaps/`.\r\n- Read more at [Docs: Install on Linux](https://docs.safing.io/portmaster/install/linux)\r\n\r\n---\r\n\r\nKeywords: change, modify, modification, integration, settings, registry, file, config, configuration, mess with, break\r\n\r\nCategories: Starting and Stopping", + "keywords": [ + "change", + "modify", + "modification", + "integration", + "settings", + "registry", + "file", + "config", + "configuration", + "mess with", + "break" + ], + "categories": [ + "Starting and Stopping" + ] + }, + { + "title": "FAQ: Where is the tray icon / app indicator in GNOME?", + "url": "https://api.github.com/repos/safing/portmaster-ui/issues/242", + "body": "GNOME 3.26 [removed the default tray icon support](https://blogs.gnome.org/aday/2017/08/31/status-icons-and-gnome/).\r\n\r\nYou'll need to install an extension that adds support for status / app indicators.\r\nWe recommend this one maintained by Ubuntu / Canonical Ltd.:\r\n- Repo: https://github.com/ubuntu/gnome-shell-extension-appindicator\r\n- Extension Page: https://extensions.gnome.org/extension/615/appindicator-support/\r\n\r\n---\r\n\r\nKeywords: tray, icon, indicator, libappindicator, libnotify, org.kde.StatusNotifierWatcher, missing, not visible, does not appear\r\n\r\nCategories: Compatibility", + "keywords": [ + "tray", + "icon", + "indicator", + "libappindicator", + "libnotify", + "org.kde.StatusNotifierWatcher", + "missing", + "not visible", + "does not appear" + ], + "categories": [ + "Compatibility" + ] + }, + { + "title": "FAQ: Why does Portmaster keep blocking connections after I close it?", + "url": "https://api.github.com/repos/safing/portmaster/issues/719", + "body": "Portmaster is not just one process, but consists of multiple parts:\r\n\r\n- Portmaster Core Service: A system service started by your operating system.\r\n- Portmaster Tray Notifier: A small icon living in your status and notification tray.\r\n- Portmaster UI: The app you open.\r\n\r\nIf you close the app, you only close your \"window\" into what Portmaster (the Core Service) is currently doing.\r\nIn order to fully shut down Portmaster and have it stop blocking anything, you must select the option in either the app or the tray:\r\n\r\nUI - Settings Page:\r\n![image](https://user-images.githubusercontent.com/18184155/176720125-8769ad3a-a99a-4bfe-a194-37ea344042e7.png)\r\n\r\nTray Icon:\r\n![image](https://user-images.githubusercontent.com/18184155/176720369-f71391fb-3428-4cb3-ac23-f6b429324bd7.png)\r\n\r\nWhen you close the app for the first time, it clarifies what is and is not happening when closing the app.\r\n\r\nRead more about the architecture of Portmaster [on our docs](https://docs.safing.io/portmaster/architecture/overview).\r\n\r\n---\r\n\r\nKeywords: closing, shut down, shutting down, exit, minimize, blocking, completely, disable\r\n\r\nCategories: Privacy Filter", + "keywords": [ + "closing", + "shut down", + "shutting down", + "exit", + "minimize", + "blocking", + "completely", + "disable" + ], + "categories": [ + "Privacy Filter" + ] + }, + { + "title": "FAQ: Why does Portmaster send plain/unencrypted DNS queries?", + "url": "https://api.github.com/repos/safing/portmaster/issues/700", + "body": "Portmaster takes care of protecting your DNS queries by becoming the gateway for all DNS queries on your system and then sending them through an encrypted connection to the configured DNS server.\r\n\r\nIf you are using a DNS server for your network that has a dashboard, or if the DNS service you are using discerns between encrypted and non-encrypted queries, you might notice that sometimes Portmaster sends unencrypted queries.\r\n\r\nIn order to understand why that is necessary, let's take a look at a common network structure: A free __WiFi access point in a café__ or airport. Usually these can only be used when you __accept their Terms of Service__. In order for you to get you to read them, the network needs to somehow redirect to that.\r\nThis __needs to work even if the secure DNS server are unreachable__ - as you've not yet \"logged into\" the free network.\r\n\r\nThis is why Portmaster always __sends a handful of special domains__ - used by operating systems and browsers - __as plain DNS queries to the DNS server provided by the network__. You can find the current list of these domains [in the docs](https://docs.safing.io/portmaster/architecture/core-service/secure-dns/#connectivity-domains) or in the [source code as \"Connectivity Domains\")](https://github.com/safing/portmaster/blob/f135ec3242905b84811b26975a3458117cc2c28e/netenv/online-status.go#L53).\r\n\r\nIf you don't want these queries to go out, you can block them by enabling the setting [Ignore System/Network Servers](https://docs.safing.io/portmaster/settings#dns/noAssignedNameservers) or [Use Secure Protocols Only](https://docs.safing.io/portmaster/settings#dns/noInsecureProtocols). Please consider the side effects of enabling these settings when you do so.\r\n\r\nThe Portmaster will also attempt to detect these \"Captive Portals\" and will notify you if it finds one.\r\n\r\n---\r\n\r\nFor the time being there is also another possibility why this can happen. To make sure everything works as expected, we enabled Portmaster to fall back to the system assigned DNS servers in case all the configured DNS server failed. This is to ensure that we don't break the workflow when installing Portmaster.\r\nWe are working on a solution how to best handle this in a way that does not break setups and provides the best privacy. This is internally tracked at CC#2405.\r\n\r\n---\r\n\r\nKeywords: unencrypted query, DNS leaks, not sent, DHCP, system assigned.\r\n\r\nCategories: Leaks", + "keywords": [ + "unencrypted query", + "DNS leaks", + "not sent", + "DHCP", + "system assigned." + ], + "categories": [ + "Leaks" + ] + }, + { + "title": "FAQ: Why does the DNS Leak test say that I have a leak?", + "url": "https://api.github.com/repos/safing/portmaster/issues/720", + "body": "Leaks test are always built for a specific service. If a leak test says you are \"leaking\", it means that your device is not configured exactly as _they expect_. If you are using Portmaster, this is most probably the case.\r\n\r\nThe easiest thing you can do is to take the IP addresses the leak test says you are leaking and enter them on this page: https://bgpview.io/\r\n\r\nThis will tell you who the IP address belongs to. __As long as this is _not_ your ISP, all is good.__\r\n\r\nSometimes you can even try to just enter the IP address in your browser and see where it leads to. Many services have small web pages set up so interested network administrators can check what the IP address is used for.\r\n\r\nIf you are confident that you are experiencing a real leak of any kind, please report it and include the following information:\r\n- The software or website you used for the test\r\n- Any leaked IP addresses (that are not yours)\r\n- Any leaked domain names / dns queries\r\n\r\n---\r\n\r\nKeywords: dns, ip, leak, leaking, VPN, not contained, astray\r\n\r\nCategories: Leaks", + "keywords": [ + "dns", + "ip", + "leak", + "leaking", + "VPN", + "not contained", + "astray" + ], + "categories": [ + "Leaks" + ] + }, + { + "title": "FAQ: Why does the SPN not connect?", + "url": "https://api.github.com/repos/safing/spn/issues/107", + "body": "When Portmaster connects to the SPN und normal circumstances, it does not depend on a single server or on DNS. It can directly try all servers to find one it can connect to.\r\n\r\nIf you are connecting to the SPN for the first time, Portmaster downloads a set of IPs from the update server in order to bootstrap into the network. After that, it only connects directly to the network.\r\n\r\n### Troubleshooting\r\n\r\nHere are things you can try when Portmaster does not successfully connect to the SPN:\r\n\r\n#### 1. Check if your Internet connection works.\r\n\r\nDisable SPN and check if you can connect to the Internet without the SPN.\r\n\r\n#### 2. Check for Portmaster Updates.\r\n\r\nSometimes there are changes to the SPN servers that also require Portmaster to update. We wait some time to allow clients to update before deploying breaking changes, but you might just be behind too much.\r\n\r\n![image](https://user-images.githubusercontent.com/18184155/187939384-181f5fa0-fa70-4fd6-b3c8-e0e9e7d98db7.png)\r\n\r\n#### 3. Re-Initialize\r\n\r\nIf none of these resulted in a successful connection to the SPN, you can also clear all caches regarding the SPN and re-initialize it.\r\n\r\n![image](https://user-images.githubusercontent.com/18184155/187939868-ad73fc9e-89de-44ef-b0c5-947a2605ed75.png)\r\n\r\n#### 4. Ask for Help\r\n\r\nIf none of these steps could resolve your issue, please reach out to use and we will investigate the issue. Be sure to open the Bug Report page in the Portmaster _while_ it is trying to connect to the SPN, so that we have the correct data for analysis.\r\n\r\n---\r\n\r\nKeywords: connection, fails, failed, try, retry, trying, timeout, disconnect, unable, blocked\r\n\r\nCategories: SPN\r\n", + "keywords": [ + "connection", + "fails", + "failed", + "try", + "retry", + "trying", + "timeout", + "disconnect", + "unable", + "blocked" + ], + "categories": [ + "SPN" + ] + }, + { + "title": "FAQ: Why is my Internet or Network Access broken after shutdown or uninstall?", + "url": "https://api.github.com/repos/safing/portmaster/issues/699", + "body": "While Portmaster integrates deeply into the network stack of your operating system, all of it is volatile - meaning that it is automatically removed when Portmaster shuts down or when Portmaster is uninstalled.\r\n\r\nHowever, there are special cases where you might loose Internet or network connectivity after shutting down or uninstalling Portmaster.\r\n\r\n### 1. DNS Configuration Issues\r\n\r\nPortmaster becomes the gateway for all DNS queries when you install it, but it does not configure itself as your DNS server in the system. Rather, it does a _soft_ integration by redirecting all DNS queries to itself.\r\n\r\nWhat can happen is that at some point - while Portmaster is installed - the DNS configuration of your system is changed or corrupted into a state that does not work. But because Portmaster is installed, it will seamlessly fix it for you, because it \"corrects\" all queries.\r\nWhen you then shutdown or uninstall Portmaster this \"fix\" is removed and you end up with a broken DNS configuration.\r\n\r\n__Please review the DNS configuration of your system.__ When in doubt, set it to _automatic_ or _DHCP_.\r\n\r\n### 2. Network Stack Issues by the Operation System\r\n\r\nIn some more extreme cases, the system might not correctly remove the integration as it should.\r\n\r\n#### Windows\r\n\r\nPortmaster marks all its network stack integrations (the Firewall Driver / Kernel Extension) as non-permanent and as such they are removed by Windows when the Portmaster shuts down or when Windows reboots.\r\n\r\nIn rare cases, however, Windows fails to correctly remove Portmaster’s network stack integration correctly, resulting in a loss of network connectivity. We have never experienced this issue ourselves and thus haven’t yet been able to take an in-depth look.\r\n\r\nThe help Windows restore network connectivity, open a Windows [cmd](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/cmd) as an Administrator and enter the following commands to reset your network.\r\nWarning: You might need to reconfigure any special network settings you had.\r\n\r\n netsh int ip reset\r\n netsh winsock reset catalog\r\n\r\nAfter that, reboot.\r\n\r\nIf these steps did not restore network connectivity, please report this.\r\n\r\n#### Linux\r\n\r\nPortmaster adds rules to the _iptables_ configuration in order to integrate into the network stack. These are automatically removed when Portmaster shuts down or is uninstalled. There might be rare cases, where this does not happen. Then you can remove them manually by running `sudo /opt/safing/portmaster recover-iptables` or restarting.\r\n\r\nIf there is another problem, you can try to restart the networking with the command `sudo systemctl restart networking` or the equivalent for your distribution.\r\n\r\nIf these steps did not restore network connectivity, please report this.\r\n\r\n---\r\n\r\nKeywords: lost internet, no network, timeout, after install, after shutdown, cannot access, not working, uninstall, remove, deleted, reboot, restart, broken, DNS, resolving, network issues\r\n\r\nCategories: Windows, Linux, Starting and Stopping", + "keywords": [ + "lost internet", + "no network", + "timeout", + "after install", + "after shutdown", + "cannot access", + "not working", + "uninstall", + "remove", + "deleted", + "reboot", + "restart", + "broken", + "DNS", + "resolving", + "network issues" + ], + "categories": [ + "Windows", + "Linux", + "Starting and Stopping" + ] + } +] diff --git a/_data/faq-config.yml b/_data/faq/config.yml similarity index 83% rename from _data/faq-config.yml rename to _data/faq/config.yml index 362ab51..3ef9d06 100644 --- a/_data/faq-config.yml +++ b/_data/faq/config.yml @@ -5,4 +5,6 @@ categories: - Starting and Stopping - Compatibility - Leaks + - Windows + - Linux - Other diff --git a/_data/faq-data.json b/_data/faq/data.json similarity index 87% rename from _data/faq-data.json rename to _data/faq/data.json index e45ecc0..3615640 100644 --- a/_data/faq-data.json +++ b/_data/faq/data.json @@ -1,6 +1,6 @@ [ { - "body": "Portmaster is currently built for desktops that have a physical graphical interface. That said, you can run Portmaster on a server if done correctly.\r\n\r\nLet me also remind you that Portmaster is not yet stable software and things may break once in a while. Ok, let's start:\r\n\r\n### Backup Access\r\n\r\nIf in any way possible make sure and _test_ your backup access to the server in case you lock yourself out.\r\n\r\n### Prepare Config File\r\n\r\nWe'll need to write our config file ourselves and place it on the server before we install Portmaster so that we don't lock ourselves out. You can either use an existing Portmaster instance to configure your settings and then copy the `config.json` file from the data directory, or you can build it from scratch. Below is a template as a starting point. Now, let's go though the settings you want to change:\r\n\r\n- [API Listen Address](https://docs.safing.io/portmaster/settings#core/listenAddress)\r\n - By default, Portmaster only listens on localhost, change this to `0.0.0.0:817` to enable connections from anywhere.\r\n- [Incoming Rules](https://docs.safing.io/portmaster/settings#filter/serviceEndpoints)\r\n - You need to additionally allow from where connections to the Portmaster API are allowed. Scope this a narrow as possible.\r\n - We can't configure rules for applications in `config.json`, so we add only global rules for now and can switch to per-app after install.\r\n - (First add app rule, test, and then remove the global rule!)\r\n - Also, allow other management protocols so you can still access your server, such as SSH or RDP.\r\n- [Development Mode](https://docs.safing.io/portmaster/settings#core/devMode)\r\n - ⚠️ While Portmaster has support for [API Keys](https://docs.safing.io/portmaster/settings#core/apiKeys), these are not yet supported for logging into the UI. This means you will need to activate [Development Mode](https://docs.safing.io/portmaster/settings#core/devMode) for now, to allow access the the UI.\r\n- [Automatic Updates](https://docs.safing.io/portmaster/settings#core/automaticUpdates)\r\n - Portmaster uses automatic updates to stay up to date. Depending on your use case, this might not be what you want.\r\n - We haven't yet split the automatic update system into binaries and intelligence data, so disabling this will cut you off from intelligence data updates.\r\n - Until we have support for splitting this, you should manually update regularly by pressing the \"Download Updates\" button in tools menu.\r\n\r\nIf you run Portmaster on a private network you have access to, then this might be enough. If you want to access Portmaster via a public network, more caution and work is needed.\r\n\r\n⚠️ Portmaster does not support HTTPS for the UI. You will need to take care of this yourself. We recommend using something like [Traefik](https://traefik.io/) or [Caddy](https://caddyserver.com/) as a reverse proxy for automatic HTTPS.\r\n\r\n`config.json` template with multiple options - delete the ones you don't need:\r\n```\r\n{\r\n \"core\": {\r\n \"automaticUpdates\": false,\r\n \"devMode\": true,\r\n \"expertiseLevel\": \"developer\",\r\n \"listenAddress\": \"0.0.0.0:817\"\r\n },\r\n \"filter\": {\r\n \"serviceEndpoints\": [\r\n \"+ Localhost\",\r\n \"+ * TCP/SSH # Allow remote SSH access from anywhere\",\r\n \"+ * */3389 # Allow remote RDP access from anywhere\",\r\n \"+ * TCP/817 # Allow remote access to Portmaster from anywhere\",\r\n \"+ LAN TCP/817 # Allow remote access to Portmaster from LAN only\"\r\n ]\r\n }\r\n}\r\n```\r\n\r\nYou may also want to validate the json before using your config.\r\n\r\n### Place Config File\r\n\r\n_Before_ installing we need to place to config file:\r\n\r\n- Windows: `C:\\ProgramData\\Safing\\Portmaster\\config.json`\r\n- Linux: `/opt/safing/portmaster/config.json`\r\n\r\n### Install Portmaster\r\n\r\nThen, run the installer for Portmaster on the server. If everything went well, then you should still have access to your server and to the Portmaster UI in the way you configured.\r\n\r\n----\r\n\r\nKeywords: server, automatic updates, production, remote access, API, HTTP, authentication\r\n\r\nCategories: Compatibility", + "body": "Portmaster is currently built for desktops that have a physical graphical interface. That said, you can run Portmaster on a server if done correctly.\r\n\r\n### Backup Access\r\n\r\nIf in any way possible make sure and _test_ your backup access to the server in case you lock yourself out.\r\n\r\n### Prepare Config File\r\n\r\nWe'll need to write our config file ourselves and place it on the server before we install Portmaster so that we don't lock ourselves out. You can either use an existing Portmaster instance to configure your settings and then copy the `config.json` file from the data directory, or you can build it from scratch. Below is a template as a starting point. Now, let's go though the settings you want to change:\r\n\r\n- [API Listen Address](https://docs.safing.io/portmaster/settings#core/listenAddress)\r\n - By default, Portmaster only listens on localhost, change this to `0.0.0.0:817` to enable connections from anywhere.\r\n- [Incoming Rules](https://docs.safing.io/portmaster/settings#filter/serviceEndpoints)\r\n - You need to additionally allow from where connections to the Portmaster API are allowed. Scope this a narrow as possible.\r\n - We can't configure rules for applications in `config.json`, so we add only global rules for now and can switch to per-app after install.\r\n - (First add app rule, test, and then remove the global rule!)\r\n - Also, allow other management protocols so you can still access your server, such as SSH or RDP.\r\n- [Development Mode](https://docs.safing.io/portmaster/settings#core/devMode)\r\n - ⚠️ While Portmaster has support for [API Keys](https://docs.safing.io/portmaster/settings#core/apiKeys), these are not yet supported for logging into the UI. This means you will need to activate [Development Mode](https://docs.safing.io/portmaster/settings#core/devMode) for now, to allow access the the UI.\r\n- [Automatic Updates](https://docs.safing.io/portmaster/settings#core/automaticUpdates)\r\n - Portmaster uses automatic updates to stay up to date. Depending on your use case, this might not be what you want.\r\n - We haven't yet split the automatic update system into binaries and intelligence data, so disabling this will cut you off from intelligence data updates.\r\n - Until we have support for splitting this, you should manually update regularly by pressing the \"Download Updates\" button in tools menu.\r\n\r\nIf you run Portmaster on a private network you have access to, then this might be enough. If you want to access Portmaster via a public network, more caution and work is needed.\r\n\r\n⚠️ Portmaster does not support HTTPS for the UI. You will need to take care of this yourself. We recommend using something like [Traefik](https://traefik.io/) or [Caddy](https://caddyserver.com/) as a reverse proxy for automatic HTTPS.\r\n\r\n`config.json` template with multiple options - delete the ones you don't need:\r\n```\r\n{\r\n \"core\": {\r\n \"automaticUpdates\": false,\r\n \"devMode\": true,\r\n \"expertiseLevel\": \"developer\",\r\n \"listenAddress\": \"0.0.0.0:817\"\r\n },\r\n \"filter\": {\r\n \"serviceEndpoints\": [\r\n \"+ Localhost\",\r\n \"+ * TCP/SSH # Allow remote SSH access from anywhere\",\r\n \"+ * */3389 # Allow remote RDP access from anywhere\",\r\n \"+ * TCP/817 # Allow remote access to Portmaster from anywhere\",\r\n \"+ LAN TCP/817 # Allow remote access to Portmaster from LAN only\"\r\n ]\r\n }\r\n}\r\n```\r\n\r\nYou may also want to validate the json before using your config.\r\n\r\n### Place Config File\r\n\r\n_Before_ installing we need to place to config file:\r\n\r\n- Windows: `C:\\ProgramData\\Safing\\Portmaster\\config.json`\r\n- Linux: `/opt/safing/portmaster/config.json`\r\n\r\n### Install Portmaster\r\n\r\nThen, run the installer for Portmaster on the server. If everything went well, then you should still have access to your server and to the Portmaster UI in the way you configured.\r\n\r\n----\r\n\r\nKeywords: server, automatic updates, production, remote access, API, HTTP, authentication\r\n\r\nCategories: Compatibility", "title": "FAQ: Can I run Portmaster on a server?", "url": "https://github.com/safing/portmaster/issues/707" }, @@ -24,6 +24,11 @@ "title": "FAQ: Does Portmaster support IPv6?", "url": "https://github.com/safing/portmaster/issues/778" }, + { + "body": "You can link your Discord ID to your Portmaster account in order to gain access to private channels as well as gaining the sweet user flair on all your posts:\r\n![image](https://user-images.githubusercontent.com/11504285/195292347-c895c904-f999-428a-b4f1-72776ac8cb57.png)\r\n\r\n### Get your Discord ID\r\nYour discord ID is NOT your user name, and most people have never seen it.\r\nWe might update the bot in the future to retrieve this ID automatically, but for now you will have to jump through some hoops to get your ID.\r\n**1. Go to settings**\r\n![image](https://user-images.githubusercontent.com/11504285/195293428-66ba2648-40d4-4d7c-b636-b1cd92b00b59.png)\r\n**2. Open Advanced**\r\n![image](https://user-images.githubusercontent.com/11504285/195293524-a40225f6-1199-4d0c-b7cc-7f550fe3d7c2.png)\r\n**3. Activate \"Developer Mode\"**\r\n![image](https://user-images.githubusercontent.com/11504285/195293614-f6515c35-bc55-4008-865c-5f7d33fa81bd.png)\r\n**4. \"Copy ID\" from your \"My Account\" Page**\r\n![image](https://user-images.githubusercontent.com/11504285/195293877-317257d1-442c-405a-9628-f72412db45b2.png)\r\n\r\n### Add your ID to your Portmaster Account\r\n\r\nAfter logging into your Portmaster Account at https://account.safing.io/:\r\n\r\n**1. Go to \"Account and Password**\r\n![image](https://user-images.githubusercontent.com/11504285/195294507-9de25198-7257-4924-acf0-6c5c0043b765.png)\r\n**2. Enter your Discord ID**\r\n![image](https://user-images.githubusercontent.com/11504285/195294778-1570d97b-d40a-4fda-805e-a4ec788d2b69.png)\r\n**3. Confirm Change with Password**\r\n![image](https://user-images.githubusercontent.com/11504285/195294941-1a25dc88-f4a5-44a8-be91-544ba1b6799d.png)\r\n\r\nThe update in Discord should be immediate.\r\nNote that Reddit can be filled out already but this feature is not available yet. \r\n\r\n---\r\n\r\nKeywords: Discord, Account, Flair, User,\r\n\r\nCategories: Guides, Account", + "title": "FAQ: How can I add my Discord ID to my Portmaster Account?", + "url": "https://github.com/safing/portmaster/issues/936" + }, { "body": "Portmaster is all about protecting your privacy. This also means that it may block something that you want to allow. Here's how you do it:\r\n\r\n## 1. Find the blocked connection in the Network Monitor\r\n\r\nBefore we can try to fix anything, we need to find the connection that is blocked in the Network Monitor. To do this, open the Portmaster App, which will start with the Network Monitor already open.\r\n\r\nThen, find the application that you are having trouble with. Sometimes applications are split into multiple sub-parts, so you might need to click around. If you see an application that has at least a little bit of a grey bar, it means that at least one connection is blocked:\r\n![image](https://user-images.githubusercontent.com/18184155/175247736-9961ea93-be13-4624-9278-76beba26f80d.png)\r\n\r\nIf you have found the application, open it and search for the blocked connection, which are marked with a red dot:\r\n![image](https://user-images.githubusercontent.com/18184155/175248225-5842969e-d603-4e0f-8d7a-815c115ee9ed.png)\r\n\r\nIf your connections are grouped in some way, again look out for the grey parts of the bar:\r\n![image](https://user-images.githubusercontent.com/18184155/175247736-9961ea93-be13-4624-9278-76beba26f80d.png)\r\n\r\nIf you found a connection that was blocked and looks like the one that you'd rather allow, continue to the next step:\r\n\r\n## 2. Find out why it is blocked\r\n\r\nTo get more information about the blocked connection, click on it to open the details:\r\n![image](https://user-images.githubusercontent.com/18184155/175249877-db0c0ff7-ec4e-41ad-916a-7c78f60f4544.png)\r\n\r\nIn addition to many other details (also depending on your [User Interface Mode](https://docs.safing.io/portmaster/settings#core/expertiseLevel)), you can see \"Applied Setting\" in the bottom left of this section.\r\nThis tells you which setting was responsible for blocking this connection.\r\n\r\n## 3. Allow the connection\r\n\r\nIn order to allow this connection, you now have two options:\r\n1. Add an exception for this connection (recommended), or\r\n2. Change the responsible setting\r\n\r\n### 3.1. Add an exception for this connection\r\n\r\nIn order to add an exception for this domain, just press the button at the bottom left of the connection section:\r\n![image](https://user-images.githubusercontent.com/18184155/175252873-b246c6a9-c326-4526-a946-537bca8c2d7a.png)\r\n\r\nIf you then go to the settings of the application, you will see that a new rule was added:\r\n![image](https://user-images.githubusercontent.com/18184155/175253147-4a692177-1de3-4cf5-90c6-7f4b6938ee66.png)\r\n\r\nIf the \"Allow Domain\" or \"Allow IP\" button is disabled, this means that an exception is not possible and that you must change the responsible setting:\r\n\r\n### 3.2. Change the responsible setting\r\n\r\nBefore you change the setting, you must decide whether you want to change the settings for this app only (recommended) or globally for all apps (which don't have this setting configured differently).\r\n\r\nPressing the corresponding button will take you to the responsible setting:\r\n![image](https://user-images.githubusercontent.com/18184155/175252694-7676ed7e-f356-46ff-a6fb-3847d857c0ef.png)\r\n\r\nHow to change the setting heavily depends on the setting itself, so the best way to go forward is to read the description by clicking on the (i) icon:\r\n![image](https://user-images.githubusercontent.com/18184155/175254095-1fc018b1-5451-4f71-a2b3-1113b9beec86.png)\r\n\r\nGenerally, we try to make all settings provide more protection by turning them \"on\", so in most cases turning off a setting will allow the connection.\r\n\r\nIn case there are multiple settings that block a connection, you might need to repeat this process.\r\n\r\n---\r\n\r\nKeywords: allow, exception, unbreak, unblock, not block, stop blocking, deny, denied, dropped, permit, connection, DNS request\r\n\r\nCategories: Guides, Privacy Filter", "title": "FAQ: How can I allow a blocked connection?", @@ -45,7 +50,7 @@ "url": "https://github.com/safing/spn/issues/106" }, { - "body": "If you want to help testing Portmaster and want to give earlier feedback on new features, you can switch to the [\"Beta\" Release Channel](https://docs.safing.io/portmaster/settings#core/releaseChannel).\r\n\r\n__Please be sure to always report problems that arise, so we can quickly find and fix them!__\r\n__Also, general feedback on changes are always very welcome!__\r\n\r\nIf you experience problems, you can always switch back to \"Stable\".\r\n\r\n⚠️ Though Portmaster has not reached the v1.0 release, it already uses the final release channels. This means that “Stable” is the current baseline and “Beta” is more unstable.\r\n\r\n---\r\n\r\nCategories: Guides", + "body": "If you want to help testing Portmaster and want to give earlier feedback on new features, you can switch to the [\"Beta\" Release Channel](https://docs.safing.io/portmaster/settings#core/releaseChannel).\r\n\r\n__Please be sure to always report problems that arise, so we can quickly find and fix them!__\r\n__Also, general feedback on changes are always very welcome!__\r\n\r\nIf you experience problems, you can always switch back to \"Stable\".\r\n\r\n---\r\n\r\nCategories: Guides", "title": "FAQ: How can I help testing Portmaster?", "url": "https://github.com/safing/portmaster/issues/717" }, @@ -69,6 +74,21 @@ "title": "FAQ: How do I share debug information and logs?", "url": "https://github.com/safing/portmaster/issues/705" }, + { + "body": "We use the notification system that was added in Windows 10, as it supports actions (ie. has buttons). Windows 7 and 8 do not have any support for these buttons.\r\n\r\nNotifications may still work to some extent, but prompts will not. Please disable [Prompt Desktop Notifications](https://docs.safing.io/portmaster/settings#filter/askWithSystemNotifications).\r\n\r\n---\r\n\r\nKeywords: broken, cannot click, can't press, missing button, Microsoft\r\n\r\nCategories: Windows", + "title": "FAQ: Notifications not available on Windows 7 and 8", + "url": "https://github.com/safing/portmaster-ui/issues/361" + }, + { + "body": "Some users report that the Portmaster Core Service will not start at boot, although it is configured to do so. If that is the case, you can check its status in the \"Services\" Desktop App. There, search for the Service \"Portmaster Core\" and inspect and start it as needed.\r\n\r\n---\r\n\r\nKeywords: starting, boot, startup, automatic\r\n\r\nCategories: Windows, Starting and Stopping\r\n", + "title": "FAQ: Portmaster Core Does Not Start at Boot", + "url": "https://github.com/safing/portmaster/issues/956" + }, + { + "body": "In some cases the Portmaster will fail to restart, because the Portmaster Kernel Extensions cannot be loaded and returns the error code `0x422`.\r\nThis stems from a known issue in Windows, where system services are not completely removed when something is monitoring the system services.\r\nWhen the Portmaster restarts, it is then unable to initialize the Kernel Extension, because the system thinks it is still unloading.\r\n\r\nIf you experience this issue, please follow this workaround:\r\n\r\n_Quoting from _\r\n\r\n> There may be several causes which lead to the service being stuck in “marked for deletion”.\r\n>\r\n> 1. [SysInternals' Process Explorer is opened](http://blog.cyotec.com/2011/05/specified-service-has-been-marked-for.html). Closing it should lead to automatic removal of the service.\r\n>\r\n> 1. [Task Manager is opened](https://stackoverflow.com/questions/20561990/how-to-solve-the-specified-service-has-been-marked-for-deletion-error/21310096#comment32672750_20565337).\r\n>\r\n> 1. [Microsoft Management Console (MMC) is opened](https://stackoverflow.com/a/8529760/240613). To ensure all instances are closed, run `taskkill /F /IM mmc.exe`.\r\n>\r\n> 1. [Services console is opened](https://stackoverflow.com/a/21310096/240613). This is the same as the previous point, since Services console is hosted by MMC.\r\n>\r\n> 1. [Event Viewer is opened](https://stackoverflow.com/a/18467128/240613). Again, this is the same as the third point.\r\n> \r\n> 1. [The key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\\\{service name} exists](https://stackoverflow.com/a/2804099/240613).\r\n>\r\n> 1. [Someone else is logged into the server](https://stackoverflow.com/a/28632820/240613) and has one of the previously mentioned applications opened.\r\n>\r\n> 1. An instance of Visual Studio *used to debug the service* is open.\r\n\r\n---\r\n\r\nKeywords: error code, restarting, boot\r\n\r\nCategories: Windows, Starting and Stopping\r\n", + "title": "FAQ: Portmaster Fails to Restart", + "url": "https://github.com/safing/portmaster/issues/955" + }, { "body": "#### Most Important\r\n\r\n- Portmaster does not do any permanent changes to your network configuration:\r\n - No network interfaces are added or changed.\r\n - No routing entries are added or changed.\r\n - No DNS server configuration is added or changed.\r\n- Required integration is done \"on-the-fly\" by redirecting packets.\r\n- When Portmaster is shut down or uninstalled, all (volatile) network integration is removed automatically.\r\n - When you still experience issues, check out #699.\r\n\r\nBesides that, changes vary depending on your operating system:\r\n\r\n#### Windows\r\n\r\n- All data is saved to `C:\\ProgramData\\Safing\\Portmaster` by default.\r\n- A system service is registered and marked to start automatically at boot.\r\n- Application entry for the Portmaster UI is added.\r\n- Application entry for the Portmaster Tray Notifiier is added and marked to start automatically at login.\r\n- Uninstall information is placed in the registry.\r\n- Read more at [Docs: Install on Windows](https://docs.safing.io/portmaster/install/windows)\r\n\r\n#### Linux\r\n\r\n- All data is saved to `/opt/safing/portmaster` by default.\r\n- Portmaster adds iptables entries on start and removes them when stopped.\r\n - This integration makes use of packet and connection marks, which likely makes Portmaster incompatible with other software attempting the same.\r\n- A systemd service file is placed at `/etc/systemd/system/portmaster.service`.\r\n- `.desktop` files are placed in `/usr/share/applications/`.\r\n- Icon is placed in `/usr/share/pixmaps/`.\r\n- Read more at [Docs: Install on Linux](https://docs.safing.io/portmaster/install/linux)\r\n\r\n---\r\n\r\nKeywords: change, modify, modification, integration, settings, registry, file, config, configuration, mess with, break\r\n\r\nCategories: Starting and Stopping", "title": "FAQ: What changes does Portmaster make to my system?", @@ -90,7 +110,7 @@ "url": "https://github.com/safing/portmaster/issues/719" }, { - "body": "Portmaster takes care of protecting your DNS queries by becoming the gateway for all DNS queries on your system and then sending them through an encrypted connection to the configured DNS server.\r\n\r\nIf you are using a DNS server for your network that has a dashboard, or if the DNS service you are using discerns between encrypted and non-encrypted queries, you might notice that sometimes Portmaster sends unencrypted queries.\r\n\r\nIn order to understand why that is necessary, let's take a look at a common network structure: A free __WiFi access point in a café__ or airport. Usually these can only be used when you __accept their Terms of Service__. In order for you to get you to read them, the network needs to somehow redirect to that.\r\nThis __needs to work even if the secure DNS server are unreachable__ - as you've not yet \"logged into\" the free network.\r\n\r\nThis is why Portmaster always __sends a handful of special domains__ - used by operating systems and browsers - __as plain DNS queries to the DNS server provided by the network__. You can find the current list of these domains [in the docs](https://docs.safing.io/portmaster/architecture/core-service/secure-dns/#connectivity-domains) or in the [source code as \"Connectivity Domains\")](https://github.com/safing/portmaster/blob/f135ec3242905b84811b26975a3458117cc2c28e/netenv/online-status.go#L53).\r\n\r\nIf you don't want these queries to go out, you can block them by enabling the setting [Ignore System/Network Servers](https://docs.safing.io/portmaster/settings#dns/noAssignedNameservers) or [Use Secure Protocols Only](https://docs.safing.io/portmaster/settings#dns/noInsecureProtocols). Please consider the side effects of enabling these settings when you do so.\r\n\r\nThe Portmaster will also attempt to detect these \"Captive Portals\" and will notify you if it finds one.\r\n\r\n---\r\n\r\nFor the time being there is also another possibility why this can happen. While getting Portmaster stable and making sure everything works as expected, we enabled Portmaster to fall back to the system assigned DNS servers in case all the configured DNS server failed. This is to ensure that we don't break the workflow of our users while moving forward. We are currently working on a solution how to handle this nicely. This is internally tracked at CC#2405.\r\n\r\n---\r\n\r\nKeywords: unencrypted query, DNS leaks, not sent, DHCP, system assigned.\r\n\r\nCategories: Leaks", + "body": "Portmaster takes care of protecting your DNS queries by becoming the gateway for all DNS queries on your system and then sending them through an encrypted connection to the configured DNS server.\r\n\r\nIf you are using a DNS server for your network that has a dashboard, or if the DNS service you are using discerns between encrypted and non-encrypted queries, you might notice that sometimes Portmaster sends unencrypted queries.\r\n\r\nIn order to understand why that is necessary, let's take a look at a common network structure: A free __WiFi access point in a café__ or airport. Usually these can only be used when you __accept their Terms of Service__. In order for you to get you to read them, the network needs to somehow redirect to that.\r\nThis __needs to work even if the secure DNS server are unreachable__ - as you've not yet \"logged into\" the free network.\r\n\r\nThis is why Portmaster always __sends a handful of special domains__ - used by operating systems and browsers - __as plain DNS queries to the DNS server provided by the network__. You can find the current list of these domains [in the docs](https://docs.safing.io/portmaster/architecture/core-service/secure-dns/#connectivity-domains) or in the [source code as \"Connectivity Domains\")](https://github.com/safing/portmaster/blob/f135ec3242905b84811b26975a3458117cc2c28e/netenv/online-status.go#L53).\r\n\r\nIf you don't want these queries to go out, you can block them by enabling the setting [Ignore System/Network Servers](https://docs.safing.io/portmaster/settings#dns/noAssignedNameservers) or [Use Secure Protocols Only](https://docs.safing.io/portmaster/settings#dns/noInsecureProtocols). Please consider the side effects of enabling these settings when you do so.\r\n\r\nThe Portmaster will also attempt to detect these \"Captive Portals\" and will notify you if it finds one.\r\n\r\n---\r\n\r\nFor the time being there is also another possibility why this can happen. To make sure everything works as expected, we enabled Portmaster to fall back to the system assigned DNS servers in case all the configured DNS server failed. This is to ensure that we don't break the workflow when installing Portmaster.\r\nWe are working on a solution how to best handle this in a way that does not break setups and provides the best privacy. This is internally tracked at CC#2405.\r\n\r\n---\r\n\r\nKeywords: unencrypted query, DNS leaks, not sent, DHCP, system assigned.\r\n\r\nCategories: Leaks", "title": "FAQ: Why does Portmaster send plain/unencrypted DNS queries?", "url": "https://github.com/safing/portmaster/issues/700" }, @@ -110,7 +130,7 @@ "url": "https://github.com/safing/portmaster-ui/issues/272" }, { - "body": "While Portmaster integrates deeply into the network stack of your operating system, all of it is volatile - meaning that it is automatically removed when Portmaster shuts down or when Portmaster is uninstalled.\r\n\r\nHowever, there are special cases where you might loose Internet or network connectivity after shutting down or uninstalling Portmaster.\r\n\r\n### 1. DNS Configuration Issues\r\n\r\nPortmaster becomes the gateway for all DNS queries when you install it, but it does not configure itself as your DNS server in the system. Rather, it does a _soft_ integration by redirecting all DNS queries to itself.\r\n\r\nWhat can happen is that at some point - while Portmaster is installed - the DNS configuration of your system is changed or corrupted into a state that does not work. But because Portmaster is installed, it will seamlessly fix it for you, because it \"corrects\" all queries.\r\nWhen you then shutdown or uninstall Portmaster this \"fix\" is removed and you end up with a broken DNS configuration.\r\n\r\n__Please review the DNS configuration of your system.__ When in doubt, set it to _automatic_ or _DHCP_.\r\n\r\n### 2. Network Stack Issues by the Operation System\r\n\r\nIn some more extreme cases, the system might not correctly remove the integration as it should.\r\n\r\n#### Windows\r\n\r\nPortmaster marks all its network stack integrations (the Firewall Driver / Kernel Extension) as non-permanent and as such they are removed by Windows when the Portmaster shuts down or when Windows reboots.\r\n\r\nIn rare cases, however, Windows fails to correctly remove Portmaster’s network stack integration correctly, resulting in a loss of network connectivity. We have never experienced this issue ourselves and thus haven’t yet been able to take an in-depth look.\r\n\r\nThe help Windows restore network connectivity, open a Windows [cmd](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/cmd) as an Administrator and enter the following commands to reset your network.\r\nWarning: You might need to reconfigure any special network settings you had.\r\n\r\n netsh int ip reset\r\n netsh winsock reset catalog\r\n\r\nAfter that, reboot.\r\n\r\nIf these steps did not restore network connectivity, please report this.\r\n\r\n#### Linux\r\n\r\nPortmaster adds rules to the _iptables_ configuration in order to integrate into the network stack. These are automatically removed when Portmaster shuts down or is uninstalled. There might be rare cases, where this does not happen. Then you can remove them manually by running `sudo /opt/safing/portmaster recover-iptables` or restarting.\r\n\r\nIf there is another problem, you can try to restart the networking with the command `sudo systemctl restart networking` or the equivalent for your distribution.\r\n\r\nIf these steps did not restore network connectivity, please report this.\r\n\r\n---\r\n\r\nKeywords: lost internet, no network, timeout, after install, after shutdown, cannot access, not working, uninstall, remove, deleted, reboot, restart, broken, DNS, resolving\r\n\r\nCategories: Starting and Stopping", + "body": "While Portmaster integrates deeply into the network stack of your operating system, all of it is volatile - meaning that it is automatically removed when Portmaster shuts down or when Portmaster is uninstalled.\r\n\r\nHowever, there are special cases where you might loose Internet or network connectivity after shutting down or uninstalling Portmaster.\r\n\r\n### 1. DNS Configuration Issues\r\n\r\nPortmaster becomes the gateway for all DNS queries when you install it, but it does not configure itself as your DNS server in the system. Rather, it does a _soft_ integration by redirecting all DNS queries to itself.\r\n\r\nWhat can happen is that at some point - while Portmaster is installed - the DNS configuration of your system is changed or corrupted into a state that does not work. But because Portmaster is installed, it will seamlessly fix it for you, because it \"corrects\" all queries.\r\nWhen you then shutdown or uninstall Portmaster this \"fix\" is removed and you end up with a broken DNS configuration.\r\n\r\n__Please review the DNS configuration of your system.__ When in doubt, set it to _automatic_ or _DHCP_.\r\n\r\n### 2. Network Stack Issues by the Operation System\r\n\r\nIn some more extreme cases, the system might not correctly remove the integration as it should.\r\n\r\n#### Windows\r\n\r\nPortmaster marks all its network stack integrations (the Firewall Driver / Kernel Extension) as non-permanent and as such they are removed by Windows when the Portmaster shuts down or when Windows reboots.\r\n\r\nIn rare cases, however, Windows fails to correctly remove Portmaster’s network stack integration correctly, resulting in a loss of network connectivity. We have never experienced this issue ourselves and thus haven’t yet been able to take an in-depth look.\r\n\r\nThe help Windows restore network connectivity, open a Windows [cmd](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/cmd) as an Administrator and enter the following commands to reset your network.\r\nWarning: You might need to reconfigure any special network settings you had.\r\n\r\n netsh int ip reset\r\n netsh winsock reset catalog\r\n\r\nAfter that, reboot.\r\n\r\nIf these steps did not restore network connectivity, please report this.\r\n\r\n#### Linux\r\n\r\nPortmaster adds rules to the _iptables_ configuration in order to integrate into the network stack. These are automatically removed when Portmaster shuts down or is uninstalled. There might be rare cases, where this does not happen. Then you can remove them manually by running `sudo /opt/safing/portmaster recover-iptables` or restarting.\r\n\r\nIf there is another problem, you can try to restart the networking with the command `sudo systemctl restart networking` or the equivalent for your distribution.\r\n\r\nIf these steps did not restore network connectivity, please report this.\r\n\r\n---\r\n\r\nKeywords: lost internet, no network, timeout, after install, after shutdown, cannot access, not working, uninstall, remove, deleted, reboot, restart, broken, DNS, resolving, network issues\r\n\r\nCategories: Windows, Linux, Starting and Stopping", "title": "FAQ: Why is my Internet or Network Access broken after shutdown or uninstall?", "url": "https://github.com/safing/portmaster/issues/699" } diff --git a/_data/releases/all.json b/_data/releases/all.json new file mode 100644 index 0000000..7a23e73 --- /dev/null +++ b/_data/releases/all.json @@ -0,0 +1,902 @@ +[ + { + "name": "portmaster-v0.4.2", + "tag_name": "portmaster-v0.4.2", + "body": "\r\n\r\n- Hide SPN tunnel info for LAN and localhost connections\r\n- Fix settings not being saved and the SPN feature carousel leaking CSS", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.4.2", + "created_at": "2022-10-19T09:30:15Z", + "date": "2022-10-19", + "repo": "portmaster-ui" + }, + { + "name": "notifier-v0.3.5", + "tag_name": "notifier-v0.3.5", + "body": "\r\n\r\n- initialize library on startup, lib api update\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/notifier-v0.3.5", + "created_at": "2022-10-18T13:25:47Z", + "date": "2022-10-18", + "repo": "portmaster-ui" + }, + { + "name": "portmaster-v0.4.1", + "tag_name": "portmaster-v0.4.1", + "body": "\r\n\r\n- Fix nodejs version for github action\r\n- Only load app-icon if presentation path is set\r\n- Fix linting errors and add github action\r\n- Improve styling of shared \"More\" dropdown and add \"App Settings\" link to grouped-by-app row\r\n- Fix styling of netquery search bar\r\n- Update side-dash to navigate to app connections and only expand when clicking the chevron\r\n- Add a \"all-done\" icon to prompt and notification list if they are empty\r\n- Fix abort-button not working when editing/creating a new rule\r\n- Hide app-icon for some special profiles and fix incorrect profile source\r\n- Fix support page layout changing depending on issue-title length\r\n- Fix SPN map behaving strange on pan and zoom\r\n- Do not show path and binary name if they are empty\r\n- Add tooltips to all main navigation items\r\n- Fix broken styling of text-input in confirmation dialog used when asking for an email\r\n- Fix URL query parameter mangling when reloading the current router URL", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.4.1", + "created_at": "2022-10-18T13:25:47Z", + "date": "2022-10-18", + "repo": "portmaster-ui" + }, + { + "name": "v1.0.0", + "tag_name": "v1.0.0", + "body": "\r\n\r\n- Bump version to v1.0.0\r\n- Fix restart button on Windows", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v1.0.0", + "created_at": "2022-10-18T13:18:20Z", + "date": "2022-10-18", + "repo": "portmaster" + }, + { + "name": "v0.9.11", + "tag_name": "v0.9.11", + "body": "\r\n\r\n- Update unidentified profile name\r\n- Allow any own local connection\r\n- Explicitly allow all connections of Portmaster Core Service\r\n- Use constants for default action values\r\n- Improve logging\r\n- Switch to FilterConnection as main decision function\r\n- Fix profile migration iteration error handling and only warn, not fail\r\n- Integrate special profiles into regular profile fetching for correct profile udpates\r\n- Classify unidentified localhost connections as unidentified instead of unsolicited\r\n- Make restart and shutdown APIs work without module", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.11", + "created_at": "2022-10-13T13:41:11Z", + "date": "2022-10-13", + "repo": "portmaster" + }, + { + "name": "assets-v0.3.1", + "tag_name": "assets-v0.3.1", + "body": "", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/assets-v0.3.1", + "created_at": "2022-10-13T13:33:45Z", + "date": "2022-10-13", + "repo": "portmaster-ui" + }, + { + "name": "notifier-v0.3.4", + "tag_name": "notifier-v0.3.4", + "body": "\r\n\r\n- Remove security level code\r\n- Added ActionInvoked check on linux notifications\r\n- Fix notification event handling\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/notifier-v0.3.4", + "created_at": "2022-10-13T13:33:45Z", + "date": "2022-10-13", + "repo": "portmaster-ui" + }, + { + "name": "v0.5.4 (lib only)", + "tag_name": "v0.5.4", + "body": "\r\n\r\n- Remove persistent connected notification", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.5.4", + "created_at": "2022-10-12T08:10:50Z", + "date": "2022-10-12", + "repo": "spn" + }, + { + "name": "v0.9.10", + "tag_name": "v0.9.10", + "body": "\r\n\r\n- Check if active profile is outdated before using\r\n- Improve logging and context usage\r\n- Use interception config only when ready\r\n- Use per-user lock file when unlocking\r\n- Fix fs error handling", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.10", + "created_at": "2022-10-11T12:58:03Z", + "date": "2022-10-11", + "repo": "portmaster" + }, + { + "name": "v0.5.3 (lib only)", + "tag_name": "v0.5.3", + "body": "\r\n\r\n- Fix fs error handling", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.5.3", + "created_at": "2022-10-11T12:02:26Z", + "date": "2022-10-11", + "repo": "spn" + }, + { + "name": "portmaster-v0.4.0", + "tag_name": "portmaster-v0.4.0", + "body": "\r\n\r\n- Add support to open parent process details\r\n- Add process details dialog. A bunch of minor improvements and fixes\r\n- Add support to create and edit profiles and fingerprints. Minor improvements for the v1 release\r\n- Add SPN feature carousel and multiple fixes\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.4.0", + "created_at": "2022-10-11T07:20:23Z", + "date": "2022-10-11", + "repo": "portmaster-ui" + }, + { + "name": "v0.9.9", + "tag_name": "v0.9.9", + "body": "\r\n\r\n- Add support for cmdline matching and add basic interpreter support\r\n- Add default icon for Windows services\r\n- Add migration for profiles\r\n- Improve profile metadata handling\r\n- Expose registered process tags via API\r\n- Check all regex fingerprint matches\r\n- Improve network tags for external requests\r\n- Add support for Windows Store tags\r\n- Use new profile functions in firewall\r\n- Add first tag handlers for svchost, app image, net\r\n- Collect env, tags and and matching path for processes\r\n- Move from LinkedPath to Fingerprints and PresentationPath\r\n- Fix darwin build", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.9", + "created_at": "2022-10-11T07:06:41Z", + "date": "2022-10-11", + "repo": "portmaster" + }, + { + "name": "v0.9.8", + "tag_name": "v0.9.8", + "body": "\r\n\r\n- replaced snoretoast with wintoast\r\n- Update SPN dep\r\n- Update deps\r\n- Fix rebase error and clean up\r\n- Allow verdict to change from initial non-allow state\r\n- Improve use of packet in connection decision making\r\n- Improve logging\r\n- Stop tunnels if they are not needed anymore due to verdict change\r\n- Improve verdict handling and switch to immediate re-evaluation\r\n- fix array allocation\r\n- add defer to unlock\r\n- preallocate array\r\n- better wording for log\r\n- Small fixes\r\n- Refactoring\r\n- Fixes\r\n- fix linter errors\r\n- Windows implementation\r\n- Removed comments\r\n- Fix merge error\r\n- Refactoring\r\n- Tunnel flag bugfix and refactoring\r\n- issue new verdict on configuration change\r\n- Reset connection PoC", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.8", + "created_at": "2022-10-10T14:19:33Z", + "date": "2022-10-10", + "repo": "portmaster" + }, + { + "name": "notifier-v0.3.3", + "tag_name": "notifier-v0.3.3", + "body": "", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/notifier-v0.3.3", + "created_at": "2022-10-10T14:14:05Z", + "date": "2022-10-10", + "repo": "portmaster-ui" + }, + { + "name": "v0.5.2 (lib only)", + "tag_name": "v0.5.2", + "body": "\r\n\r\n- Reset SPN exceptions again\r\n- Add StopTunnel method to TunnelContext\r\n- Add spn connect event\r\n- Update portmaster-start in Hub Dockerfile\r\n- Update deps\r\n- Add testsuite cmd\r\n- Expose token zone init\r\n- Increase default client timeout", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.5.2", + "created_at": "2022-10-10T14:04:34Z", + "date": "2022-10-10", + "repo": "spn" + }, + { + "name": "v0.9.7", + "tag_name": "v0.9.7", + "body": "\r\n\r\n- Add per-user locking option to portmaster-start run cmds\r\n- Improve and fix verification and fixing\r\n- Start with same verification config on all channels\r\n- Move all filter/interception config to interception module\r\n- Add verify cmd to portmaster-start\r\n- Improve signing with updatemgr\r\n- Add signature support to updatemgr\r\n- Enable signature checking in beta and staging release channels\r\n- Add support for signed updates", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.7", + "created_at": "2022-09-29T13:09:22Z", + "date": "2022-09-29", + "repo": "portmaster" + }, + { + "name": "portmaster-v0.3.6", + "tag_name": "portmaster-v0.3.6", + "body": "\r\n\r\n- Don't group by app by default. Load results chart after the first page has been loaded\r\n- Show tooltip with allow/block reason when hoving the verdict color indicator. Fixes #298\r\n- Fix different values for boolean allowed filter. Fixes safing/portmaster#804\r\n- Fix whitespace break in connection reason. Fixes #287\r\n- Increase button hit box in network scout and correctly handle developermode\r\n- Fix SPN account state handling in account details and login page\r\n- Trim whitespace from ordered list before saving. Fixes #221\r\n- Add inidcation that sub-filter lists are selected. Fixes #296\r\n- Fix change detection not being triggered correctly in app-icon\r\n- Reverse collapse/expand button for SPN hub details\r\n- Reverse the side-dash button in the navigation\r\n- Fix scrolling when side-dash overflows the app height\r\n- Apply user-supplied query in exide-node profile stats\r\n- Fix dialog styles not being applied correctly\r\n- Fix sfng-select incorrectly adding an empty option\r\n- Allow bulk deletion of rules and ask for confirmation. Save on enter. Fixes safing/portmaster#806. fixes #220\r\n- Decrease polling timeout and use correct command to stop on windows. Fixes #234", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.3.6", + "created_at": "2022-09-23T08:21:52Z", + "date": "2022-09-23", + "repo": "portmaster-ui" + }, + { + "name": "v0.9.6", + "tag_name": "v0.9.6", + "body": "\r\n\r\n- Add exit code for controlled failures\r\n- Add search domain info to resolver debug info\r\n- Fix repeating broadcast notifications\r\n- Improve incoming rules quick actions\r\n- Remove default incoming rules\r\n- Implement review suggestion\r\n- incoming: force block by default, apply default action and allow LAN per rules\r\n- Reset connection handling channel when firewall handler is stopped\r\n- Fix feature links in README", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.6", + "created_at": "2022-09-22T14:49:52Z", + "date": "2022-09-22", + "repo": "portmaster" + }, + { + "name": "v0.5.1", + "tag_name": "v0.5.1", + "body": "\r\n\r\n- Add docker support for hub\r\n- Increase UDP read size for now\r\n- Only start sluice for IPv6 if IPv6 stack is enabled\r\n- Stop using module management for the hub\r\n- Build hub without cgo\r\n- Fail nicely when Hub is misconfigured", + "prerelease": false, + "html_url": "https://github.com/safing/spn/releases/tag/v0.5.1", + "created_at": "2022-09-22T14:45:00Z", + "date": "2022-09-22", + "repo": "spn" + }, + { + "name": "portmaster-v0.3.5", + "tag_name": "portmaster-v0.3.5", + "body": "\r\n\r\n- Add new side-dash and improved SPN page\r\n- Add another default app icon from Windows to ignore\r\n- Fix background color for notification and prompt overlays\r\n- Fix no-prompts/no-notification position and remove max-height of network-activity widget for now\r\n- Migrate notification and prompt widgets to overlays accessible from the main menu", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.3.5", + "created_at": "2022-08-31T12:26:25Z", + "date": "2022-08-31", + "repo": "portmaster-ui" + }, + { + "name": "v0.9.5", + "tag_name": "v0.9.5", + "body": "\r\n\r\n- Show update failed notification only after some failed tries\r\n- Switch to zipfs lib for loading files from a zip\r\n- Move resolving unbreak filter list IDs to filterlists module\r\n- Improve logging of loaded intel data\r\n- Add new geoip metadata fields\r\n- Set tunneling options for (not) using community nodes\r\n- Add special Wayland args to Electron on Linux only", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.5", + "created_at": "2022-08-30T15:20:42Z", + "date": "2022-08-30", + "repo": "portmaster" + }, + { + "name": "v0.5.0", + "tag_name": "v0.5.0", + "body": "\r\n\r\n- Validate stickied Pins and sticky them by profile\r\n- Improve finding nearest pins with anycast IPs\r\n- Switch ConnectRequest encoding to CBOR\r\n- Use global default value for max find matches\r\n- Enable priority data messages by default\r\n- Send capacity and latency message with high priority\r\n- Add new config option: use community nodes", + "prerelease": false, + "html_url": "https://github.com/safing/spn/releases/tag/v0.5.0", + "created_at": "2022-08-30T15:08:26Z", + "date": "2022-08-30", + "repo": "spn" + }, + { + "name": "app-electron-v0.2.5", + "tag_name": "app-electron-v0.2.5", + "body": "\r\n\r\n- Specifically enable node integration for electron 20+", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/app-electron-v0.2.5", + "created_at": "2022-08-26T11:11:43Z", + "date": "2022-08-26", + "repo": "portmaster-ui" + }, + { + "name": "v0.9.4", + "tag_name": "v0.9.4", + "body": "\r\n\r\n- Improve wording of custom filter list setting\r\n- Disable restarting on failure for UI components\r\n- Enable WaylandWindowDecorations feature for electron run on wayland\r\n- Use correct ICMP message for blocking connections in iptables\r\n- Abort restarts if updated version is rolled back\r\n- Enable filter list category Unbreak Popular Websites by default\r\n- Set default log level to warning for portmaster-core", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.4", + "created_at": "2022-08-24T13:25:24Z", + "date": "2022-08-24", + "repo": "portmaster" + }, + { + "name": "app-electron-v0.2.4", + "tag_name": "app-electron-v0.2.4", + "body": "Changelog app-electron-v0.2.4:\r\n\r\n- Upgrade electron to v20", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/app-electron-v0.2.4", + "created_at": "2022-08-24T11:40:41Z", + "date": "2022-08-24", + "repo": "portmaster-ui" + }, + { + "name": "portmaster-v0.3.4", + "tag_name": "portmaster-v0.3.4", + "body": "\r\n\r\n- Bump portmaster module version\r\n- Fix regression with allow/block buttons\r\n- Remove debugger statement\r\n- Fix minor regressions and add support for query parameters in open-page action\r\n- Add error message to error button and abort change instead of reset\r\n- Use correct method to get app profile by scoped ID\r\n- Fix lazy loading of group-by results ignoring the current filter\r\n- Force a reload of the UI after the Portmaster restarted", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.3.4", + "created_at": "2022-08-17T08:15:32Z", + "date": "2022-08-17", + "repo": "portmaster-ui" + }, + { + "name": "v0.4.15", + "tag_name": "v0.4.15", + "body": "\r\n\r\n- Bump portmaster to v0.9.3\r\n- Add support for running old hub bins in hybrid in simple testing\r\n- Fix crane context usage", + "prerelease": false, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.15", + "created_at": "2022-08-08T11:53:25Z", + "date": "2022-08-08", + "repo": "spn" + }, + { + "name": "v0.9.3", + "tag_name": "v0.9.3", + "body": "\r\n\r\n- Fixed unstable SQL statement causing memory leaks due to prepared stmt caching", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.3", + "created_at": "2022-08-04T10:03:03Z", + "date": "2022-08-04", + "repo": "portmaster" + }, + { + "name": "portmaster-v0.3.3", + "tag_name": "portmaster-v0.3.3", + "body": "\r\n\r\n- Fix environment configuration not being passed to @safing/portmaster-api\r\n\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.3.3", + "created_at": "2022-08-04T09:35:13Z", + "date": "2022-08-04", + "repo": "portmaster-ui" + }, + { + "name": "portmaster-v0.3.2", + "tag_name": "portmaster-v0.3.2", + "body": "\r\n\r\n- Fix navigation menu actions not working anymore", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.3.2", + "created_at": "2022-08-03T14:26:08Z", + "date": "2022-08-03", + "repo": "portmaster-ui" + }, + { + "name": "portmaster-v0.3.1", + "tag_name": "portmaster-v0.3.1", + "body": "\r\n\r\n- Bump portmaster module version\r\n- Add notice if all connections of a group have been garbage collected\r\n- Fix app settings being reset on graph update\r\n- Remove deprecated field spn_used and switch to tunneled instead\r\n- Save and re-use the filter for the global network activity viewer\r\n- Show loading indicator in select-boxes and support presetting the netquery filter\r\n- Lighten up the background color of the searchbar overlay\r\n- Improve disabled state handling for select items\r\n- Set default connection group-by to profile\r\n- Fix default sort order in network activity monitor\r\n- Fix rediction to app settings not working\r\n- Fix broken styling of overlay-stepper\r\n- Accept \"no\" and \"yes\" for boolean values\r\n- Implement various small changes based on first user feedback\r\n- Refactored portmaster API related code to @safing/portmaster-api", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.3.1", + "created_at": "2022-08-03T07:07:45Z", + "date": "2022-08-03", + "repo": "portmaster-ui" + }, + { + "name": "v0.9.2", + "tag_name": "v0.9.2", + "body": "\r\n\r\n- Improve custom filter list config key", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.2", + "created_at": "2022-08-02T14:39:27Z", + "date": "2022-08-02", + "repo": "portmaster" + }, + { + "name": "v0.9.1", + "tag_name": "v0.9.1", + "body": "\r\n\r\n- Fix write/readonly connection usage and linter error\r\n- Add metadata to special responder responses\r\n- Mitigate double read locks on the layered profile\r\n- Use a dedicated write connection for persisting in sqlite and switch pool to read-only\r\n- Remove locking from SQlite access\r\n- Add connection pooling for sqlite database access\r\n- Update portbase to v0.15.0\r\n- Improve broadcasts test data\r\n- Use new microtask function\r\n- Removed duplicated field SPNUsed from netquery module\r\n- Minor improvements and documentation\r\n- Move checking custom filter list behind main filter lists to get entity data\r\n- Api ednpoint to custom filter list added\r\n- Change worning for invalid lines in filter list\r\n- Refactoring\r\n- Bug fixes and performence fixes: Synchronization bug fixed map reseting performence improvment Added more notificationa and better wording better scheduling of file parsing task\r\n- Custom filter list: subdomain and cname cheks Automatic realod when settings is changed periodicly check for file changes\r\n- Refactoring\r\n- Custom filter list proof of concept\r\n- Remove use of event log viewer\r\n- Ignore disabled event log viewer at startup\r\n- Improve app-auth request flow and implement review suggestions\r\n- Fix merge issues\r\n- Merge branch 'develop' into develop\r\n- Set DNS http maximu idle connection to 3 minutes\r\n- Minor fixes\r\n- Bugs and lint warning fixex Fix domain map cuncurrent access Fix ResolverInfo Domain was not copied bug Fix linter warnings\r\n- tls protocol for DoT added, minor refactoring\r\n- Resolver Info fill missing field\r\n- Fix config url typo\r\n- DoT support for domain name only Configed resolvers skip ther own domains\r\n- Refatoring and removed pre resolving of dot, doh\r\n- Add endpoint to retrieve the current profile ID\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.1", + "created_at": "2022-08-02T12:28:21Z", + "date": "2022-08-02", + "repo": "portmaster" + }, + { + "name": "v0.4.14", + "tag_name": "v0.4.14", + "body": "\r\n\r\n- Improve op capacity test\r\n- Improve module dependencies and context usage\r\n- Update deps\r\n- Update portbase and portmaster\r\n- Disable nolintlint linter\r\n- Add current main intel as test file\r\n- Increase health check timeout to mitigate flow bug a little\r\n- Consolidate Hub related intel and add VerifiedOwner\r\n- Use JSON and CBOR for introducing tags instead\r\n- Improve find nearest error handling\r\n- Fix access tests\r\n- Improve unknown op logging\r\n- Add more prioritized scheduling\r\n- Add MsgTypePriorityData and scheduling via prioritized microtasks\r\n- Fix logging prefixes", + "prerelease": false, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.14", + "created_at": "2022-08-02T12:24:55Z", + "date": "2022-08-02", + "repo": "spn" + }, + { + "name": "v0.9.0", + "tag_name": "v0.9.0", + "body": "Note: This release will be in staging and beta slightly longer.\r\n\r\n\r\n\r\n- Fix linter error and make identifier check more explicit\r\n- Automatically append arguments required by Electron to run on wayland\r\n- Merge branch 'develop' into feature/query\r\n- Implement some review suggestions\r\n- Fix go.mod\r\n- Add additional field to internal SQL model\r\n- Bump github.com/stretchr/testify from 1.7.1 to 1.8.0\r\n- Bump github.com/hashicorp/go-version from 1.5.0 to 1.6.0\r\n- Create codeql-analysis.yml\r\n- Create dependabot.yml\r\n- Update Primary Tag-Line\r\n- Update dependencies\r\n- Add broadcast notifications test data\r\n- Add broadcasts module\r\n- Simplify and improve update version export\r\n- Fix linter error\r\n- Remove filter lists help\r\n- Improve rules and filterlists config options\r\n- Stop using deprecated function\r\n- Fix detection of incoming localhost packets on Linux\r\n- Make intel index override-able by other indexes\r\n- Add check to ensure matching PID constants\r\n- Fix direction detection for unsupported protocols\r\n- Add support for free-text search and minor bug fixes in netquery\r\n- Add support for pagination to netquery module\r\n- Add query and chart support with multiple fixes to ORM package\r\n- Add support for new query API\r\n- Use new(record.Meta) instead of a dedicated call to SetMeta\r\n- Add and update netquery code based on review discussions\r\n- Add netquery module to main\r\n- Add documentation to query runner\r\n- Add initial sqlite support in netquery\r\n- Add basic, tailored SQL ORM mapper\r\n- Improve device location system with more safeguards\r\n- Add geoip.IsInitialized to expose if the databases have been loaded\r\n- Deactivate IPv6 integrations when no IPv6 stack is detected\r\n- Suppress error when stopping during filterlist update\r\n- Improve read rights on log files", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.9.0", + "created_at": "2022-07-19T15:07:03Z", + "date": "2022-07-19", + "repo": "portmaster" + }, + { + "name": "v0.4.13", + "tag_name": "v0.4.13", + "body": "\r\n\r\n- Let operations override end error to be sent\r\n- Add missing doc\r\n- Add helper to get the exit node\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.13", + "created_at": "2022-07-19T14:55:52Z", + "date": "2022-07-19", + "repo": "spn" + }, + { + "name": "portmaster-v0.3.0", + "tag_name": "portmaster-v0.3.0", + "body": "\r\n\r\nThis version includes the new Network Activity view, which is responsible for most commits:\r\n\r\n- Strip FAQ prefix and flex-grow collision\r\n- Fix codelyzer dependency\r\n- Add FAQs to support page\r\n- Fix build errors due to incorrect rebasing/merging of feature branches\r\n- Fix showing default stackable config values\r\n- Fix opening tip-up link in new tab in browser\r\n- Add reset broadcast notification state debug button\r\n- Add broadcast notification styling\r\n- Merge branch 'feature/safing-ui-lib' into develop\r\n- Implement review suggestions\r\n- Upgrade all other packages and fix linting errors due to stricter angular/rxjs types\r\n- Fix linter errors due to stricter Angular 14 template checking\r\n- Updated to Angular@14\r\n- Partial broken upgrade to angular@13\r\n- Ditch ngx-build-plus as tailwind has native support in angular now\r\n- Ditch ngx-build-plus as tailwind has native support in angular now\r\n- Fix tailwind configuration and move component scss out of @layers for now\r\n- Run \"Organize Imports\" on all files\r\n- Switch from app- prefix to sfng- prefix in tab components\r\n- Migrated toggle-switch and overlay-stepper to new @safing/ui\r\n- Migrated most shared common components to a new @safing/ui library\r\n- Minor changes to imports and build config\r\n- Add \"more\" dropdown with additional filters to netquery viewer and update stylign\r\n- Add more translations for connection fields\r\n- Update tag-bar styling\r\n- Add missing provider to searchbar overlay\r\n- Add groupby/orderby support to netquery searchbar and update styling\r\n- Update connection details component styling\r\n- Update connection details component stylign\r\n- Add missing animation declaration to network-activity-widget\r\n- Use fixed width for connection counter\r\n- Fix focus component not running after the view has been initialized\r\n- Add group-by and order-by support to text query language\r\n- Remove version info bar in settings and add new menus in navigation\r\n- Fix redirect to settings action to open the correct tab\r\n- Add dedicated module for app-icon\r\n- Fix button outline class in pagination component\r\n- Refactor select component styling\r\n- Add menu component inputs that proxy through to the dropdown\r\n- Upgrade tailwind version\r\n- Add additional allowed position and offset-x support to dropdown\r\n- Add pagination support to new netquery viewer\r\n- Various improvements to the new netquery/network monitor search system\r\n- Bump notifier version\r\n- Auto-scale icons to better size for tray\r\n- Update systray lib to include fix for setting icon\r\n- Add new basic netquery viewer using the new query interface. Includes various refactoring\r\n- Move network overview from monitor to dedicated widget\r\n- Move icon changer to own goroutine in icon test program\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.3.0", + "created_at": "2022-07-19T14:49:57Z", + "date": "2022-07-19", + "repo": "portmaster-ui" + }, + { + "name": "v0.4.12", + "tag_name": "v0.4.12", + "body": "\r\n\r\n- Fix SPN reinit api permission\r\n- Update dependencies\r\n- Add safeguard to stop uncontrolled operation\r\n- Add captain.GetSPNStatus to export the current SPN status\r\n- Remove incorrect config annotations\r\n- Make navigator wait for the geoip databases to load before starting\r\n- Add safeguards and improve logging\r\n- Add api endpoint to re-initialize the SPN", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.12", + "created_at": "2022-06-22T14:54:09Z", + "date": "2022-06-22", + "repo": "spn" + }, + { + "name": "v0.8.13", + "tag_name": "v0.8.13", + "body": "Changelog\r\n\r\n- Update SPN\r\n- Fix multicast detection on ended connections as well as some linter errors\r\n- Add support for upcoming UNBREAK filter list\r\n- Send notification instead of killing conflicting DNS service\r\n- Improve wording on setting dns/noInsecureProtocols\r\n- Improve support for DNS-SD and fall back to cached data for non-ICANN queries\r\n- Detect responses to multi/broadcast queries\r\n- Calm down and relax dns query check\r\n- Reset system self-check after network change", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.13", + "created_at": "2022-06-01T11:54:06Z", + "date": "2022-06-01", + "repo": "portmaster" + }, + { + "name": "v0.4.11", + "tag_name": "v0.4.11", + "body": "\r\n\r\n- Improve error usage and wording\r\n- Lower log level for expansion terminal OK errors\r\n- Allow OpEnd to change the sent error message\r\n- Remove bootstrap flag from client state", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.11", + "created_at": "2022-06-01T11:50:42Z", + "date": "2022-06-01", + "repo": "spn" + }, + { + "name": "notifier-v0.3.2", + "tag_name": "notifier-v0.3.2", + "body": "\r\n\r\n- Update fyne.io/systray in notifier\r\n- Enable notifier arm64 builds for Windows and Linux", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/notifier-v0.3.2", + "created_at": "2022-05-20T06:57:38Z", + "date": "2022-05-20", + "repo": "portmaster-ui" + }, + { + "name": "v0.8.12", + "tag_name": "v0.8.12", + "body": "\r\n\r\n- Update SPN", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.12", + "created_at": "2022-05-19T09:30:45Z", + "date": "2022-05-19", + "repo": "portmaster" + }, + { + "name": "v0.4.10", + "tag_name": "v0.4.10", + "body": "\r\n\r\n- Do not special UDP socket options on windows\r\n- Add nil guards to crane hooks", + "prerelease": false, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.10", + "created_at": "2022-05-19T09:27:44Z", + "date": "2022-05-19", + "repo": "spn" + }, + { + "name": "v0.8.11", + "tag_name": "v0.8.11", + "body": "\r\n\r\n- Use alternative approach to fix nfqueue closing process", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.11", + "created_at": "2022-05-18T11:26:46Z", + "date": "2022-05-18", + "repo": "portmaster" + }, + { + "name": "v0.8.10", + "tag_name": "v0.8.10", + "body": "\r\n\r\n- Increase supported size of windows network state table entries\r\n- Fix shutting down nfq interception with go-nfqueue v1.3.1\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.10", + "created_at": "2022-05-16T07:17:46Z", + "date": "2022-05-16", + "repo": "portmaster" + }, + { + "name": "v0.4.9", + "tag_name": "v0.4.9", + "body": "\r\n\r\n- Enable submit control system and add default terminal options\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.9", + "created_at": "2022-05-16T07:14:57Z", + "date": "2022-05-16", + "repo": "spn" + }, + { + "name": "v0.4.8", + "tag_name": "v0.4.8", + "body": "\r\n\r\n- Update terminal opts for production\r\n- Add submit control to terminal\r\n- Integrate duplex flow queue into terminal\r\n- Fix home hub policy check, add ID as Hub entity domain\r\n- Fix crane update hook handler on client", + "prerelease": false, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.8", + "created_at": "2022-05-09T12:26:19Z", + "date": "2022-05-09", + "repo": "spn" + }, + { + "name": "notifier-v0.3.1", + "tag_name": "notifier-v0.3.1", + "body": "\r\n\r\n- Auto-scale icons to better size for tray\r\n- Update systray lib to include fix for setting icon\r\n- Move icon changer to own goroutine in icon test program\r\n- Fix status handling\r\n- Switch to fyne.io/systray", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/notifier-v0.3.1", + "created_at": "2022-05-05T09:16:59Z", + "date": "2022-05-05", + "repo": "portmaster-ui" + }, + { + "name": "v0.8.9", + "tag_name": "v0.8.9", + "body": "\r\n\r\n- Add MatchMulti function to match endpoints list against multiple entities\r\n- Only warn about unexpected parent process when not in dev mode\r\n- Resolve to real file paths before checking path based API access\r\n- Use more verbose names for iptables chains\r\n- Show notification about manual DNS setup instead of compatibility notice\r\n- Block DNS requests if bypass prevention is active\r\n- Add config option to disable dns query interception", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.9", + "created_at": "2022-05-05T09:13:34Z", + "date": "2022-05-05", + "repo": "portmaster" + }, + { + "name": "v0.4.7", + "tag_name": "v0.4.7", + "body": "\r\n\r\n- Add traced logging to SPN tunnel building\r\n- Correctly fail when tunnel creation fails.\r\n- Add sluice UDP listener with socket options to fix packet response addresses", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.7", + "created_at": "2022-05-05T09:11:02Z", + "date": "2022-05-05", + "repo": "spn" + }, + { + "name": "portmaster-v0.2.4", + "tag_name": "portmaster-v0.2.4", + "body": "\r\n\r\n- Remove y-offset in intro drop-downs\r\n- Finish intro screen steps for MVP\r\n- Update code to use new modules and component selectors\r\n- Fix background color of dialogs\r\n- Create dedicated module for config components and add more customization support to generic-component\r\n- Create dedicated modules for shared components\r\n- Change current menu to be based on new dropdown module\r\n- Split drop-down and select into different modules with multiple changes\r\n- wip: Use OverlayStepper to display intro MVP on page load. Still needs refactoring\r\n- Add first version of the intro MVP using the new OverlayStepper\r\n- Add OverlayStepper module that supports wizard-like stepping through pages\r\n- Workaround for button hover with blue background. Still needs a proper fix\r\n- Fix dialog typings and allow access to dialog content reference\r\n- Add DialogModule as a depdendency to tip-up and fix imports\r\n- Disable electron's internal secure DNS system\r\n- Create dedicated module for dialog service\r\n- Add arm64 building for electron", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.2.4", + "created_at": "2022-04-13T10:14:17Z", + "date": "2022-04-13", + "repo": "portmaster-ui" + }, + { + "name": "v0.8.8", + "tag_name": "v0.8.8", + "body": "\r\n\r\n- Improve IP scope classification\r\n- Reset device locations when network changes\r\n- Only fix chrome sandbox permission when needed\r\n- Add intel-only flag for initializing intel data only\r\n- Ignore comments on rule parsing\r\n- Only warn when registry cleanup fails\r\n- Improve wording on block bypassing notification and setting\r\n- Raise dns/nameservers config to expertise level user\r\n- Improve prevented bypass attempt notification\r\n- Fix connection locking in firewall packet handler\r\n- Add notify threshold for app related notification\r\n- Fix secure DNS bypass notification to reflect reality\r\n- Increase self-check timeouts and threshold\r\n- Improve resolver config for intro slides\r\n- Clear DNS cache when DNS resolver config changes in any way", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.8", + "created_at": "2022-04-13T09:55:59Z", + "date": "2022-04-13", + "repo": "portmaster" + }, + { + "name": "v0.4.6", + "tag_name": "v0.4.6", + "body": "\r\n\r\n- Bump hub version\r\n- Update deps\r\n- Stick destinations to Hubs or avoid them in case pure network error\r\n- Increase sluice request expiry\r\n- Fix index error in region optimizer\r\n- Fix broken controller stop message\r\n- Improve SPN graph rendering with new data\r\n- Synchronize stopping state\r\n- Improve hub installer", + "prerelease": false, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.6", + "created_at": "2022-04-13T09:36:59Z", + "date": "2022-04-13", + "repo": "spn" + }, + { + "name": "v0.8.7", + "tag_name": "v0.8.7", + "body": "\r\n\r\n- Update SPN", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.7", + "created_at": "2022-03-24T14:48:36Z", + "date": "2022-03-24", + "repo": "portmaster" + }, + { + "name": "v0.4.5", + "tag_name": "v0.4.5", + "body": "\r\n\r\n- Reset crane update hook when stopping SPN\r\n- Stop SPN client manager correctly when not yet connected\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.5", + "created_at": "2022-03-24T14:46:21Z", + "date": "2022-03-24", + "repo": "spn" + }, + { + "name": "assets-v0.3.0", + "tag_name": "assets-v0.3.0", + "body": "\r\n\r\n- Update js assets for graph rendering\r\n- Refactor notifier icons, copy to go source tree for embedding\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/assets-v0.3.0", + "created_at": "2022-03-23T16:01:03Z", + "date": "2022-03-23", + "repo": "portmaster-ui" + }, + { + "name": "notifier-v0.3.0", + "tag_name": "notifier-v0.3.0", + "body": "\r\n\r\n- Switch to new embedded icon\r\n- Add SPN status support\r\n- Refactor notifier icons, copy to go source tree for embedding\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/notifier-v0.3.0", + "created_at": "2022-03-23T16:01:03Z", + "date": "2022-03-23", + "repo": "portmaster-ui" + }, + { + "name": "portmaster-v0.2.3", + "tag_name": "portmaster-v0.2.3", + "body": "\r\n\r\n- Always use \"view all\" as the defautl for app settings\r\n- Show blue dots for settings-subsystems as well\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.2.3", + "created_at": "2022-03-23T16:01:03Z", + "date": "2022-03-23", + "repo": "portmaster-ui" + }, + { + "name": "v0.8.6", + "tag_name": "v0.8.6", + "body": "\r\n\r\n- Fix metrics for connections going through SPN\r\n- Show system notification when fixing electron sandbox fails\r\n- Always apply electron sandbox SUID fix\r\n- Mark config options as sensitive\r\n- Add debug interfaces for wfp and iptables\r\n- Set recursion available flag on nameserver responses\r\n- Validate resolver config for unknown parameters\r\n- Add documentation for new parameters\r\n- Expand special service TLDs\r\n- Add support for search-only resolvers\r\n- Improve search scope validation and add configuration support\r\n- Split unattributed connections into to Unidentified App and Network Noise\r\n- Exempt IPv6 LAN (broadcast domain only) from SPN\r\n- Fix checking if existing pid-lock process is portmaster-start", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.6", + "created_at": "2022-03-23T15:04:43Z", + "date": "2022-03-23", + "repo": "portmaster" + }, + { + "name": "v0.4.4", + "tag_name": "v0.4.4", + "body": "\r\n\r\n- Improve SPN client health check triggers and stop old connection when reconnecting\r\n- Mark config options as sensitive\r\n- Add debug info for SPN\r\n- Improve spn client lifecycle\r\n- Improve terminal abandoning", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.4", + "created_at": "2022-03-22T12:51:53Z", + "date": "2022-03-22", + "repo": "spn" + }, + { + "name": "portmaster-v0.2.2", + "tag_name": "portmaster-v0.2.2", + "body": "\r\n\r\n- Use drop-down option tooltips for value description\r\n- Add support for option descriptions in the drop-down via tooltips\r\n- Add maximum width for tooltip\r\n- Display blue dots when settings got changed. Fixes #206", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.2.2", + "created_at": "2022-03-02T09:18:54Z", + "date": "2022-03-02", + "repo": "portmaster-ui" + }, + { + "name": "v0.8.5", + "tag_name": "v0.8.5", + "body": "\r\n\r\n- Improve dns / exit policy and routing alg interaction\r\n- Update SPN settings order\r\n- Integrate SPN route manipulation settings\r\n- Add per app SPN settings\r\n- Add endpoint list validation regex and function\r\n- Add config option annotation key for verdict names\r\n- Simplify secure DNS bypass message creation\r\n- Update portbase to v0.14.0\r\n- Improve secure DNS bypass notification\r\n- Enable build for arm64 platform\r\n- Add validation for DNS server config\r\n- Stop useless updating of app compat warning\r\n- Fix verdicts of DNS request connections\r\n- Only hide successful queries of the system resolver\r\n- Fix bypass detection to correctly attribute encrypted DNS bypassing", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.5", + "created_at": "2022-03-02T09:10:22Z", + "date": "2022-03-02", + "repo": "portmaster" + }, + { + "name": "v0.4.3", + "tag_name": "v0.4.3", + "body": "Changelog\r\n\r\n- Abort crane msg submitting when crane is shutting down\r\n- Add function to check if any hub policies are set\r\n- Improve and add home / dns exit hub policy parsing\r\n- Fix and improve session path checking\r\n- Update SPN settings order\r\n- Check existing hub route before using in new route\r\n- Integrate SPN route manipulation settings\r\n- Add home and DNS exit node rules", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.3", + "created_at": "2022-03-02T08:58:32Z", + "date": "2022-03-02", + "repo": "spn" + }, + { + "name": "v0.8.4", + "tag_name": "v0.8.4", + "body": "Changelog v0.8.4:\r\n\r\n- Update SPN to v0.4.2", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.4", + "created_at": "2022-02-24T09:06:26Z", + "date": "2022-02-24", + "repo": "portmaster" + }, + { + "name": "portmaster-v0.2.1", + "tag_name": "portmaster-v0.2.1", + "body": "\r\n\r\n- Only show interfering settings for SPN quick setting button when SPN is enabled\r\n- Fix \"Use SPN\" not correctly detecting disabled state\r\n- Only show interfering settings for SPN quick setting button when enabled\r\n- Implement review suggestions\r\n- Use default shadow in app-view statistics due to visual gliches\r\n- Add support for custom rule list verdict names\r\n- Use correct settings key for use-spn interfering settings detection\r\n- Add quick settings support for Internet and Use SPN\r\n- Fix global value not being displayed for toggle-switches in app settings\r\n- Support jumping to the global setting from an app-settings tooltip\r\n- Add rich tooltip support and keep open when hovering the tooltip content\r\n- Update Accordion components to use sfng prefix\r\n- Remove obsolete debug components\r\n- Rename AppSettingsPageComponent to AppViewComponent to better match the new purpose\r\n- Rename app-settings to app-view to match new purpose\r\n- Cleanup MutationObserver in tooltip on destroy\r\n- Add tooltip component for small inline-help\r\n- Update issue manager workflow", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.2.1", + "created_at": "2022-02-24T08:59:35Z", + "date": "2022-02-24", + "repo": "portmaster-ui" + }, + { + "name": "v0.8.3", + "tag_name": "v0.8.3", + "body": "\r\n\r\n- Remove manual timestamp from compatibility warnings\r\n- Update network rating setting wording\r\n- Fully disable force block settings by default, allow \"off\" for all security level settings\r\n- Update go workflow", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.3", + "created_at": "2022-02-24T08:58:53Z", + "date": "2022-02-24", + "repo": "portmaster" + }, + { + "name": "v0.4.2", + "tag_name": "v0.4.2", + "body": "\r\n\r\n- Remove test phase button from SPN status notification\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.2", + "created_at": "2022-02-23T10:00:38Z", + "date": "2022-02-23", + "repo": "spn" + }, + { + "name": "v0.8.2", + "tag_name": "v0.8.2", + "body": "\r\n\r\n- Add setting category to network rating setting\r\n- Improve handling of layered profile on profile update\r\n- Fix profile config parsing\r\n- Fix deleting profiles\r\n- Remove deprecated MarkUsed functions", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.2", + "created_at": "2022-02-16T10:18:39Z", + "date": "2022-02-16", + "repo": "portmaster" + }, + { + "name": "v0.8.1", + "tag_name": "v0.8.1", + "body": "\r\n\r\n- Bump versions\r\n- Update deps\r\n- Fix go build flags", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.1", + "created_at": "2022-02-14T15:32:39Z", + "date": "2022-02-14", + "repo": "portmaster" + }, + { + "name": "v0.4.1", + "tag_name": "v0.4.1", + "body": "\r\n\r\n- Update deps", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.4.1", + "created_at": "2022-02-14T15:20:33Z", + "date": "2022-02-14", + "repo": "spn" + }, + { + "name": "portmaster-v0.2.0", + "tag_name": "portmaster-v0.2.0", + "body": "\r\n\r\n- Change order of icons and add small border\r\n- Show message if no apps match the search term\r\n- Fix tip up anchor size in app settings\r\n- Show app description and add warning to details tab name\r\n- Fix spacing in app overview\r\n- Remove deprecated ApproxLastUsed\r\n- Add tab component and rework app settings to new app-centric design\r\n- Implement changes as discussed in review\r\n- Move \"Reset to\" label in settings to the right\r\n- Add blue line to setting if it was changed by the user\r\n- Add space at the end of the settings list\r\n- Change color of settings key and remove commented code\r\n- Increase toggle-switch size a bit\r\n- Fix disabled state not working for dropdown\r\n- Allow settings to be changed even when locked and unlock automatically\r\n- Update app settings component to enable user-changed markers for config settings\r\n- Update config view component to new style and support collapsible categories\r\n- Update styling of generic settings component\r\n- Update styling for ordered list settings and remove use of legacy color names\r\n- Update styling for rule list settings and remove use of legacy color names\r\n- Update basic settings component for better input focus UX\r\n- Update security level switch to use toggle-switch in on/off mode\r\n- Update multi-switch box and spacing to allow better centering\r\n- Update styling of drop-down component and remove use of legacy color names\r\n- Menu component should have the same minimum width than it's trigger\r\n- Removed testing code in support-page that should not have been merged\r\n- Improved tip up components to handle stacking and support dynamic tip up contents\r\n- Update styling of text inputs and search highlighting\r\n- Create dedicated toggle-switch component instead of using (ab)using multi-switch\r\n- Update tailwindcss configuration for better color support", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.2.0", + "created_at": "2022-02-14T13:29:45Z", + "date": "2022-02-14", + "repo": "portmaster-ui" + }, + { + "name": "v0.8.0", + "tag_name": "v0.8.0", + "body": "\r\n\r\n- Add notification if IPv6 network integration fails\r\n- Fix nameserver takeover loop\r\n- Fix nameserver listener restarts\r\n- Improve empty list matching\r\n- Fix incoming rules for system resolver\r\n- Add profile descriptions for all internal profiles and apply them with the metadata\r\n- Remove deprecated ApproxLastUsed field of profile\r\n- Use period time format for all workflow labels\r\n- Remove broken network key prefix check\r\n- Don't allow wildcard suffix domain rules that look like an address range rule\r\n- Fix fast-tracking non-echo ICMP/v6 messages\r\n- Fix tests and linters\r\n- Update test script, config and workflow", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.8.0", + "created_at": "2022-02-14T13:25:22Z", + "date": "2022-02-14", + "repo": "portmaster" + }, + { + "name": "v0.7.21", + "tag_name": "v0.7.21", + "body": "\r\n\r\n- Update SPN to v0.3.19", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.7.21", + "created_at": "2022-01-31T10:09:06Z", + "date": "2022-01-31", + "repo": "portmaster" + }, + { + "name": "v0.3.19", + "tag_name": "v0.3.19", + "body": "\r\n\r\n- Increase queue sizes", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.3.19", + "created_at": "2022-01-31T10:06:30Z", + "date": "2022-01-31", + "repo": "spn" + }, + { + "name": "v0.7.20", + "tag_name": "v0.7.20", + "body": "\r\n\r\n- Derive release channel by index presence, remove unused indexes from core", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.7.20", + "created_at": "2022-01-27T08:54:21Z", + "date": "2022-01-27", + "repo": "portmaster" + }, + { + "name": "app-electron-v0.2.3", + "tag_name": "app-electron-v0.2.3", + "body": "\r\n\r\n- Upgrade electron to v16\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/app-electron-v0.2.3", + "created_at": "2022-01-26T14:49:55Z", + "date": "2022-01-26", + "repo": "portmaster-ui" + }, + { + "name": "assets-v0.2.5", + "tag_name": "assets-v0.2.5", + "body": "\r\n\r\n- Add libraries for graph rendering\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/assets-v0.2.5", + "created_at": "2022-01-26T14:49:55Z", + "date": "2022-01-26", + "repo": "portmaster-ui" + }, + { + "name": "notifier-v0.2.4", + "tag_name": "notifier-v0.2.4", + "body": "\r\n\r\n- Update notifier deps\r\n- Use warning color when restarting\r\n- Cleanup app resources properly\r\n- Don't hide status message\r\n- Shorten status message\r\n- Update notifier to wait for connection loss in shutdown/restart\r\n- Hide network rating buttons in notifier according to setting\r\n", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/notifier-v0.2.4", + "created_at": "2022-01-26T14:49:55Z", + "date": "2022-01-26", + "repo": "portmaster-ui" + }, + { + "name": "portmaster-v0.1.25", + "tag_name": "portmaster-v0.1.25", + "body": "\r\n\r\n- Display alive connection count in developer mode and add dbl-click to SPN page\r\n- Add shutdown/restart overlays\r\n- Update UI dependencies to latest patch version\r\n- Use hostname instead of a hardcoded localhost for websocket connections\r\n- Hide network rating buttons in notifier according to setting\r\n- Use on/off toggles instead of security level switch if network rating is disabled", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.1.25", + "created_at": "2022-01-26T14:49:55Z", + "date": "2022-01-26", + "repo": "portmaster-ui" + }, + { + "name": "v0.7.19", + "tag_name": "v0.7.19", + "body": "\r\n\r\n- Update SPN\r\n- Revert dependency changes for clean merge\r\n- Fix network detection with multiple interfaces on same net\r\n- Fix geolocation lookup errors during device location estimation\r\n- Weigh coordinate distance stronger\r\n- Fix matching unknown AS Orgs\r\n- Test for /proc/self/ns/user instead of sysctl\r\n- Fix version number\r\n- Use new migration system for network-rating migration\r\n- Move network rating config key to stable\r\n- Add support to enable/disable the network rating system", + "prerelease": false, + "html_url": "https://github.com/safing/portmaster/releases/tag/v0.7.19", + "created_at": "2022-01-26T14:43:20Z", + "date": "2022-01-26", + "repo": "portmaster" + }, + { + "name": "v0.3.18", + "tag_name": "v0.3.18", + "body": "Changelog\r\n\r\n- Improve hub validation and fix locking in import\r\n- Abort hub import earlier when received messages don't match expected Hub\r\n- Add virtual network support\r\n- Remove test logging\r\n- Improve terminal errors to eliminate special space\r\n- Fix hub forwarding on import\r\n- Increase costs of unmeasured connections\r\n- Use correct logging lib\r\n- Add stopping time for api table outputs\r\n- Remove unused variables\r\n- Add regions for optimization\r\n- Raise hub costs to better match lane costs\r\n- Increase capacity test volume to 50MB again\r\n- Add time limit to stopping cranes\r\n- Don't die when the intel update fails on startup\r\n- Disable kcp until we find a replacement\r\n- Update QueueSize to uint32 and increase controller queue size\r\n- Sync crane status to connected Hub\r\n- Remove unnecessary check\r\n- Reduce default capacity test volume to 25MB\r\n- Make measurement TTL dynamic to save bandwidth\r\n- Improve pin update order\r\n- Increase timeouts related to verifying Hubs", + "prerelease": false, + "html_url": "https://github.com/safing/spn/releases/tag/v0.3.18", + "created_at": "2022-01-26T14:37:53Z", + "date": "2022-01-26", + "repo": "spn" + }, + { + "name": "v0.3.17", + "tag_name": "v0.3.17", + "body": "\r\n\r\n- Add support for discontinued Hubs, fix Hub deletion", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.3.17", + "created_at": "2022-01-25T15:15:36Z", + "date": "2022-01-25", + "repo": "spn" + }, + { + "name": "v0.3.16", + "tag_name": "v0.3.16", + "body": "\r\n\r\n- Save tunnel context after updating", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.3.16", + "created_at": "2022-01-21T15:15:17Z", + "date": "2022-01-21", + "repo": "spn" + }, + { + "name": "v0.3.15", + "tag_name": "v0.3.15", + "body": "\r\n\r\n- Improve and stabilize sorting with geo proximity and Hub ID\r\n- Add geoip proximity to measurements\r\n- Fix intel data loading after SPN module restart\r\n- Enable waiting for measurements\r\n- Improve measurement intervals\r\n- Switch default back to TCP", + "prerelease": false, + "html_url": "https://github.com/safing/spn/releases/tag/v0.3.15", + "created_at": "2022-01-20T08:52:04Z", + "date": "2022-01-20", + "repo": "spn" + }, + { + "name": "v0.3.14", + "tag_name": "v0.3.14", + "body": "\r\n\r\n- Decrease allowed Hub name lengths\r\n- Fix application of intel overrides\r\n- Add crane traffic stats\r\n- Permit user-level localhost API access", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.3.14", + "created_at": "2022-01-19T10:25:59Z", + "date": "2022-01-19", + "repo": "spn" + }, + { + "name": "v0.3.13", + "tag_name": "v0.3.13", + "body": "\r\n\r\n- Disable min measurements for smoother migration to new hub version\r\n- Add yaml parser dependency\r\n- Add sysctl for server configuration\r\n- Improve simulation test setup\r\n- Enable and switch to kcp by default\r\n- Improve stats with new measurements\r\n- Delete obsolete Hubs from database\r\n- Improve latency and capacity ops\r\n- Improve network optimization with measurements\r\n- Improve Terminal errors\r\n- Add measurements framework\r\n- Improve maintain status function signature\r\n- Add InfoOverrides to the Intel data and switch to new source\r\n- Add Offline state to Pin\r\n- Update location proximity to use a float\r\n- Fix and improve initial metrics\r\n- Send offline status message when shutting down", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.3.13", + "created_at": "2022-01-18T14:55:33Z", + "date": "2022-01-18", + "repo": "spn" + }, + { + "name": "v0.3.12", + "tag_name": "v0.3.12", + "body": "\r\n\r\n- Cut off far away Hubs when searching for nearest\r\n- Improve route cost calculation", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.3.12", + "created_at": "2021-12-23T15:54:51Z", + "date": "2021-12-23", + "repo": "spn" + }, + { + "name": "portmaster-v0.1.24", + "tag_name": "portmaster-v0.1.24", + "body": "\r\n\r\n- Remove SPN plan override\r\n- Add new no-icon icon", + "prerelease": true, + "html_url": "https://github.com/safing/portmaster-ui/releases/tag/portmaster-v0.1.24", + "created_at": "2021-12-23T14:10:33Z", + "date": "2021-12-23", + "repo": "portmaster-ui" + }, + { + "name": "v0.3.11", + "tag_name": "v0.3.11", + "body": "\r\n\r\n- Add basic metrics\r\n- Add option to specify main spn map name and update simple testing env\r\n- Log new values for latency, capacity and load\r\n- Adjust hub costs to updated cost calculation\r\n- Update map graph api with new data\r\n- Improve cost calculation with new data\r\n- Maintain load, latency and capacity and publish via status\r\n- Add effective bandwidth test based on the capacity op\r\n- Tweak flow queue for higher bandwidth\r\n- Fix capacity op and improve its test\r\n- Simplify tests with new exposed TestTerminal\r\n- Add Flush() to terminal interfaces\r\n- Add capacity op\r\n- Add latency op\r\n- Add latency and capacity fields/functions to crane\r\n- Expose and improve test terminal\r\n- Improve terminal error helpers and fix small issues", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.3.11", + "created_at": "2021-12-22T10:36:29Z", + "date": "2021-12-22", + "repo": "spn" + }, + { + "name": "v0.3.10", + "tag_name": "v0.3.10", + "body": "\r\n\r\n- Improve inactive subscription notification", + "prerelease": true, + "html_url": "https://github.com/safing/spn/releases/tag/v0.3.10", + "created_at": "2021-12-06T11:42:33Z", + "date": "2021-12-06", + "repo": "spn" + } +] diff --git a/_data/releases/config.yml b/_data/releases/config.yml new file mode 100644 index 0000000..1e055ad --- /dev/null +++ b/_data/releases/config.yml @@ -0,0 +1,18 @@ +repos: + - id: portmaster + name: "Portmaster" + resource: "windows_amd64/core/portmaster-core.exe" + - id: spn + name: "SPN" + resource: "linux_amd64/hub/spn-hub" + - id: portmaster-ui + tag-names: + portmaster: "UI" + notifier: "Notifier" + assets: "UI Assets" + app-electron: "UI App" + tag-resources: + portmaster: "all/ui/modules/portmaster.zip" + notifier: "windows_amd64/notifier/portmaster-notifier.exe" + assets: "all/ui/modules/assets.zip" + app-electron: "windows_amd64/app/portmaster-app.zip" diff --git a/_data/versions/beta.json b/_data/versions/beta.json new file mode 100644 index 0000000..33da72c --- /dev/null +++ b/_data/versions/beta.json @@ -0,0 +1,39 @@ +{ + "Channel": "beta", + "Published": "2022-10-19T12:43:20Z", + "Releases": { + "all/ui/modules/assets.zip": "0.3.1", + "all/ui/modules/portmaster.zip": "0.4.2", + "darwin_amd64/core/portmaster-core": "1.0.0", + "darwin_amd64/jess/jess": "0.3.1", + "darwin_amd64/start/portmaster-start": "1.0.0", + "darwin_arm64/core/portmaster-core": "1.0.0", + "darwin_arm64/jess/jess": "0.3.1", + "darwin_arm64/start/portmaster-start": "1.0.0", + "linux_all/packages/install.sh": "1.0.0", + "linux_all/packages/installer-assets.tar.gz": "1.0.0", + "linux_amd64/core/portmaster-core": "1.0.0", + "linux_amd64/jess/jess": "0.3.1", + "linux_amd64/notifier/portmaster-notifier": "0.3.5", + "linux_amd64/packages/portmaster-installer.deb": "1.0.0", + "linux_amd64/packages/portmaster-installer.rpm": "1.0.0", + "linux_amd64/start/portmaster-start": "1.0.0", + "linux_arm64/core/portmaster-core": "1.0.0", + "linux_arm64/jess/jess": "0.3.1", + "linux_arm64/notifier/portmaster-notifier": "0.3.5", + "linux_arm64/start/portmaster-start": "1.0.0", + "windows_amd64/core/portmaster-core.exe": "1.0.0", + "windows_amd64/jess/jess.exe": "0.3.1", + "windows_amd64/kext/portmaster-kext.dll": "1.0.14", + "windows_amd64/kext/portmaster-kext.pdb": "1.0.14", + "windows_amd64/kext/portmaster-kext.sys": "1.0.14", + "windows_amd64/notifier/portmaster-notifier.exe": "0.3.5", + "windows_amd64/notifier/portmaster-wintoast.dll": "0.1.4", + "windows_amd64/packages/portmaster-installer.exe": "1.0.0", + "windows_amd64/start/portmaster-start.exe": "1.0.0", + "windows_arm64/core/portmaster-core.exe": "1.0.0", + "windows_arm64/jess/jess.exe": "0.3.1", + "windows_arm64/notifier/portmaster-notifier.exe": "0.3.5", + "windows_arm64/start/portmaster-start.exe": "1.0.0" + } +} \ No newline at end of file diff --git a/_data/versions/stable.json b/_data/versions/stable.json new file mode 100644 index 0000000..7fa24bc --- /dev/null +++ b/_data/versions/stable.json @@ -0,0 +1,54 @@ +{ + "Channel": "stable", + "Published": "2022-10-20T06:37:10Z", + "Releases": { + "all/intel/geoip/geoipv4.mmdb.gz": "20220804.11.58", + "all/intel/geoip/geoipv6.mmdb.gz": "20220804.12.24", + "all/ui/modules/assets.zip": "0.3.1", + "all/ui/modules/base.zip": "0.2.11", + "all/ui/modules/console.zip": "0.1.11", + "all/ui/modules/monitor.zip": "0.2.4", + "all/ui/modules/portmaster.zip": "0.4.2", + "all/ui/modules/profilemgr.zip": "0.1.7", + "all/ui/modules/settings.zip": "0.1.8", + "darwin_amd64/core/portmaster-core": "1.0.0", + "darwin_amd64/hub/spn-hub": "0.5.1", + "darwin_amd64/jess/jess": "0.3.1", + "darwin_amd64/start/portmaster-start": "1.0.0", + "darwin_arm64/core/portmaster-core": "1.0.0", + "darwin_arm64/jess/jess": "0.3.1", + "darwin_arm64/start/portmaster-start": "1.0.0", + "linux_all/packages/install.sh": "1.0.0", + "linux_all/packages/installer-assets.tar.gz": "1.0.0", + "linux_amd64/app/portmaster-app.zip": "0.2.5", + "linux_amd64/core/portmaster-core": "1.0.0", + "linux_amd64/hub/spn-hub": "0.5.1", + "linux_amd64/jess/jess": "0.3.1", + "linux_amd64/notifier/portmaster-notifier": "0.3.5", + "linux_amd64/packages/portmaster-installer.deb": "1.0.0", + "linux_amd64/packages/portmaster-installer.rpm": "1.0.0", + "linux_amd64/start/portmaster-start": "1.0.0", + "linux_arm64/app/portmaster-app.zip": "0.2.5", + "linux_arm64/core/portmaster-core": "1.0.0", + "linux_arm64/jess/jess": "0.3.1", + "linux_arm64/notifier/portmaster-notifier": "0.3.5", + "linux_arm64/start/portmaster-start": "1.0.0", + "windows_amd64/app/portmaster-app.zip": "0.2.5", + "windows_amd64/core/portmaster-core.exe": "1.0.0", + "windows_amd64/hub/spn-hub.exe": "0.5.1", + "windows_amd64/jess/jess.exe": "0.3.1", + "windows_amd64/kext/portmaster-kext.dll": "1.0.14", + "windows_amd64/kext/portmaster-kext.pdb": "1.0.14", + "windows_amd64/kext/portmaster-kext.sys": "1.0.14", + "windows_amd64/notifier/portmaster-notifier.exe": "0.3.5", + "windows_amd64/notifier/portmaster-snoretoast.exe": "0.6.0", + "windows_amd64/notifier/portmaster-wintoast.dll": "0.1.4", + "windows_amd64/packages/portmaster-installer.exe": "1.0.0", + "windows_amd64/start/portmaster-start.exe": "1.0.0", + "windows_arm64/app/portmaster-app.zip": "0.2.5", + "windows_arm64/core/portmaster-core.exe": "1.0.0", + "windows_arm64/jess/jess.exe": "0.3.1", + "windows_arm64/notifier/portmaster-notifier.exe": "0.3.5", + "windows_arm64/start/portmaster-start.exe": "1.0.0" + } +} \ No newline at end of file