-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
VITE_SESSION_SECRET #24
Comments
I also think that it should not be prefixed with vite, but solid docs do prefix it (making it public to the client) so I'm not sure which is the correct answer? |
Yes I noticed the same in the Solid documentation. I think this is wrong and could (do?) leak the session secret. I'll move this to |
Make sure you separate the auth client and the session storage otherwise the client will try to parse server env variables (causing an error to be thrown on the browser), move the session storage to server/auth.ts if you do decide to do that |
It works well, thanks for the above tip 😉 – I was not aware everything under I'm pretty sure this should be the default. I don't have time right now to "hack" myself and see how I could retrieve the session secret. Although, based on Vite documentation, the session secret is (most probably) leaked with the current setup. |
Ye i think so too, |
maybe include https://github.com/t3-oss/t3-env as part of the addon? |
Thank you for this great utility!
In
utils/auth.ts
, you use:According to the security notes in https://vitejs.dev/guide/env-and-mode.html#env-files:
Isn't it concerning or did I misunderstand something?
The text was updated successfully, but these errors were encountered: