-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Payments keep counting down after client disconnected #104
Comments
This makes the idea of prepaid authids to not work because it will run out of money even if not used. This must be a bug? |
If you want to add the feature of using remaining credit, please keep your system account-free (as it's now), otherwise there would be worry for users who use your service through a 3rd party vpn, is he/she always started your program with the primary vpn on. |
This is feature from design, not bug. |
The payment "account" is the same as the payment id used. It is possible ti reconnect using paymentid@prividerid/serviceid and continue use it as long as balance is left on thus paymentid. The problem is that money is reduced no matter if connected or not. Hmm. So prepaying is not useful in order to use later. You need to keep adding small payments while you are connected. I was thinking like a refill option. Well you could have an intetermediate wallet for that if we keep current design. |
Yes, for now, it is recommended to use small payments. Recommended way for achieving more persistent authids is to define minimal minutes longer, like 1 month for some service. So uder can use this proxy entire month regardless of usage. But, again, security is playing role. More authids means more privacy. |
I have noticed in /opt/lthn/var/log/audit.log that payment balance for authids keep counting down to zero after client disconnected. Decided to test this.
Paid 9 LTHN to a provider that charge 0.05 LTHN/min so this should last 3 hours. Disconnected after approximately 10 minutes and the balance kept counting down until zero on exit node.
See attached logs.
Client_interaction.txt
Client_audit.log.txt
audit.log
lthnvpnd_debug.txt
The text was updated successfully, but these errors were encountered: