-
Notifications
You must be signed in to change notification settings - Fork 19
Expire VPN order credentials
Stephen Donner edited this page Jan 20, 2023
·
5 revisions
- install latest Brave Beta (or Release Candidate) build
- launch Brave
- purchase and configure a
BraveVPN
connection viaaccount.bravesoftware.com
- quit Brave (disconnect from
BraveVPN
, if connected) - download expire-tlv2-order.sh
- edit its path to be
cd ~/Library/Application\ Support/BraveSoftware/Brave-Browser-Beta/
and save changes/exit -
chmod 0777 expire-tlv2-order.sh
(to make it script-executable on macOS) ./expire-tlv2-order.sh
- if it succeeds, it'll return/exit silently
- you should now have the following files:
Local\ State
,Local\ State.new
, and something likeLocal State.Thu Jan 19 21:34:18 PST 2023
- the last file w/timestamp is the original;
Local\ State
andLocal\ State.new
should be identical, as.new
is copied over to replace the originalLocal\ State
file - launch Brave
- click on the
VPN
button in the browser toolbar
- prompts user to add
BraveVPN
macOS network config - after doing so, connects to
BraveVPN
Am expecting to see an appropriate "credentials have expired" message; see bottom note for more detail
Should this be the Edit payment method
dialog? (Figma design)
===== Changes the script makes to Local\ State
: =====
- sets "expires_at" to be
current date
+00:00:00
(is this the same asorders->expires_at to be yesterdays date
from the testing doc?) - removes all
unblinded_creds
entries in the list which have avalid_to
greater than today
According to the Manipulate SKUs State testing doc, line 11:
Start Browser, attempt to use VPN, you should not have any valid credentials and the order should be expired, this should cause us to be in expired state.