It would be better to use bcrypt, beause its more secure as it's slower (uses more computing cycles).
Your code could also be better:

You wouldn't need salt field in User model, because it's saved into the same field as password does.

For authentication, something like:

var mongoose = require('mongoose'),
  bcrypt = require('bcryptjs');

var userSchema = mongoose.Schema({
  email: String,

Describe the bug

To Reproduce

• Upload a file from Widget/Facebook with a long file name.
• View the conversation in the agent dashboard.

Is your feature request related to a problem?

Please describe.

Feature flags currently can only be toggled on and off, but not deleted.

Describe the solution you'd like

A delete button.

Describe alternatives you've considered

Repurposing old feature flags for new ones.

Additional context

Thank you for your feature request – we love each and every on

This name is just the default event used when generating new channels in Phoenix, but let's make our event names a bit more descriptive... we already have conversation:created and conversation:updated events, so let's be consistent and add message:created in place of shout.

(Note: we'll probably need to keep "shout" around for backwards compatibility)

Context

• This is part of release-1.5 #148
• MEDIUM priority task

Tasks

• Remove dependency bcrypt-nodejs in package.json
• Add dependency bcrypt in package.json
• Migrate file app/data/user-dao.js to bcrypt
• Validate the instalation with the local test
• Add and submit the chang