passwords

I have implemented a TextInputLayout with a password field in the usual way: <android.support.design.widget.TextInputLayout android:layout_width="match_parent" android:layout_height="wrap_content"> <EditText android:id="@+id/returning_password" android:layout_width="match_parent" android:layout_height="wrap_content" android:hint="@string/prompt_password" android:inputType="textPassword" android:maxLines="1" android:textSize="14sp" /> </android.support.design.widget.TextInputLayout> This worked fine when using the Android support library up to version 24.0.2, but after switching to 25.0.1:

On a modern Unix or Linux system, how can you tell which code set the /etc/passwd file stores user names in? Are user names allowed to contain accented characters (from the range 0x80..0xFF in, say, ISO 8859-1 or 8859-15)? Can the /etc/passwd file contain UTF-8? Can you tell that it contains UTF-8? What about the plain text of passwords before they are encrypted or hashed? Clearly, if the usernames and other data is limited to the 0x00..0x7F range (and excludes 0x00 anyway), then there is no difference between UTF-8, 8859-1 or 8859-15; the characters present are all encoded the same. Also, I'm

I'm facing a problem here, with HttpListener. When a request of the form http://user:password@example.com/ is made, how can I get the user and password ? HttpWebRequest has a Credentials property, but HttpListenerRequest doesn't have it, and I didn't find the username in any property of it. Thanks for the help. Matt Brindley What you're attempting to do is pass credentials via HTTP basic auth, I'm not sure if the username:password syntax is supported in HttpListener, but if it is, you'll need to specify that you accept basic auth first. HttpListener listener = new HttpListener(); listener

After the linkedin password hash leak, I've been looking at our password hashing. We using Django 1.4 which uses PBKDF2, which is great and a step up from the previous SHA1. However I'm curious how easily one could brute force that. I'm looking at our password complexity rules, and am wondering how fast it'd take to do (say) 8 length lower case ascii letters. This guide to cracking the LinkedIn password hash, has someone doing 430 million sha1 hashes per second on a GPU. http://erratasec.blogspot.ie/2012/06/linkedin-vs-password-cracking.html What kinda speeds would you get for PBKDF2? Does

Laravel uses bcrypt to hash passwords. According to this article, at some point in the process, the Hash::make function creates and uses a 22-length random string as a salt to generate the password. For a single distinct password, Hash::make does return unique hashes, hinting that it does use some kind of salting somewhere in the process. But these salts are not stored in the users table, where I would expect them. How does laravel know the appropriate hash to use to verify the password? Laravel Hash Explained The article that you linked seems to contain the answer. https://mnshankar.wordpress

How to set up my own password for accessing the h2 while working in embedded mode? (if anyone confused - talking about the root password for accessing the database) In Eclipse it seems that password assignment occurs at the moment of db connection creation which in turn launches the process of schema creation, where we provide username and password. Even if this is true how to change existing password after set up? I've searched in information schema - found `users', there is no password column though. The process seems to be really weird, what am I missing. In PostgreSQL it is a way easier.

I have a new website I'm working on that the client wants to keep a secret, but at the same time, I want to put an under construction page with some info on it. I would like to have everything except index.html require a user/password--index.html would be available to everyone. I have the following, but I'm not sure what I need to add: AuthName "Restricted Area" AuthType Basic AuthUserFile /path/to/file/.htpasswd AuthGroupFile /dev/null require valid-user There are too many files and possibly new files to say "for this set of files require a user/password". I think it has something to do with

Possible Duplicate: Secure hash and salt for PHP passwords Iv'e read a lot of posts both in stackoverflow and other websites talking about web security. Such as salting encrypting etc. And I'm kinda not getting it so a simple explanation would be really helpful. So here's what I know so far. A user logs in types his username and password. The input then goes through a process. Lets say the username and password is combined like for example: $username = (USERS USERNAME INPUT); $password = (USERS PASSWORD INPUT); $userinput = $username . $password; Then we add some salt. $salt1 = "13$13aVc!kd";