Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Don't clear password fields if the password is ok
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Robert Walker  
View profile  
 More options Oct 26 2012, 10:14 am
From: Robert Walker <li...@ruby-forum.com>
Date: Fri, 26 Oct 2012 16:11:19 +0200
Local: Fri, Oct 26 2012 10:11 am
Subject: Re: Don't clear password fields if the password is ok
Dmitry Maksyoma wrote in post #1081303:

> No, I'm not using auth engine, I only use `has_secure_password'. I've
> tried
> removing that and adding `attr_accessor :password,
> :password_confirmation'
> and it didn't change a thing, so it seems to be the default Rails
> behaviour.

> My view: http://pastebin.com/s7tpwN4D

I'm not 100% sure about this, but I have a feeling that behavior exists
for security reasons. The primary concern about providing a password to
a server is limiting the amount of time the cleartext version exists.

In fact I'd be willing to wager that the hashing occurs in the RACK
middleware, which means your Rails application never sees the cleartext
password, and therefore would not have it to send back in the response.

--
Posted via http://www.ruby-forum.com/.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.