IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Bah. Risk is the issue.
...and there are more risks than simply "proceeding as normal". One is that they would (in parallel) gain access to the new-password mailbox through sniffing, cracking or other means. Another is that they mount a DOS on my mailbox through the "new password" feature. For some mail systems, these would go hand-in-hand. Secure systems require examining all the risks, not just the original risk for which your technology was designed.
New So what's YOUR suggestion?
Regards,

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
New Unfortunately for you #1 ;)
But looking at #2, it should be possible to secure the plaintext pword DB on a limited-services box. If the server also does FTP, SSH, what-have-you, it becomes less desirable.
New WTF?
How is #2 any more secure than #3?
Regards,

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
New Sorry. You're right. I didn't read carefully.
I glossed over the email part.
New So how does that change your answer?
And I'm mainly interested to see if you have any suggestions for automated functionality.

But if we were to do #1, there's still the issue of me authenticating requests for password changes (if I'm doing the changing) or email snooping if I'm resetting and sending a new one.

There's also option #4 at the end of the thread.
Regards,

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
Expand Edited by admin Nov. 30, 2004, 04:48:36 PM EST
New Same risk than we have now during login.
And with CRCs suggestion that there be a limit on tries/hour, a DOS on your mailbox is NOT an issue.


Imric's Tips for Living
  • Paranoia Is a Survival Trait
  • Pessimists are never disappointed - but sometimes, if they are very lucky, they can be pleasantly surprised...
  • Even though everyone is out to get you, it doesn't matter unless you let them win.


Nothing is as simple as it seems in the beginning,
As hopeless as it seems in the middle,
Or as finished as it seems in the end.
 
 
New Same outcome, different risk--the attack surface has doubled
New Not mine.
"The other" Scott's: [link|/forums/render/content/show?contentid=185579|Post #185579].


   [link|mailto:MyUserId@MyISP.CountryCode|Christian R. Conrad]
(I live in Finland, and my e-mail in-box is at the Saunalahti company.)
Your lies are of Microsoftian Scale and boring to boot. Your 'depression' may be the closest you ever come to recognizing truth: you have no 'inferiority complex', you are inferior - and something inside you recognizes this. - [link|http://z.iwethey.org/forums/render/content/show?contentid=71575|Ashton Brown]
New Can we please weight the risks
against benefits and against the importance of the information being protected? I have hard time imagining someone using mailbox spoofing just to get access to my IWETHEY identity. DOSes can be easily prevented by limiting the number of resets per day.
--

This guy's ahead of his time! He's using quantum programming methods: in universes where invalid data is passed to this function, it does not return. Thus you are ensured that you will only have valid data after calling it. Optimally you'd destroy the universe on failure, but computers haven't quite advanced to that level yet.

-- [link|http://thedailywtf.com/archive/2004/10/26/2920.aspx|The] Daily WTF

     zIWT meta: Which is better: - (admin) - (66)
         3) -NT - (mmoffitt)
         1) - (jb4) - (3)
             Not for long, at least... -NT - (admin) - (2)
                 Is that a threat?!? -NT - (jb4) - (1)
                     You should know by now... - (admin)
         3, with verification - (Arkadiy) - (29)
             Seconded. -NT - (Yendor)
             NO - (FuManChu) - (27)
                 Er, buh? - (admin) - (3)
                     That's enough of a detriment not to warrant the risk IMO -NT - (FuManChu) - (2)
                         ? -NT - (admin) - (1)
                             ?? -NT - (drewk)
                 Yeah - (Yendor) - (11)
                     How is that insecure? - (FuManChu) - (2)
                         You're unclear on this. - (admin) - (1)
                             See below. -NT - (FuManChu)
                     You only need one field labeled "Hint" - (tuberculosis) - (7)
                         Sure... - (Yendor) - (6)
                             Bah. - (admin)
                             Not quite - (FuManChu) - (4)
                                 And my point is... - (Yendor) - (3)
                                     I have a standard formula I use for passwords. - (folkert) - (2)
                                         I also have a standard formula - (daemon) - (1)
                                             Ding, Ding, Ding. - (folkert)
                 It's only insecure if the user is allowed to proceed - (imric) - (10)
                     Bah. Risk is the issue. - (FuManChu) - (9)
                         So what's YOUR suggestion? -NT - (admin) - (4)
                             Unfortunately for you #1 ;) - (FuManChu) - (3)
                                 WTF? - (admin) - (2)
                                     Sorry. You're right. I didn't read carefully. - (FuManChu) - (1)
                                         So how does that change your answer? - (admin)
                         Same risk than we have now during login. - (imric) - (2)
                             Same outcome, different risk--the attack surface has doubled -NT - (FuManChu)
                             Not mine. - (CRConrad)
                         Can we please weight the risks - (Arkadiy)
         3) with some safeguards? - (Another Scott)
         4) WikiWay: everything wide open ... muuuaaaahahahahahaha -NT - (drewk) - (1)
             Shaddap wid' yer shaddin' ap... -NT - (admin)
         3 with a "what is your dog's name?" thingie -NT - (Silverlock)
         I'll join Ark, Scott(2), Don(Silverback), and YendorMike: 3+ - (CRConrad) - (2)
             <raises hand> on that last bit. :-) -NT - (Another Scott)
             Aye - 3) with - (imric)
         Another few options: - (admin) - (9)
             I'd rather not vote on solutions until we discuss risks - (FuManChu) - (8)
                 Re: I'd rather not vote on solutions until we discuss risks - (admin) - (7)
                     Okay, start with costs of current proposals - (FuManChu) - (3)
                         Missed the point. :-) - (admin) - (2)
                             Understood, but you're use case #1 - (FuManChu) - (1)
                                 I can do private keys... - (folkert)
                     What do you want the software to do? - (Another Scott) - (2)
                         Nope, wrong - (drewk) - (1)
                             Yes, a *good* challenge question would be needed. - (Another Scott)
         how about 4, the way we do it now - (daemon) - (3)
             Which is? - (Another Scott)
             And what would that be? - (admin) - (1)
                 the way it works now - (daemon)
         How about 5... - (jb4)
         16) Storing them encrypted with a "reset my password" featur - (folkert)
         A variation on 2) - (altmann)
         3), with a question 1st. -NT - (broomberg)
         3 with a proviso - (ChrisR) - (1)
             I like that! -NT - (Arkadiy)
         3. Puts the onus of keeping valid email address on user. -NT - (a6l6e6x)
         3 -NT - (pwhysall)
         6. - (static)
         "zIWT meta: Which is better:" Voting/Ratification (new thread) - (folkert)

The fourth-worst poetry in the known Universe.
123 ms