[01:17:16] <ixti> are there any known issues with $inc/$set operations on nested documents (e.g. { "$inc": { "foo.bar": 1 } })
[01:17:42] <zzing> Are there any examples of implementing a user authentication system inside of a mongo database, that is separate from the regular authentication mechanism? Specifically the kind of thing a blog might implement where it just uses a single account for the mongo database to access the data.
[01:18:22] <ixti> nm. just realized that i misunderstood original problem described in issue
[21:59:17] <wasbazi> Anyone in here feel like discussing MongoDB vulnerabilities other than "don't use eval" (cause that's what the internet is telling me)
[22:05:28] <kexmex> wasbazi: what other ones do you know of?
[22:06:30] <kexmex> sucks that bson is json-like so if you are getting user input, its hard to sanitize it really
[22:07:37] <wasbazi> I don't really know much about it at all.
[22:07:55] <wasbazi> I'm building my first node/express/mongoose app and I've done user auth with php/mysql before.
[22:08:20] <wasbazi> So I thought, oh ya SQL injection. I shouldn't use user data directly from the client, how do I protect it in JS...
[22:15:30] <kexmex> parse the json, look at the attributes, if attribute is enum check if it matches enum values, or if an integer, that it's within range, if string, not too long, check character set with regexp…and so on
[22:18:38] <wasbazi> I guess that makes some sense. So just some basic checks for type/length and I shouldn't have to worry too much on it.
[22:22:42] <beepbeep_> when working with mongodb, always use ObjectId for id's?
[22:23:07] <beepbeep_> Do you use another unique identifier for in apps?