News for hackers. Stuff that matters.
Re:The Single Sign On by HeyLaughingBoy on Tuesday March 09, 2010 @02:30PM (#1179161)
OK, I'm not a web developer: I do embedded systems and hardware interfacing, so go easy on me :-)

Assuming that the hospital network was secure, then why couldn't the system, when receiving a request from that single IP, request a cookie? If the cookie doesn't exist, then that user has never logged in and is then given an identifying, non expiring cookie and from then on is allowed access and is identified? Knowing the hospital's external IP would serve as authentication.

I know just enough about web apps to be dangerous, so someone please tell me what's wrong with this idea?

Re:The Single Sign On by cookiecaper on Tuesday March 09, 2010 @03:46PM (#1179318)
That's not a problem if you know the end game, which is that only one person in the hospital will ever know about it, but if you assume more than one person in the hospital will need access, you need to provide user-level permissions to prevent patient records from falling into the wrong hands; if you just give everyone in the hospital the exact same level of access, you're exposing a lot of things to a lot of people that shouldn't know about them.
Re:The Single Sign On by Karzyn on Tuesday March 09, 2010 @02:36PM (#1179174)
I believe that the system you described would allow all users on the hospital system to log in since the system can't check who exactly is requesting the cookie. Plus, once the cookie is distributed it is only associated with the current login attempt so the system cannot know exactly which user it is.
Re:The Single Sign On by dkarl on Tuesday March 09, 2010 @06:44PM (#1179721)
Knowing the hospital's external IP would serve as authentication.

Unless the hospital provides wifi for guests and visitors.