https://discord.cloudflare.com logo
Join Discord
Powered by
# functions
  • i
    There's a pure-Javascript bcrypt module called bcryptjs, but since it's pure JS it will need more CPU than you get on the free plan
  • i
  • s
    Looks like https://github.com/cloudflare/next-on-pages/issues/1 will need to be resolved first
  • s
    Is it supported on paid plans ?
  • i
    I haven't used it personally but others have, yes. I understand it takes a few hundred milliseconds
  • i
    If you try it on a free plan it should run and you can see how it works
  • i
    you don't automatically get killed when you hit the cpu limit so for a few requests it should work
  • s
    Thanks I will take a look
  • z
    Definitely use the crypto stuff that’s built in, not the js bcrypt 🙂
  • s
    built in is just sha512 right ?
  • s
    is this oke to use for user data ?
  • i
    I don't see why not, and it would be easier and faster and one less dependency
  • z
    You get a bunch of SHAs and MD5. Depends on your use case, but SHA512 should work for most things
  • s
    oke thanks people
  • w
    I appreciate the fix 🙂 Please keep them coming!
  • w
    SHA is not good for passwords
  • w
    But for like integrity yes
  • s
    how should I store and hash passwords with workers then, if they can't use « standards » like bcrypt ?
  • z
    Yeah i wasn’t thinking of passwords when i heard “hashing”. I’m don’t know if any of the web crypto algos CF gives you are appropriate…
  • z
    Maybe this PBKDF2 (but see note at top and comments) https://gist.github.com/chrisveness/770ee96945ec12ac84f134bf538d89fb
  • z
    Based on your use case you might want that js bcrypt after all… but you’ll probably need to use unbound
  • j
    Yeah you can definitely use bcrypt or argon2 with Workers, but you'll need more CPU time via unbound
  • s
    can I somehow calculate the costs beforehand ?
  • j
    https://pricing.ceru.dev/ will be your best bet
  • j
    You get a healthy amount for free in the base paid plan - more than enough to test and get an idea for how long it'll take, and you can then estimate costs
  • s
    I'm so confused of 'how long does the worker run'
  • s
    where can I test this ?
  • s
    I will be way way way below 100 000 requests per months
  • s
    I may be even not hitting 1000
  • j
    I believe wrangler will tell you the response time for a request, which should give you some idea. You can also check the worker stats in the dash too
1...307308309...392Latest