You should use a separate access token/password for each client with restricted permissions, that would be the standard security procedure. Handing your password to another machine is *never* secure, encrypted/compiled or not.
In this case it looks like you should simply make the information available through a public API/database instead of fetching e-mail. But, a quick hack is to just create a new e-mail account, and forward all mail there. That way if someone does something bad with it you just create another one. You could even create a separate account for each user if it's a small-scale app. On Wednesday, January 9, 2013 8:31:55 AM UTC-2, Koti Kanna wrote: > > Hi all, > > I am using npm module imap to fetch emails. where it requires username and > password to fetch mails. This mail client i am hosting on a third party > machine. My worry is, if any body open this file they can actually see my > user name and password. Is there any way to precompile this module into > machine code? > > Do you have any plans to support executables for nodejs Apps, before it > touches version 1.0? > > Thanks > Koti > > P.S.: The one and only language right now i know is JavaScript. > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
