You can try this direct VBA approach which doesn’t require HEX editing. It will work for any files (*.xls, *.xlsm, *.xlam …). Tested and works on: Excel 2007 Excel 2010 Excel 2013 – 32 bit version Excel 2016 – 32 bit version Looking for 64 bit version? See this answer How it works I will … Read more
Why password validation rules are bad? Our very own Jeff Atwood (blogger of Coding Horror and co-founder of Stack Overflow and Stack Exchange) wrote a blog about password rules back in March of 2017 titled Password Rules are Bullshit. If you haven’t read this post, I would urge you to do so as it greatly … Read more
Share the password (a char[]) and salt (a byte[]—8 bytes selected by a SecureRandom makes a good salt—which doesn’t need to be kept secret) with the recipient out-of-band. Then to derive a good key from this information: /* Derive the key, given password and salt. */ SecretKeyFactory factory = SecretKeyFactory.getInstance(“PBKDF2WithHmacSHA256”); KeySpec spec = new PBEKeySpec(password, … Read more
You are correct that storing the password in a plain-text field is a horrible idea. However, as far as location goes, for most of the cases you’re going to encounter (and I honestly can’t think of any counter-examples) storing the representation of a password in the database is the proper thing to do. By representation … Read more
DISCLAIMER: This answer was written in 2008. Since then, PHP has given us password_hash and password_verify and, since their introduction, they are the recommended password hashing & checking method. The theory of the answer is still a good read though. TL;DR Don’ts Don’t limit what characters users can enter for passwords. Only idiots do this. … Read more
bcrypt is a hashing algorithm which is scalable with hardware (via a configurable number of rounds). Its slowness and multiple rounds ensures that an attacker must deploy massive funds and hardware to be able to crack your passwords. Add to that per-password salts (bcrypt REQUIRES salts) and you can be sure that an attack is … Read more
Strings are immutable. That means once you’ve created the String, if another process can dump memory, there’s no way (aside from reflection) you can get rid of the data before garbage collection kicks in. With an array, you can explicitly wipe the data after you’re done with it. You can overwrite the array with anything … Read more
If you want to restrict user to enter minimum 8 character password which will contain upper and lower case letter and one special character you can use regular expression like ^((?=(?:.*[a-zA-Z]){7})(?=(?:.*[@#$%^?])).{8})$
\u is a special code in printf; your code contains \username which is causing the error you are getting. I suspect you just have a typo there; if not, represent a backslash in printf with \\. Per @Jim Balter’s comment, you probably used \ where you meant /.
Project -> Clean seems to be the only solution to me. Trying cleaning your project a few times and then build it.