You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Plans to address HTTP fallback, Electron security settings, and token storage? #98
Hi! I’m interested in using Liner, but I have a few security questions.
1. HTTP fallback in v0.1.35
baseUrl.ts switches to http://edge.tryliner.fun:10518 when the primary API is unavailable. Since authentication requests also use this API base, it looks like passwords and session tokens could be sent without transport encryption.
I see the fallback is disabled in main. Has this fix reached users through an OTA update, or does it require a new release?
2. Electron security settings
main.ts sets both sandbox: false and webSecurity: false.
What requires these settings, and are there plans to enable these protections?
3. Token storage
auth-session.ts stores access and refresh tokens in localStorage.
Are there plans to move sensitive tokens to OS-backed secure storage and limit their exposure to the renderer?
Could you clarify which of these are planned fixes and which are intentional design choices? If fixes are planned, is there a target release?
HTTP fallback:#28 (merged) stops the app from falling back to plain HTTP, and #85 removes the remaining code. It's in main but not in a release yet: the latest is still 0.1.35.
sandbox and webSecurity:#11 turns on webSecurity, enables the sandbox and limits the injected CORS headers to known hosts. It's still in review.
Token storage:#11 also moves the session out of localStorage into encrypted storage through safeStorage.
None of these are meant as design choices. When they ship is up to the maintainers.
Activity
loreofmin-ux commentedon Oct 17, 2026
Thanks for raising these, they're fair points!
HTTP fallback: #28 (merged) stops the app from falling back to plain HTTP, and #85 removes the remaining code. It's in
mainbut not in a release yet: the latest is still 0.1.35.sandboxandwebSecurity: #11 turns onwebSecurity, enables the sandbox and limits the injected CORS headers to known hosts. It's still in review.Token storage: #11 also moves the session out of
localStorageinto encrypted storage throughsafeStorage.None of these are meant as design choices. When they ship is up to the maintainers.
feralbureau commentedon Oct 18, 2026
fixed