Comments (5)
I'm using prisma and only storing the sessionId in the cookie. I can probably share some best practices in the future, currently working something out.
from svelte-kit-cookie-session.
Hm good question, i think it should be safe to expose these values but i'm in no means a security expert. What you can do is to only expose the data you need on the client via getSession
, i always have some public data that i expose via getSession and private session data which i only use in my endpoints, handle etc. also i always use a secret thats > 32 characters or even 64.
from svelte-kit-cookie-session.
You are right. On top that, data from the session (the cookie) to be processed in the backend should have low trust since it remains essentially user input.
Do you use any ready made stuff for handling the server session ?:)
from svelte-kit-cookie-session.
So is the purpose of providing a secret key to sign the session data, rather than to encrypt it?
from svelte-kit-cookie-session.
I'm using prisma and only storing the sessionId in the cookie. I can probably share some best practices in the future, currently working something out.
So this way it's becoming a statefull solution right? Storing an ID inside the cookie, then use this ID to do a lookup in a database serverside? I'm thinking of doing something like that as well, using firestore as a database...
When you say best practices, what do you mean exactly?
from svelte-kit-cookie-session.
Related Issues (20)
- Setting rolling to true does not refresh expiration HOT 3
- Consider `SameSite=Lax` as a new default HOT 2
- Build Fails in Vercel HOT 2
- Could this work with @sveltejs/adapter-cloudflare? HOT 5
- Security of Hashing Algorithm HOT 3
- Is this safe against cookie theft and replay attacks after expiry? HOT 3
- Support for SvelteKit@next-415+ HOT 8
- Document cookie options HOT 2
- Session Cookie not being set in safari HOT 2
- Hook for setting initial session state HOT 2
- SvelteKit Session Cookie and Houdini HOT 1
- Version 3.3.0 compilation process is broken HOT 4
- Can't build when using env var as secret HOT 3
- Feat: Chunked cookies HOT 4
- Question: Svelte only compatible ? HOT 2
- Iniitalizing guide update HOT 1
- init() doesn't set initial cookie until set() or update() is called HOT 2
- Need to expire cookies in minutes instead of days. HOT 4
- Svelte 4? HOT 1
- Secure to pass sensitive session data to page?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from svelte-kit-cookie-session.