Slashdot Mirror


Security and School - How Should One Speak Up?

AJ asks: "Well, in the midst of writing 1 of my 3 papers tonight, I realized how insecure my school's network is. It all started because I was upset about them changing from using my SSN to a proprietary number scheme for identifying students. I didn't think that was a bad thing, but I was wondering if they really were securing things. So, I needed a password to access a school resource from the internet. After a little of dabbling around, I found the place where I needed to enter my propriety school ID and password. As it turns out, the login form uses HTTP instead of HTTPS! Also, my school runs a wide-open wireless network that I always had considered a convenience, but now I am changing my passwords over that network! Oh, and that proprietary ID along with a password, lead right to a student summary page where my DOB, age, address and SSN are located. So Slashdot, what is a concerned student to do?" "I have made suggestions before with little results. Should I send an e-mail with an ultimatum. What should my after-ultimatum actions be. I was thinking that I could simply start to sniff passwords (18,000 students and quite a few use wireless) and then place them on my webpage at school. I wouldn't be so concerned, but this wireless problem, combined with a poor web design, has me freaked out. Has anyone dealt with this before?"

46 of 137 comments (clear)

  1. Job opportunity? by eviljolly · · Score: 5, Interesting

    Maybe you should take a different approach to this situation. You say that the school has security problems, and you seem to be knowledgeable in the matter, so why not explain the problem and ask them if they would be willing to pay you to fix it? If all else they might nag their developers to work a little harder after hearing about it. :)

    1. Re:Job opportunity? by c · · Score: 4, Insightful

      so why not explain the problem and ask them if they would be willing to pay you to fix it?

      Because a lot of institutions will take the offer and twist it so it looks like a blackmail attempt, then involve law enforcement. I've seen way too many headlines reading something like "well meaning security person gets ass-fucked because they offered to help intitution fix security problems in return for money".

      The last thing you want to do is make it look like you're after money.

      c.

      --
      Log in or piss off.
    2. Re:Job opportunity? by torpor · · Score: 5, Informative

      well meaning security person gets ass-fucked because they offered to help intitution fix security problems in return for money"

      Too often the 'well meaning' part of these stories is hype. More often than not, it was a selfish, arrogant little brat-kid type who was trying to 'rule supreme over the stooopid school admins' and got upset when nobody listened to their tantrum and rants.

      Some guidelines for the current situation:

      - Put everything in writing, proof-read it first, then again, and spell check. Produce a professional report, not a whiny rant about why things suck.

      - Send a copy of this report to your schools administrators, registered mail. Hand-deliver a copy to the school administrator, if you can, but always, always, always put everything in writing first. Always. ALWAYS.

      - Be thorough and complete, and make sure you explain why you are being so thorough.

      - Provide examples WHEN ASKED and not before-hand. If you attach a page full of passwords you've sniffed out of the ether, this gives you a definite disadvantage if they decide to put your head on a pike. Remember, as a student, you are just one of many in the eyes of the administrator. It may well be that the problems they try to solve involve decapitating you.

      - Be courteous about this problem. It is not one single persons problem, but is in fact a group problem. Singling out one person for all the problems and mistakes of the group will do nothing but serve to make you enemies, so don't do it.

      - Follow up. If there is a change as a result of your investigation, follow up and ensure it is fixed. Work as closely with the people who are responsible for this problem as you can...

      Always, always, always try to remember, that a whiny rant about things sucking is not going to work as well as a detailed, professional, spell-checked report. If your report about the network problems doesn't look like homework, and doesn't shoot for an "A", then its going to get you into more trouble than you expect ...

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
  2. Bad idea! by 42forty-two42 · · Score: 4, Interesting
    "I have made suggestions before with little results. Should I send an e-mail with an ultimatum. What should my after-ultimatum actions be. I was thinking that I could simply start to sniff passwords (18,000 students and quite a few use wireless) and then place them on my webpage at school."
    If you're going to blackmail your school (and threaten to break various computer crimes laws), don't post about it on a high-traffic site beforehand! Better would be to talk directly to the network admin and offer to show them a live password-capture session.
    1. Re:Bad idea! by yotaku · · Score: 4, Informative

      I'm not so sure about this. Although I guess now that you've posted here you had better speak up. But if it was me, I'd have just kept my mouth closed. I know someone who reported a security flaw in my highschool's network and was promptly banned from using any school computers except under supervision and suspended from school for a week.

    2. Re:Bad idea! by 42forty-two42 · · Score: 4, Funny
      Yeah...there are some people on Slashdot, but this guy is one of the dumbest I've seen yet.
      You're new here, aren't you?
  3. UM... by ewhenn · · Score: 4, Insightful

    I was thinking that I could simply start to sniff passwords (18,000 students and quite a few use wireless) and then place them on my webpage at school. I wouldn't be so concerned

    If this page really allow you to view all of the above info (SSN, etc.) AND you are upset it would violate your privacy, why are you willing to post a bunch of other peoples passwords online?? Wouldn't taht violate THEIR privacy. I mean if someone found a problem with my banks online checking that would let people exploit and get into my account, I would not appreciate someone posting my account number an pin online. In fact I would sue the poster of htat information if I could. Be careful where you tread.

    1. Re:UM... by Grab · · Score: 3, Insightful

      Dead right.

      By all means, sniff the passwords. But then put them in a document and circulate it to your department supervisors. Make sure the document says *exactly* what you did (every step of the process). It would be good if every step was within the IT policy you subscribed to (then they can't lynch you for that), although as a whistle-blower this may not be necessary. And NEVER use those passwords, otherwise you could be done for hacking into someone else's account.

      Don't even think about asking for money - as someone else said, this makes you look like a blackmailer. Initially you have to act simply as someone bringing in information. What they choose to do with the info is their decision - most likely someone in the IT department *does* have the skills to fix the problem, it's just that they got some incompetent trainee to do it instead. If it turns out that the IT department need your skills then you can negotiate a contract or you can do it for free, but NEVER state that to start with.

      Give out ONLY hard-copies - that way a Word document can't accidentally get put on the web or something dumb like that. This limits circulation - it's more effort to photocopy/scan than to forward an email, so there's less chance of the passwords going where they shouldn't.

      Finally, make sure a hard-copy goes to the school paper, with instructions to hold onto it for 2 weeks (or some arbitrary length of time), and have a good talk with the people running the paper before you tell the school authorities. Make sure when you raise the issue with the school authorities that you tell them you've given the info to the school paper, and tell them the time limit. That way, they know they need to fix things within 2 weeks before things go public. It also covers your ass by ensuring they can't lynch you as a scapegoat, bcos the paper will crucify them.

      Basically, examine every step you take and see how it could be used against you. Getting a couple of your friends to check through what you're doing would also be useful (and having a friend watching at crucial stages like sniffing the passwords gives you the extra backup of a witness).

      Grab.

    2. Re:UM... by Spoing · · Score: 3, Insightful
      1. By all means, sniff the passwords.

      Do *NOT* follow that advice.

      Follow this advice.

      If I have to say why, you're already treading on thin ice.

      When I've run system scans and dumps on systems I do not manage, I've asked first and shown the admins what I do exactly -- and that's in my professional capacity.

      As a student, make no doubts that you will not be treated well if they even think you are able to do this. The admins should get it, though others will not understand -- though if the admins did know WTF they were doing, they'd use HTTPS in the first place...right?

      Instead, I'd point out that you are concerned since HTTP is an unsecure method and that others are likely to abuse your account and you want to know if the school is willing to take responsibility when that happens.

      Scare them into action but do so from the point of view of someone who would not even look themselves.

      In the meantime, use https:// in the URL yourself -- it will probably work -- and suggest friends do the same if it does.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    3. Re:UM... by Glonoinha · · Score: 3, Insightful

      This sounds a lot like that college kid that decided to 'test' airport security a few months ago by sneaking a knife onto a commercial flight. Made it past security, got onto the plane, then announced his amazing feat of stealth and cunning to the crew. Ha Ha your security still sucks - I tested it and I am better than you - hey wait, it was only a test - hey who are these stormtrooper guys - ouch.

      Oddly neither the airport nor the government found his 'test' very enlighting. No, in fact I think he was facing several years in Federal Pound-Me-In-The-Ass Prison.

      Original poster : you are approaching this like a child in an adult world. It is obvious that you desire peer level attention and recognition for your 'accomplishments'. Trust me, as someone that was 'recognized' and 'acknowledged' by the university administration for 'hacking' his college computers (possibly before you were even born) ... recognition is highly overrated. That you even suggested collecting the list of passwords and placing them on a webpage at school shows incredible immaturity. Not because you said it, but because doing so is even a remotely viable consideration in your mind.

      You want to blow the whistle, then blow the whistle. If you see a serious breach of security and you feel the need to get it fixed, go to https://tips.fbi.gov and fill out that form, hit submit. I pretty much 100% guarantee that they will take you serious. You can call them at 202-324-3000 if you want.

      Understand, however, that once you invite the government into any aspect of your life or business it is impossible to put that genie back in the bottle. This goes with any cute little pranks you enumerated like sniffing passwords or listing them on a web page at school.

      There is a fine line between helper and terrorist in today's environment and you really don't want to screw away your lifetime potential because you were being 'gifted and talented' in college. Not only do you not want to cross the line, you don't even want to be under evaulation as to which side of the line you are at - all it takes is one bureaucrat to misinterpret anything you have said and you are royally fscked.

      If you are here because you are genuinely concerned about massive lapses in the security as implemented at your university then consider whether or not you are ready to be a martyr for that security - because once you blow the whistle you can pretty much kiss goodbye any chances at graduation from that college. But the needs of the many outweigh the needs of the few and we are ok with sacrificing you as a pawn in the name of the overall good.

      If you are here to impress us with your 1337 haxor skillz - what you did wasn't 1337, it was merely a rite of passage for every systems guy worth his salt. About like programming a bubble sort in visual basic - everybody is proud the first time they do it, but it really isn't that big a deal.

      You want to impress us, do something none of has done yet :
      Find Osama bin Laden, hell I think there is still a $25M reward for the information leading to his capture.
      Figure out a way to actually get the administration to fix their security. Do that and you will be our hero.
      Find a way to bring back the tech sector jobs that are being outsourced overseas. Do that and you will be our hero and we will rename Linux in your honor.

      --
      Glonoinha the MebiByte Slayer
  4. Show the problem to your school leaders... by joelparker · · Score: 4, Informative
    First, contact your school technical staff;
    they are the ones to fix this problem.

    Second, if the technical staff does not fix it,
    contact your school's Deans for intervention.

    Third, if the Deans do not get the problem solved,
    contact your school paper and ask for help.

    This all shows that you're a team player,
    in case you need to escalate it later.

    1. Re:Show the problem to your school leaders... by mar1boro · · Score: 5, Interesting

      Call me paranoid. In a perfect world this would be the ideal situation.
      If you are determined to get this fixed ( as you should be ), and you are
      on friendly terms with both your system admins and your school's administration
      then take the straight forward approach suggested by joelparker.

      If they do not know you, I would attempt to be a little more anonymous.
      If you point out laxaties in their security, you will be the first person
      they think of when there is a problem. The security admin will probably
      also get his ass chewed by his boss. The admin will remember you.

      If you are still determined, do one of two things;
      1. Compose anonymous snail mails. One to the school's admin, and
      if this is a state school - one to the state's security admin at the
      department of education.
      2. If you have money, or can find an activist lawyer willing to do this
      pro-bono - retain council and enter into a priveledged communication.
      Have the lawyer communicate with the admins.

      Just remember - no good deed ever goes unpunished.

      --
      -- "It was as if the paint factories had decided to deal direct with the art galleries." - Thursday Next
  5. No no no by FattMattP · · Score: 4, Insightful
    I was thinking that I could simply start to sniff passwords (18,000 students and quite a few use wireless) and then place them on my webpage at school.
    So you're going to point out how insecure their network is by placing 18,000 students accounts in more danger than they're already in? You'll end up in jail for "hacking" if you do that. Seriously.

    What you should do instead is write a letter explaining the situation in terms that a layman can understand. Outline why you believe the current setup is a problem and the risks associated with it. Identity theft is becoming more of a problem these days so maybe they'll understand where you're coming from. Then, and here's the important part, present a solution for them.

    Whatever you do, DO NOT sniff the network and post the results. Don't even show them privatly to the people in charge. Let them handle their own security investigation. All you need to do is point out the problem and suggest a resolution.

    --
    Prevent email address forgery. Publish SPF records for y
    1. Re:No no no by Biochrome · · Score: 5, Informative

      You'll end up in jail for "hacking" if you do that. Seriously. I meerly nmaped our server, and I spent a night in jail, and lost all computer priveleges forever at school. Do NOT even act like you may be comprimising network security... you'll end up in a boatload of trouble.

    2. Re:No no no by Frisky070802 · · Score: 2, Informative

      I'm with you there. Just think about what happened to Randal Schwartz at Intel a few years ago!

      --
      Mencken had it right. So glad that's old news.
  6. Damned if you, damned if you don't by G4from128k · · Score: 3, Insightful

    IANAL, but I suspect that if you intentionally demonstrate the insecurity of the system, you will be sent to jail. Ask a lawyer, but I suspect that their advice wil be to not do anything that involves you breaking into the system.

    On the otherhand, until somebody at the school gets their identity stolen AND they can prove the school was at fault, nothing will change.

    At most, I would document the problem WITHOUT breaking any laws (again IANAL). Even documenting the problem that might get you in hot water for the terrorist crime of "hacking."

    I feel for you. Be careful.

    --
    Two wrongs don't make a right, but three lefts do.
  7. Inspiration by MegaT · · Score: 3, Interesting

    So Slashdot, what is a concerned student to do?
    this?

  8. Sniffing's a bad idea by the_truk_stop · · Score: 3, Insightful

    While sniffing passwords sounds like a great way to get students' awareness up, that's generally an extremely bad idea. While the administration sounds like it's being incompetent, you posting sensitive information online will quickly get you slapped with legal issues.

  9. No ultimatums... by isaac · · Score: 4, Informative
    Do not make an ultimatum. You WILL be subject to disciplinary procedures, and probably prosecuted. If speaking to the campus technology people responsible (and I mean speaking to the people who are *really* responsible - the managers, not the helpdesk) for these systems and networks about your concerns produces only indifference, you should drop the F-bomb - FERPA, the Family Educational Rights and Privacy Act. Under FERPA, your school may be both liable to you (and theoretically face loss of federal funds) for unauthorized disclosure of your educational records and other personally-identifiable information like SSN. (Directory information, such as your name, and the fact that you're a student, is not automatically protected from discloseure by default, but you may request that such info not be disclosed to third parties.)

    I guarantee the IT managers will have heard of FERPA, and they should snap to attention when you remind them of their responsibilities under the act.

    Consult an attorney licensed to practice in your jurisdiction for more information on your rights. I also recommend judicious use of Google.

    -Isaac

    --
    I am not a lawyer, and this is not legal advice. For Entertainment Purposes Only.
    1. Re:No ultimatums... by GigsVT · · Score: 2, Interesting

      Yeah, but there doesn't seem to be a clear cut line. From what he's said, the data is pretty much secure. As secure as any normal data was 15 years ago.

      Sure, it could (and probably should) be more secure, but does FERPA lay out detailed standards for encryption and data security practices? I personally don't know, but I seriously doubt it.

      (On the other hand, I see no use in putting that data on the web, of course he knows his own SSN and personal info.)

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    2. Re:No ultimatums... by Anonymous Coward · · Score: 3, Insightful

      Remember also that you catch more flies with honey than with vinegar, and even if you drop the "F" bomb, a pissed-off vice chancellor or IT manager can stonewall like you can't even comprehend while appearing to any outsider to be dealing with an unreasonable student as responsibly as possible

    3. Re:No ultimatums... by bcrowell · · Score: 2, Insightful
      Under FERPA, your school may be both liable to you (and theoretically face loss of federal funds) for unauthorized disclosure of your educational records and other personally-identifiable information like SSN.
      IANAL, but I believe there are some big exceptions written into the law. Your information can be given to anybody who has a legitimate educational reason to see it. I also don't think the law spells out any particular level of security that's required. The only kind of stuff that really gets you in trouble as a teacher or administrator is somthing silly like posting people's grades on the door of your office at the end of the semester.

      The OP just needs to get a better grip on reality. His SSN is not a well kept secret. Anybody who really wants to find out his SSN can easily do it. I also think he's confused about the "proprietary" student ID number as opposed to an SSN. Using an SSN for anything but social security is both a security risk and an invasion of your privacy. His school is doing the right thing by switching away from SSNs.

      The basic solution is that he should not use a valuable password on this particular account. Problem solved.

  10. At Northwestern University... by the_truk_stop · · Score: 3, Interesting
    ...the page where you change your password has a Javascript app that will check if your password meets the Northwestern University IT guidelines.

    If it doesn't, a pretty window pops up, displaying your password along with an explanation of the error. Wonderful. A variation of my second most sensitive password suddenly popped up when I missed the shift key while typing in a symbol. So far all my complaint has gotten from IT is "We'll forward this one on to so-and-so."

    Students in-the-know are generally ignored. I wouldn't bet heavily that your school will change its policies anytime soon. It probably took a boatload of work to make the switch in the first place, so more changes will probably take a lot of prodding.

  11. obvious by sporty · · Score: 2, Informative
    1. talk to parents. explain to them thuroughly what the situation is.


    2. get a lawyer. you have a right to use their networks, not admin it. you can point things out, and use the system as intended, but that's as far as it goes. i.e. http vs https. changing other's passwords and what not is something for your parents and a lawyer to discuss with the school.

    --

    -
    ping -f 255.255.255.255 # if only

    1. Re:obvious by littlerubberfeet · · Score: 2, Informative

      I agree. Do ALL communication through that lawyer. That alone will probably scare them into making changes.

      DO NOT give up the protection of a lawyer under any circumstance, because they will screw you over. If changes aren't made, have your lawyer send a cease and desist for violating FERPA, the Family Educational Rights and Privacy Act.

      Lawyers are expensive. I bet you could find one to take this on pro-bono. Ask around, email the ACLU and EFF.

      --
      Sig (appended to the end of comments you post, 120 chars)
  12. Suggestion by theantix · · Score: 3, Informative

    Do *not* sniff passwords or publish them, unless you want to face some nasty consequences. What you should to is draw up a list of the tools required to sniff the passwords and give them a recipe as to how someone could crack their security.

    From what you've said there... You should say something along the lines of "A person could sit in the school parking lot with a laptop and a wireless networking card, and run the program 'Ethereal' to watch the network traffic. This person could literally watch the login IDs and passwords, and use that information to get your SSN and other vital and private information."

    Pass that along to IT, your school administrators... if that doesn't get them hopping try passing the story on to your local community newspaper. That would be much safer than risking the legal reprecussions of cracking passwords yourself.

    --
    501 Not Implemented
  13. Honestly? No techies. by JabberWokky · · Score: 5, Informative
    Do not go to the IT department. They have screwed up, and will move to cover their asses in the easiest way; making you a scapegoat and likely sending you ass to jail.

    Go to a Dean, the highest level one you can get a good ten minute discussion. Do not discuss this with anybody else. Tell him that you have not discussed this with anybody else, that you have not exploited this vulnerability in any way, and you are coming to him directly as you realize that publically announcing such a discovery can lead to serious consequences.

    In the corporate world, this is known as an "executive sponsor", somebody with the political clout to shield you when the people who screwed up try to discredit you. It is vital that you have a sponsor, since a student has nearly zero political standing. Lay it all on the line and look the Dean directly in the eye and tell him or her that you are concerned about this issue and also about the reprocussions that whistleblowing this issue may have.

    If the Dean is not connected to the technical issues, they won't have any reason to cover their asses and will stand in your corner in the resulting (and there will be one) shitstorm.

    --
    Evan

    --
    "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
  14. MOD PARENT DOWN by Fortunato_NC · · Score: 4, Interesting

    Sarbanes-Oxley has nothing to do with your college's wireless network, or private data, or any of that. It's about corporate governance and reporting requirements for large public corporations. Mods, YHBT. YHL. (again!) HAND!

    --
    Blogging Weight Loss, Distance Education, and more at verlin.com
  15. Re:Legal repercussions for the school by alienw · · Score: 4, Informative

    Actually, it's called FERPA. Sarbanes-Oxley has nothing to do with privacy or colleges.

  16. It depends on who you know. by consolidatedbord · · Score: 4, Interesting

    If you go to the principle, you will probably get suspended/expelled for "hacking" the network. I went to 2 highschools. At Highschool A, if you had anything to do with anything that was not a part of the school's acceptable use policy, even if it was non-malicious and for the better of the school, you were almost guaranteed expulsion. (If they caught you that is. ;-) ) At Highschool B, there was a well established tech community that the assistant principle was a close part of. The on-site LAN admin s were young, former students of the school, so were pretty open to listening to what anyone had to say about "insecurities" on the LAN. I became a part of their student tech program, which offered fairly simple classes in networking, perl, html, and operating system theory. I advanced in the classes, and ended up teaching one of them as a student. Quickly, one of the LAN admins and I become buddies, and a trust was formed with me, him, and the assistant principle. As long as no harm was done when finding some kind of security vulnerability, then no suspension/expulsion was needed. I do recall however, having a history teacher at Highschool A who would periodically pull me and a fellow tech out of class periodically to fix computers. A trust was formed between us, and him. The best advice for reporting this, would be to find a teacher who you are closest to, and explain to them the issues involved. Inform him/her that you aren't trying to harm anyone, you only made a simple ovservasion and would like to report it. A trusting teacher will then put in a good word for you, the student, and you may even get some extra credit.

    --
    while true ; do echo this is my sig; done
  17. Many players by linuxwrangler · · Score: 3, Informative

    First consider your goal. I presume it is to get them to fix the problem rather than to extort money, humiliate them, etc.

    Given that assumption remember that there are many players. There are the software writers and network admins. They may be afraid of being made to look bad in front of their superiors. They may know the problems and be working on them. They may simply be doing all they can with the resources that have been given them.

    Work your way up from there. IT Department heads may try to claim it isn't a problem (prevent embarassment), indicate the need for more resources or may be in the dark because their people screwed up and hid the problem.

    The legal department and higher administration will be worried about liability and bad press. As such, any "demonstration" you put on can be used against you. Suddenly you will be the bad guy - the evil cracker. They may even try to go after you legally to cover their asses.

    Others have mentioned S-O legislation. There may be a compliance officer on campus who you can contact.

    So what to do?

    I would write a detailed letter describing the problem in layman's terms. Profess ignorance to allow people to save face (phrases such as "perhaps I am unaware of fixes that are already in the works", and "I know running a student network on a tight budget is difficult...") and express your desire that this matter be handled quickly and without the need to involve outside parties but insist that it must be handled.

    The "ignorance" method also allows you to send the letter to a wide recipient list without looking like you are trying to skewer any particular person or department: "I apologize for the wide distribution but I'm not sure who is in charge of such a matter as it involves S-O compliance, student privacy, IT etc..."

    You may want to offer recommendations (perhaps this system should be taken offline to protect the sensitive data until the security problems are repaired) and offer your assistance. If you offer to arrange a demo and they accept, request that they set up a dummy account. This helps isolate you from liability and demonstrates your concern for privacy.

    Other avenues if the "good-guy" method fails: many universities have a student ombudsman, there may be state or federal S-O compliance resources and finally, there is the press.

    --

    ~~~~~~~
    "You are not remembered for doing what is expected of you." - Atul Chitnis
  18. At my secondary school.. by Anonymous Coward · · Score: 3, Interesting

    At my sec school I got in trouble three times. Once because I used megaproxy.com to access Hotmail to send some work home (intrestingly enough, megaproxy.com was stuck on a post-it on the side of the server (yes, the server was just on a desk in a little closet!) - the council, not the school, have authority over what's blocked, so my guess is the teachers used that site to access things which were blocked too....). I got a little ticking off for that. The teachers knew it was silly and had had lots of complaints from students, but done nothing about it.

    The second time I was logged on on somebody else's account and I just did a copy/paste on the common drive. That didn't actually waste much space or slow down performance at all, but it was worth a letter home and a ticking off. Yes, it was stupid using somebody else's account.

    The third time I was pointing out vulnerabilities in the security software they were using (rather, it was a program running over windows and one of the features was that it prevented you from typing "C:\" in a file dialog box. A friend discovered that if you put c:\ in the clipboard and hold paste in the dialog box then eventually the software will be too slow, windows will win and the dialog will open. He screenshotted it and put it on the common drive for people to see. I opened it and put a ring round the "c:\" showing in the dialog box. Of course, my name came up as "last edited" (I never understood why they didn't check created by, but said person had friends right at the top...hmmm.....CORRUPTION..).

    That got a letter home and lots of chats with the Admin and Head of IT (who also happened to be my maths teacher, and knew a) I was brilliant and b) I wasn't harmful) - but still, because of politics from above, she had to take action.

    The funny thing is that there were people in the year below me regularly abusing holes but who didn't get caught because they weren't trying to inform the school. Oh the irony.

    It sucks. The suits don't understand the world of computing - just right, wrong, PR and . They don't understand that sometimes you have to be "cruel to be kind", to nick a lyric.

    The hardest part is that if you do NOT show them the holes they will ignore you, but if you DO, you get letters, action, records, jail time.

    Good luck.

    1. Re:At my secondary school.. by 0BoDy · · Score: 2, Interesting

      It all goes back to this: anytime you make something illegal, then only outlaws can do it, form compiling programs to owning a gun the patriot act and american policy seem to be making being a white hat illegal. They welcome folly by olny allowing black hats who are really dangerous to continue their activities (for lack of a better word) Maybe we need to start a slashdot letter writing campaign???

      --
      Can I be a Luddite too?
  19. SSN?! by psyconaut · · Score: 4, Insightful

    " I was upset about them changing from using my SSN to a proprietary number scheme for identifying students..."

    Let me see if I understand: you're upset about not being told to use a piece of information that's the root of identity theft issues? Heck, I'd be *glad* the school was moving away from having my SSN plastered all over the place!

    -psy

  20. Re:Legal repercussions for the school by JackAsh · · Score: 3, Informative

    Some of my respondents here are absolutely right - it's HIPAA I'm talking about, not S-O. What can I say, long day at the office, been working so much on compliance for both they're freaking interchangeable in my mind by now, etc. etc. Still no excuse.

    First, IANAL (as evidenced by my previous stupid message naming the wrong act). In any event, my understanding is that although HIPAA was originally enacted/intended as a Health-Care related act, it's effects have been interpreted to apply outside of Health Care and to any industry that stores people's private, personal data. One of the big flags the act applies is storing social security numbers.

    Rule of thumb is that if you see something private stored or transmitted somewhere it needs to be seriously secured. Seriously secured is roughly defined as encryption for every stage of the data lifecycle, from storage to transmission; as well as access control measures and all that jazz.

    So anyway, a whole bunch of industries are running around with their panties in a knot because of these new privacy regs. Then you have happy California's 1386 stuff which I think was meant for online shopping but ended up saying something like that if someone hacked your entity and gained access to customer data you have to notify every single member of that customer population that resides in California or be banned from doing any kind of business in that state. I'm sure that strictly speaking the laws apply only to some very specific instances, but that hasn't stopped people from panicking just in case it could be twisted into applying to them. I'm sure that my explanations are grossly overgeneralized, but they do serve the purposes of this conversation. :)

    The point being, there's cool new regs that protect your privacy. Make sure your school is taking them into account. I wouldn't be hostile about it, but they might just need a pointer in the right directions.

    Good luck,

    -Jack Ash

  21. Platinum cards by aminorex · · Score: 2, Funny

    A few credit applications using the Dean of Students'
    home address and the names/ssns of ten or twenty
    lucky students would get some attention, I reckon!

    --
    -I like my women like I like my tea: green-
  22. bah by Maskirovka · · Score: 2, Funny
    Should I send an e-mail with an ultimatum.

    Nah.
    Just post the name of your school here and let the problem take care of itself.

  23. Above all, tact by Jmstuckman · · Score: 2, Interesting
    There are several ways to deal with this situation. The real question is how the IT staff will react to each of them.

    The most important thing to remember is that they're going to avoid losing face in front of their superiors at all costs. This reclaiming of face might involve lying or throwing you in jail. If you find a way to inform them of the problem *without* causing anyone to look bad in front of someone with influence, they'll be grateful.

    Half of business communication is learning how to tell people things without causing them to lose face in the workplace. The sooner you figure this out, the sooner you'll be successful in the business world.

  24. don't come close to threatening by Thu+Anon+Coward · · Score: 2, Interesting

    you want the school to kick your ass out because you threatened them with revealing their network secrets and not following their AUP (surely they have one?)?

    instead, find some sympathetic influential faculty (especially if they have tenure) who can make life hell for those responsible. if they refuse to do anything, just report it to your local newspaper and document _EVERYTHING_ (either immediately write notes while in their presence or tape-record what their comments are while they deny any problems). if they turn purple or get irate, either way you got 'em by the short-n-curlies.

    you shouldn't have to put up with stupid people who endanger your future life because they won't protect your data.

    hmmm, I wonder if this would make them liable for future case of identity theft? potentially big bucks!

    --



    I'm good with numbers - .45, 7.62, 9.....
  25. I've had this same situation by shfted! · · Score: 2, Interesting

    About a year ago, I noticed a fairly significant vulnerability allowing me to get the shadow passwords of any student in the CS program, as well as all faculty and staff at my university. Thankfully, I am on good terms with the CS computers administrator, and told him what I could do, and told him what to type to get it. Being plain old DES, the shadows passwords would have been trivial to crack using a dictionary approach.

    He immediately contacted the university CTS staff (they administer everything else), and it turns out they were aware of the vulnerability. I noticed that later that week the hole was closed in a hacked way, by simply disallowing use by regular users of a certain system binary.

    He also told me it was a smart decision on my part to come forward immediately with the information, because if they had found out that I knew and didn't tell them, I would have been expelled and barred from any post-secondary institution in North America for several years. I guess they keep a watch list somewhere.

    --
    He who laughs last is stuck in a time dilation bubble.
  26. I'm assuming you're in IT by Gary+Destruction · · Score: 2, Insightful

    I'm assuming that you're in IT to some capacity and not someone who just knows a good deal about networking and security. The reason I'm asking is because if you're not in IT and you approach them, they might talk down to you or attempt to discedit you. I'm sure you know what I'm talking about. The "Well what does he/she know about computers?" If you are in IT, you might want to approach them from the standpoint of an IT professional. You might say something like,"Hello. I was logging in and noticed something...." And make them aware that you are an IT professional/student so that they know you're someone that's speaking on a level playing field. And if you're a student, you could say something like,"Well in security class, I learned https and..." It's a tough situation because you don't want them to get the impression that you're snooping around and looking for something to exploit. At the same time, you don't want to come across as being intrusive or pushy. The other option is to approach them showing concern about your own privacy. The idea of an ultimatum has already been answered by previous comments.

  27. Watch your ass by +CipherDemon · · Score: 2, Interesting

    I experienced similar things with my school (except that we're a high school in florida, which means there's almost no education money. bastard politicians.). I found a multitude of insecure things in the workstation setup (including being able to edit file shares between machines from a non-admin account). So, I made a report for them and gave it to my computer teacher. The first IT person that got ahold of my report wanted me suspended and barred from all on-campus computer labs. The second one finally fixed everything that I'd mentioned and now we're running much more securely (although there are still problems that I'm NOT going to bother filing a report about as it won't do any good, I don't plan to exploit them, and I'll just get suspended). But, I haven't gotten any thanks from the IT department. Honestly, I'd rather take it to the deans first as an issue of personal privacy vs. network security. You're probably safer that way as you'll be above the IT people and won't get owned hardcore by them.

  28. Anonymity by AgentOJ · · Score: 2, Interesting

    Back in college, the same thing (more or less) happened to me. My school was using http instead of https for email, and the same password was used to access student information including DOB, SSN, etc. You also had the ability to add or drop classes with the same password. Since the school had "free" wireless access, and no form of network authentication, anyone could sit in the library and sniff passwords. I made the utterly stupid mistake of calling the "help desk," and the lout who answered accused me of hacking when I tried to explain that email wasn't secure.

    Needless to say, the computer services department eventually met with me, and offered me a tech support job. Being the starving college student, I jumped at the chance. Stupidly, I filled out the job application, and waited to hear back from them...and waited....and waited. Over the next two months, I met with the computer services department three times, each time being given some excuse as to why I hadn't started my new job.

    During this time period, I knew a number of people who worked for the computer services department who I was on good terms with. I asked one of them to check for me to see why it was taking so long to start my job, and he did some poking around for me. Eventually he found out that the job application was a front, and they used the information provided in it to do a "background check" on me to see if I had gotten in trouble for "hacking" in the past. They went so far as to call my high school and check there, and then blacklisted me as a "bogey," apparently their term for hackers.

    They never intended to give me a job. They offered me the job to keep me happy until they could do a check on me. As I had done nothing in the past to give me a "hacker record," they decided to just give me the cold shoulder. I passed up two other job offers during that time period, thinking that the higher-paying computer services job was just around the corner, as I was lead to believe. I never got the job.

    I guess the point of my story is that you can try to do the right thing, and explain the situation to your school's IT department, but you might very well end up in my situation. I'd go to an internet cafe, or send a letter, or something, but do it as anonymously as you can. Unfortunately, even though you're in college, some of the people there do not have open minds, and will scorn you for your attempt at helping.

    Funny thing is, about a year after my initial call to the IT department, one of the school newspapers ran a story detailing the problem, and praising the IT department who had "fixed this problem." The story went on to say how this "hole in the network" had been open for over a year, and hadn't been noticed until recently. I laughed out loud when I saw that, as I knew it was complete and utter bullshit.

    Mod me down if you will, but I know that at least one of the people involved in my case reads slashdot, so if this story sounded familiar, maybe you should rethink your method of dealing with those who only wanted to help.

  29. Re:Honestly? No techies. by Spoing · · Score: 3, Interesting
    1. Do not go to the IT department. They have screwed up, and will move to cover their asses in the easiest way; making you a scapegoat and likely sending you ass to jail.

    Agreed on going to the dean. If you use what I call the Columbo method -- after the dumbly and wise detective on TV -- you can also go to the IT department though this is a bit more risky but may silently solve the problem.

    The Columbo method works basically like this;

    "I'm no expert, though shouldn't there ..." (and give a base -- even misworded -- comment on what is wrong)

    Other phrases: "You know, I was wondering..." / "I find it curious that..."

    Now, don't follow through and 'catch the bad guy'...you're only talking after all -- and *you're* not the expert! These things confuse you!

    "If only someone could do something about that. Do you know anyone?"

    Change the subject and leave or if the mood is right, just smile and leave. A "Yep, I find that interesting" as you go might also get it to sink in.

    If anything, be a little funny but do not be condecending.

    Who to talk to? Pick someone who is in the IT department who does not have an ego or a nasty attitude. Be unexcited, and mention your concerns as if you're commenting on the weather.

    Note: If using https:\\ instead of http:\\ works, mention that *you* found a work around, though https should be the default -- after all -- for all those other people who haven't noticed yet. But what do you know?

    --
    A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
  30. I did something similar once... by oneiros27 · · Score: 2, Interesting

    I sent an anonymous packet of informtion to the dean through campus mail, regarding a faculty member's use of equipment purchased for a university project, and his taking that equipment for a company that he started, and giving us instead dated equipment with 'property of NASA' stickers on it. [where he worked part time, it was my understanding]. He also claimed the work of one of the students for whom he was an advisor, as the work of his company.

    Unfortunately, as there were relatively few people who had access to all of the information that I did, it was rather easy for them to track it back to me. I was called into a meeting with the dean, and the faculty member, and they threatened me with expusion. They also weren't happy with something that I posted to the group's web page (which was in fact, a violation of the university's policies regarding use of computer systems)

    I also wasn't aware that the dean had a vested interest in keeping the faculty member, as he had received a multi-million dollar grant for some of the research that he was doing.

    So, my recomendation is -- if you're going to do anything, go straight to the feds. More than likely, whomever you complain to internally knows what's going on, and wants it to continue, for some reason that you don't know about. [It might even just be a cover-your-ass approach].

    Oh -- and after graduating, years later, I needed to get a transcript for a job. It turns out the university had shipped me a diploma, but didn't have my graduation listed in their computer system. It took me over four months to get the issue resolved, and even then, as the last meeting I had with the assistant dean, he had the balls to appologize to me -- not for someone missing to update a flag in the computer system, but for them sending out an incorrect letter informing me of what classes I needed for graduation and sending me the diploma in error.

    [They only flagged me as graduated, as I had taken a number of graduate level classes, and they applied those to make up for the two one credit classes they claimed I needed, 6 years later].

    Unfortunately, I don't think that this is a direct violation of FERPA, but I know there was some new law, that I think is now in effect, that made it so they had to stop using SSNs as tracking numbers. I've been out of higher ed for almost a year now [working as a systems programmer, and speaking up about problems -- which got me fired], so I'm not as current as I used to be.

    If you really want to report this to the school, take it to the student government, or some other body that the school doesn't have direct control over.

    --
    Build it, and they will come^Hplain.
  31. From a guy in the IT Dept: by tverbeek · · Score: 2, Insightful
    Do not under any circumstances use this knowledge of vulnerabilities to actually sniff passwords, gain access to information you're not intended to have, etc. If your college's Acceptable Use policy is anything like ours, doing so will be a violation. Full stop. AU policies never include an "unless you're doing it for a noble reason" or "didn't do any harm by it" exception. And if you were to catch me with my pants down, you can be sure that I'm not going to thank you for it; I'm going to throw the book at you, to make sure that no one else gets the idea of trying something similar. It doesn't matter if I'm negligent or not; that's just the prudent IT fear-mongering to discourage genuinely malicious hacking (of the kind you're worried about).

    Instead if you know people in IT, you can try going to them with your concerns, from a "hey did you know... it worries me...." perspective. If they're good people and well managed (but just didn't stop to think about it), that should help. If you don't have a friend there, or you hear that IT are a bunch of bozos, your best bet is to bypass them and take your concerns (as "I know enough about it to suspect this could happen", not "I know how to do this") directly to one of the offices charged with handling your student data (e.g. registrar, business office, financial aid). They're the ones who ought to be most alarmed over confidentiality problems (because they've had in-services driving the point home), and it'll be their bosses in the administration who'll have the authority to put the pressure on IT to do their job.

    --
    http://alternatives.rzero.com/