Slashdot Mirror


Aussie Uni Dumps Dual-Boot In Favor of Linux

kNIGits writes "News.com.au is reporting that the University of Wollongong have dumped their previously dual-boot installations in favour of booting Linux only. Among other reasons, staff enjoy the ease with which they can 'lock down' first year students, stopping them messing with the systems prior to learning anything about them."

127 of 344 comments (clear)

  1. Hehehehe... by Pig+Hogger · · Score: 5, Interesting
    Linux to lock down... Who'd have thought...

    I've met a tech who was working for a high-school, and 90% of his time was used in fixing Windoze computers after students messed-up with them. That changed when they installed some cards (don't remember the name of the cards) with RAM on them that effectively made the hard disks read-only, and stored in RAM whatever was written on the hard-disks.

    So, whenever a PC was screwed-up, all you did was power-cycle it once!

    1. Re:Hehehehe... by Jester998 · · Score: 5, Informative

      The cards you're thinking of are often called "Sheriff Cards".

      Apparently they have them in my old high school now. Poor kids... hacking the network was one of the more fun things about high school. :)

    2. Re:Hehehehe... by ChrisBennett · · Score: 5, Informative

      There is a software solution for Windows called DeepFreeze. It works very well. I love seeing the look on faces when they delete random .dlls or change wallpaper only to find that they magically re-appear when the system reboots.

    3. Re:Hehehehe... by pVoid · · Score: 2
      I've met a tech, who works at a university called University of Toronto. They have public internet access stations at their library. And they have dozens if not hundreds of PCs running 'windoze' that students use to do their projects. They're all running 'windoze'.

      What's your point? An improperly administered box is an improperly administered box.

    4. Re:Hehehehe... by Anonymous Coward · · Score: 3, Interesting

      A undergrad lab at my alma mater (Stony Brook) had an ingenious solution: a pile of network-booting machines that automatically mirrored the "official" disk image upon detecting changes. This way, students could come in, install some other operating system for a while (other than the default FreeBSD install), and then just reboot the machine to return it to its original state. No reliance on any special software like that Windows deepfreeze thing, or assumptions about not having physical access to machines. Very elegant.

    5. Re:Hehehehe... by MechCow · · Score: 2, Interesting
      At my highschool we used Novell computers, and they were as locked down as the poor computer studies teacher could make them. You couldn't use the floppy drive. You could only execute the 8 or so programs assigned to you. The internet was so protected that I was unable to look stuff about Homer's Odyssey (luckily I was protected from the word virgin I presume).

      Now at uni things are so much more free yet the systems so much more secure. We can use the floppy drives, have our own email addresses and websites, and even the /sbin/ is a+x (I don't know how bright this is on there part). All is well...

      Unless you go into one of the windows labs in which case you are assaulted with kazaa, icq, msn straight after logging on. You will find the harddrive to be full of crap. Also many people do 'confirm' their password after logging on thus I assume there are password files on those computers with hundreds of students passwords, all with measily encryption.

      At least until XP, or the next windows after that makes into the labs it seems windows will always be a hassle for maintainers.

      --

      --
      On Slashdot I'm a lawyer.
    6. Re:Hehehehe... by shepd · · Score: 2, Insightful

      >ya. then there's that software you can get/use for free called POLICY EDITOR

      You clearly don't have even the very slightest clue about what you are talking about.

      Do you even know the difference between a piece of software that keeps an image of the HDD clean, clear and free of crap while emulating a small write-only partition and a policy editor that (pathetically) attempts to stop users from doing things?

      The number once difference would be that deepfreeze is pretty much immune to virii. Is policy editor? No, because it doesn't work at all like deepfreeze.

      This is like comparing ghost and xcopy. Sure, I could keep a backup copy of my hard drive with xcopy, but only ghost offers the bulletproof solution.

      --
      If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
    7. Re:Hehehehe... by Arker · · Score: 2

      I installed that Centurion on nearly a hundred machines in a past job. It's not nearly as good as you're making it out to be. It's pathetically easy to defeat.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    8. Re:Hehehehe... by shepd · · Score: 2, Interesting

      >Of course, it does little to protect you from leet haxoring tools like deltree.

      Overall, deepfreeze (and other such software) tends to protect its own files from deletion (windows does too, since deepfreeze is running the deepfreeze DLL will cause windows to throw an access violation upon deleting it). Although, if you can get the machine to boot to DOS, you can bypass it. However, it isn't very difficult to stop anyone from doing that...

      --
      If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
    9. Re:Hehehehe... by Anonymous Coward · · Score: 2, Insightful
      fortunately for us, we had already hacked their novell server, and had all of our stuff in a nice hidden directory, so when it came time to Quake, we had a 5 minute setup :)


      In the process you made some underpayed lab technician's day a little longer. And students wonder why the lab machines crash when they go to do real work, (or they b1tch because the machines are locked down tight). e_e

      Folks, the computer labs at (insert your favorite college here) aren't necessarily the best-funded part of the school, despite what you might want to believe. Depending on the administration, the college might not even have a proper IT division. The people who maintain the labs may also have to maintain the faculty and classroom computers, in addition to tutoring students and teaching classes.

      Please, mentally masturbate somewhere else. No tech with a day's worth of trouble tickets needs to see how 'l33t you aren't. They've got better things to do.

    10. Re:Hehehehe... by Feztaa · · Score: 5, Informative

      Older versions of DeepFreeze were pretty funny. Set the system clock sufficiently far into the future, and it magically crashed. The first thing you do after that is delete DeepFreeze, and you have no more DeepFreeze problem ;)

    11. Re:Hehehehe... by jaavaaguru · · Score: 2

      If you had choses Linux in the first place over Windows, you'd never have known that problems like that exist ;-)

      To be fair though, Linux wasn't as useable to the average person back then as it is now. Lets just hope people starting this process from the beginning don't make these mistakes.

    12. Re:Hehehehe... by Black+Copter+Control · · Score: 5, Informative
      Either way, PE is a lot easier, as well as the numerous other packages avail., than re-OSing the campus, or installing hardware into every machine.

      Windows was originally designed around the presumption that there was really only one user on the system, and that user could/should do whatver (s)he wanted. To that was added the eventual realization that Oops! That's not always the case.

      This has resulted in the back-ending of all sorts of security hacks onto what is still, essentially, a single-user system. A side effect of this is all sorts of special cases and wierd holes in the design of Windows that results in the need for things like PE.

      Unix, on the other hand was designed as a multi-user system almost from day one. In this context, a single user system is simply the special case of N==1. Locking down a Linux system requires little more than putting passwords on GRUB and the CMOS editor, and possibly pulling the setuid bit from some questionable binaries. Once that's done, there's little that a non-root user can do beyond trashing their own account, or various DOS type stupidities (which can often be responded to by a good sysadmin).

      Beyond that, the ability to prevent first-year stupidity is only one of the reasons why Linux was chosen as the standard for first-year students. Not having to worry about being sued when the students post the source code that you gave them (under some sort of non-disclosure agreement) on the net when asking for an answer to a question is another. Multiple GUI desktops, extensibility and totally free access to the source code are some of the others.

      --
      OS Software is like love: The best way to make it grow is to give it away.
    13. Re:Hehehehe... by jez9999 · · Score: 2

      >And ghost is not a BP solution either dumbass. Ghost will "ghost" errors on the drive along with everything else.

      And why are you using a used workstation to update your ghost image from?


      Any why are YOU using a used workstation to update your xcopy image from??

    14. Re:Hehehehe... by jez9999 · · Score: 2

      Sounds like you could have built your own BBC with less effort.

    15. Re:Hehehehe... by AvitarX · · Score: 2

      I think the problem is the hords of semi geek 18 year old drop outs and haxor wanna bes.

      if you are serious into programming you are more likly to have some respect.

      Your quaking was not malicious, and probably did not cause support headaches. So how was your bypassing the system so bad?

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    16. Re:Hehehehe... by jgerman · · Score: 2

      Though it would have taught the kids a heck of a lot more about computers is their teacher was knowledgable enough to install it. I didn't find Linux until my senior year (the end of it actually), but I had some Unix experience at that point. I'm pretty confident in my coding skills, but I can only imagine how much I would have known if for the previous 6-7 years of coding and learning about computers I had had Linux to work with... it's infinitely more conducive to not only programming, but exploring computers in general.

      --
      I'm the big fish in the big pond bitch.
    17. Re:Hehehehe... by jaavaaguru · · Score: 2

      Yeah, I'd say that learning Windows (aside from administration) is really just learning an application: explorer. Learning Linux is a bit more like in learning about operating systems in general. Sure, you could stick to learning KDE, which would be really similar to learning Windows, but there is a whole wealth of knowledge waiting to be found below that.

    18. Re:Hehehehe... by jonadab · · Score: 2

      As long as they have unsupervised physical access to the system, they
      can always circumvent it. Ultimately, if there is no other way, they
      can set the BIOS-forget jumper to wipe any CMOS password, set it to
      boot from a removable drive, and then have their way with the MBR and
      the boot sector of the boot partition. In almost all cases, there's
      a much easier way that doesn't involve opening the case. DeepFreeze
      is, from what I'm told, good enough that if you have no bootable
      removable drives, set the BIOS password, and can keep them from
      opening the case you won't have much trouble -- but you are always
      taking the risk that the teacher or lab assistant will step out of
      the room for too long and some clown will set the BIOS jumper and
      have his little fun. (Having no removable drives goes a long way
      toward making this harder, but that isn't always practical.)

      The better solution is to go with thin clients. Then all they can
      do is steal the thin clients, but without getting into the server
      room, that's the limit. You hook up a new thin client, and it's as
      if nothing happened. (This assumes the thin-client server is secure
      from network-based attacks; I suggest not using a Microsoft solution
      on the server end, and don't use your thin client server for serving
      other things like mail, either; spend the $50 on ebay and get
      yourself an old system you can make into a separate mail server, if
      it comes to that.)

      Seriously: a thin-client solution takes more setup, but once you
      have it in place, your headaches are greatly reduced. The only
      downside is a Single Point Of Failure, which is another reason
      you don't use a Microsoft solution on the server end.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    19. Re:Hehehehe... by jonadab · · Score: 3, Interesting

      > Yeah, I'd say that learning Windows (aside from administration)
      > is really just learning an application: explorer.

      Um, have you ever tried to administer a Windows box? Knowing
      Explorer is what you take for granted; it's the undocumented stuff
      that you have to know to survive. You're dead in the water if you
      aren't comfortable with the registry, for example. First time any
      problem crops up, you'd best know how to work with cabinets, and
      which undocumented batch files that get created by install processes
      are run on startup and, if broken, have to be deleted in order to
      restore the system to a bootable state. (And no, I'm not talking
      about AUTOEXEC.BAT; if you thought that was what I meant, you'll
      end up formatting the drive the first time anything goes wrong, but
      not until after you pull out your hair first.)

      The difference between Windows and Linux is not one of complexity;
      Windows and Linux have roughly the same amount of complexity. The
      difference is one of documentation: Linux has some. (The other
      difference is consistency in terms of the visual appearance of UI
      widgets; almost all Windows apps use the same widget set. (That's
      a good thing.) RedHat is working on this problem, but their
      solution is incomplete at this time.)

      --
      Cut that out, or I will ship you to Norilsk in a box.
    20. Re:Hehehehe... by jgerman · · Score: 2

      The difference is that Linux has accessible complexity, plain and simple.

      --
      I'm the big fish in the big pond bitch.
    21. Re:Hehehehe... by Jeffrey+Baker · · Score: 3, Insightful

      If the program was any good in the first place, it wouldn't let you set the clock. There is no legitimate multiuser system where a normal user can diddle the clock.

    22. Re:Hehehehe... by jaavaaguru · · Score: 2


      Um, have you ever tried to administer a Windows box? Knowing
      Explorer is what you take for granted


      I said aside from administration, meaning that I was talking about using windows but not administering it.

      I do believe that administering it could be very complex.

    23. Re:Hehehehe... by SavingPrivateNawak · · Score: 2, Interesting

      I tend to agree with the previous poster: you can easily lock down any NT.

      They did that at my universities and their NT-domain was the most well built I have ever encountered... far more robust than the one we have at work...

      Anyway the only way we found to get around the policies was to open the case and boot from another OS to make our 'modifications'... So we succeeded but since ANY computer is vulnerable when you have physical access to it, you can't bash NT on that.

      I also think that playing GTA2 on a university computer is no l33t hax0ring at all, so the other poster that bragged about that really proves nothing. On any computer, if you want to get some work done, you have to have write access somewhere and the ability to run binaries... once you have that, there's no reason why you couldn't play games, they are programs after all... and you are in CS-course to make programs...
      (Well of course there are many games that need to be installed but really I can't understand that! I mean, there's no fscking DLL to share with another prog, no need for special 'machine-wide' registry settings, so why require it to be 'installed'... Quake 3 r0x0rs! :) )

      To be more specific about your post, I think it could refer to some lame special Win9x versions that were extended for multiuser and access restrictions but not to NT. I think that NT was multiuser from day-1. (With the special requirement to look like the 'lame, single user one'...)

    24. Re:Hehehehe... by Black+Copter+Control · · Score: 2
      They did that at my universities and their NT-domain was the most well built I have ever encountered... far more robust than the one we have at work...

      I'd say that that backs up the theory that it takes a god-level sysadmin with attention to detail to lock down an NT network. It's not impossible, but it's far from a normal state of being.

      --
      OS Software is like love: The best way to make it grow is to give it away.
    25. Re:Hehehehe... by kraksmoka · · Score: 2
      figures, one of the lab fsckers would bitch about quake today, still. they whined and whined, its causing instability thoughout the network!

      they were always full of shit, and would walk around and shut down our boxes as we played.

      since you're one of them, that makes you highly qualified as a moron.

      if jerks like u spent the time studying your manuals instead of hunting down gamers, you might know how to find your ass in a paper bag, let alone manage a network.

      i leave you with the greatest curse i can levy upon anyone: your own stupidity is your highest reward.

      --
      "You never want a serious crisis to go to waste." - Rahm Emanuel
    26. Re:Hehehehe... by SectoidRandom · · Score: 2

      Typical school thinking, ie spend the smallest amount possible. I'm guess you used Win9x?

      I setup a bunch of locked down libary pc's at a private school here, first they chose the cheap path of Windows98, I locked them down as best as I could, of course that's only so much, after recieving frequent calls i proposed Windows2000. Since installing and locking that down six months ago NOT ONE CALL. The best a kid could hope for would be to either crash or corrupt the install, that's why the Libarian has the Ghost image cd that autoboots and images back to square one. Apparently she hasn't needed to even use that yet!

  2. UNSW by Slurpee · · Score: 5, Interesting

    The Uni of New South Wales Computer Science and Engineering department has been running unix/linux for years, no duel boot.

    8 years ago it was Sun Solaris.

    5 Years ago they moved to Intel Solaris

    Now they have (or are) moving to Intel Linux.

    anyway, good stuff at Uni of Wollongong.

  3. The article. by Anonymous Coward · · Score: 3, Informative

    Linux taking over at uni
    Chris Jenkins
    17Dec02

    LINUX is making inroads into the nation's universities, pushing Windows, Unix and Apple operating systems off the desktops of first-year IT students.

    It is making ground in IT courses because Linux is both easy to lock-down, easy to pull apart and offers simple licensing for distribution to students.

    At the University of Wollongong, which has about 1700 computer science students, machines in first-year labs that used to boot from either Windows or Linux have been changed to Linux only.

    "We get large number of inexperienced people in first-year and we are really trying to keep down our overheads and concentrate our professional support more in the later years," said Les Ohlbach, operations manager for the university's Department of Informatics."

    "The best way to control the first-years was to put them in a Linux-only environment where you can lock it down pretty well."

    Students moved to Unix and Windows in second- and third- year, he said, with Macs used for multimedia training.

    At the University of Western Australia, which has around 1650 students in its computer science courses, Linux has totally supplanted more traditional Unix distributions, such as Sun's Solaris in the school of computer science and software engineering.

    UWA's senior lecturer in computer science and software engineering Chris McDonald said Unix was dropped from teaching around 1995, and was no longer specifically required for any research projects.

    UWA recently dropped Apple from its IT education programs in the school, for the same reason that Unix was abandoned -- expensive proprietary hardware.

    "It wasn't so much the [Unix] operating system costs, because it usually came with the machine or we could get pretty good prices as an educational institution," he said.

    Linux was easier to give to students for home use, Dr McDonald said.

    "If we were using Solaris or HP-UX or something like that, I'm sure there would be very different and costly licensing issues involved," he said.

    "We are trying to move to an environment where what we provide in the laboratories can be mirrored in the students' home."

    Mr Ohlbach said the University of Wollongong favours Linux for first-years for a similar reason.

    "We are teaching programming, so they [students] need to run all sorts of IDEs and development environments. On Linux they can quite easily do most of their code at home at fairly low cost," he said.

    Dr McDonald said in teaching open-source platforms to students it is important not to "just ram open-source issues down their throats. It's important to explain why there is a difference in philosophy, why it's reasonable to not to totally tread the path of one particular vendor, one particular monopoly."

    However, Dr McDonald said UWA's school of computer science and software engineering was part of Microsoft's academic alliance program, which allowed the free distribution of Microsoft operating systems to enrolled students.

    The school used Linux and Windows to teach operating systems.

    "It's good to show not just the similarities, but more importantly the differences."

    Linux allowed better teaching of the principles behind software development, he said.

    "We'd rather explain how things work. We do that by taking things apart and putting them back together again, rather than just showing people how to use particular GUIs that other people have designed. It's our belief that open-source software better explains those concepts," he said.

    "Personally, I think that just showing students how to use operating systems tools and networking tools, is more training than education.

    "From 2003 UWA's school of computer science and software engineering will be using Linux, in preference to Windows, for our first-year Foundations of IT unit."

    Mr Ohlbach said it was important for students to have exposure to multiple operating systems and development environments.

    "Anybody wanting to be a professional computer science person, or an IT person, generally doesn't want to be seen as just a Mac or a PC party, " he said.

    This report appears on news.com.au.

    1. Re:The article. by WaKall · · Score: 5, Interesting

      "Dr McDonald said in teaching open-source platforms to students it is important not to "just ram open-source issues down their throats. It's important to explain why there is a difference in philosophy, why it's reasonable to not to totally tread the path of one particular vendor, one particular monopoly."

      I wonder WHICH monopoly he refers to?

      I think it's important to teach skills and not languages. The platform shouldn't really matter. But what I read there is "we're gonna teach non-proprietary solutions". I don't think the OS matters for the undergrads.

      I learned programming on Solaris and later Linux, and honestly there's no real difference between them for 95% of what you do in school, since you are NOT administering the box, and the interesting tools are opensource, portable, and provided by the school - you just have to USE them. This probably holds true for BSD as well.

      I do believe that we shouldn't be teaching kids to develop in MSVC++ and MFC. I think that's god-awful - we should learn to use makefiles and know the dependencies in our code, and not waste time on things that aren't portable to our jobs, on a yet-to-be-determined platform.

    2. Re:The article. by Lumpy · · Score: 3, Interesting

      I do believe that we shouldn't be teaching kids to develop in MSVC++ and MFC.

      we shouldn't teach ANYONE to program in any of the Microsoft visual environments. it promotes sloppy coding, bloat and tons of other things that make just plain old BAD programmers.

      you want to teach windows programming? then use the free solutions out there teaching the API interfacing and other parts of fighting with a windows environment is so much more important than the drivel the MS visual dev.

      Give the studen MORE understanding and a tool they can freely take home legally. you get a better programmer.

      and as a side note. every teacher should at the end of every semester force all the student to program in an embedded environment or put tight size cap's on the compiled program.

      Anyone can make gigantic bloatware, a good programmer makes fast tight code.

      --
      Do not look at laser with remaining good eye.
  4. Another Solution - Windows Policy Editor by RaboKrabekian · · Score: 5, Informative

    I'm not fully versed in all its wonders, but the Windows Policy Editor (or whatever its called now) can completely lock down a machine. It's a vastly underutilized tool for environments where you don't want users messing with the machines. I remember getting annoyed the first time I sat down at a box which wouldn't let me even look at the start menu. Any and all Windows admins should look in to its proper use in their environment.

    --
    "Moderate drinking can help prevent amputated limbs" -- Abigail Zuger, NYTimes, 12/31/02
    1. Re:Another Solution - Windows Policy Editor by tconnors · · Score: 3, Interesting

      t's a vastly underutilized tool for environments where you don't want users messing with the machines. I remember getting annoyed the first time I sat down at a box which wouldn't let me even look at the start menu.

      In our undergrad labs at cs.usyd.edu.au, there was a low-end pentium for the sole purposes of ftping files from your floppy to your 3meg quota'd ugrad account on the nix machines. It was win3.1 (even though this was in 1998-2000), and all it _appeared_ to have was a crappy ftp client and 2 other semi-useless programs. You were given a 3 minute time-limit to use this machine. But one day, I recursively transferred the wrong files, and the ftp client was crap, and couldn't recursively remove directories, so I went to the c:\windows directory (or whatever), in the ftp client, selected command.com, and clicked the "run" button. I then was in a dos shell where I could deltree.

      Moral of the story: There is no security in removing the start button :)

    2. Re:Another Solution - Windows Policy Editor by mferrare · · Score: 4, Interesting
      But consider how much you have to piss-fart aoround with WPE to get a good config - partially because no-one uses it - and compare that with 'locking down' a linux box ie:
      • secure it - and most linuxes are reasonably secure out-the-box these days
      • set a strong root password. Give the students limited sudo access if necessary
      • Probably a little bit of hardware stuff (disable floppy booting etc)
      • Maybe setting up a restricted shell or GUI environment
      But basically, students would be pretty safe on a linux box without root access. And it's simple and well-known to set up. Compare that with Windows Policy Editor. Does anyone really use it? Maybe a few but I'm sure it's not as well documented or as well tested and probably not as robust as simply locking out root access to a linux box.
      --
      Why would anyone want to use a text editor that is not vi?
    3. Re:Another Solution - Windows Policy Editor by indiigo · · Score: 2

      we use it, and like linux, it requires a lot of compatibility testing with your apps. You can easily break something bad enough irreversibly, so it's not a toy that one uses on their users.

      follow the guides and the people (beta) before you

      --
      fslg503-985-8686503-985-8686503-985-8686503-985-86 8650 3-985-fdsg8686503-985-8686503-985-8686503-9
    4. Re:Another Solution - Windows Policy Editor by foo+fighter · · Score: 4, Informative

      Windows Policy Editor was used for the 9x/Me series.

      Starting with Windows 2000, admins have access to "Group Policy". Essentially, any user interface setting -- and most system settings -- can be controlled via this either on the local machine or remotely.

      Group Policy kicks ass. You can completely lock down a machine so that cmd.exe doesn't work no matter what and the only .exe's that do work are the ones you specify. You can let the user specify their Display preferences, but nothing else. Or everything except the Display preferences. The point is, Linux has nothing to compare with this.

      The fact is, under Windows 2000 (and XP), administrators have never had an easier time setting up, controlling, troubleshooting, and fixing a user's desktop. If Linux had anything to easier to compare to this I'd be using it (admins being essentially lazy).

      At length, I've evaluated Redhat, Suse, Caldera, Debian, FreeBSD, OpenBSD, and Mac OS X. (At length means ~40 hours on each setting up desktops and administrative consoles and testing things out.)

      I have many Redhat machines running on servers at work. I have a Yellow Dog machine running my web site and email and OpenBSD running my router at home.

      The FACT is no one has a better way to administrate and trouble-shoot end-user desktops than Microsoft right now.

      --
      obviously no deficiencies vs. no obvious deficiencies
    5. Re:Another Solution - Windows Policy Editor by Anonymous Coward · · Score: 2, Insightful

      Just because you personally don't know how to do something doesn't mean it can't be done.

      Its quite possible to lock down user's desktops in linux if your familiar with linux. It doesn't sound like you are. It also sounds like your looking for a single point-n-click program to do it with. Well that just doens't exist, but it doesn't mean you can't severely limit what a linux user can do.

      Its also trivial to ssh or vnc in and take over a session of kill the appropriate process if needed. I laugh in your general direction for even joking that its somehow easier to remotely troubleshoot desktops on windows.

      Your also comparing apples and oranges a bit since the linux and microsoft desktop are two very different beasts.

      So not its not a FACT afterall.

      Also and don't take this the wrong way. Spending 40 hrs each on some distros hardly qualifies you to proclaim MS king of all administration.

    6. Re:Another Solution - Windows Policy Editor by popeyethesailor · · Score: 2

      Agreed, but when the administrator password is not in the hands of the user, which so often is the case..

    7. Re:Another Solution - Windows Policy Editor by mystran · · Score: 5, Informative
      There also another view. In windows you have to options: either you allow people to do everything or you allow them to do nothing. The policy editor just stops working once you allow someone to run an .exe from his desktop since he can break the system (with one of the numerous exploit that for example the GUI gives you).

      In Linux (and unix in general) you can allow people to do almost anything with their own account. If they mess their homedir (and it's quite unlikely to get your personal stuff to the point you can't login at all by accident), just clean it by resetting the configfile that breaks the thing.

      You can have people run custom window managers, code their own software (even that damn window manager), whatever, if they happen to know how, while at the same time making sure they don't mess the system up if they don't.

      Now, imagine that user has to do some task, and they have messed up their configs. Now on Windows you either repair their profile (which can take quite a time if you can't login as them, if possible at all) or take backup of files, create new profile and copy the files over, on linux you just throw the default configs to their homedir and all you lose are few hacks in some files (say .bash_profile/.bashrc or may .Xsession)

      About the config thing.. if you setup linux in ~40 hours (for shared use) you are pretty fast. If you can do the same (in ~40 hours) for Windows you are superman. Start counting from when you get few hundred PCs with blank harddrives, with no images ready, etc..

      And once you get new systems with different hardware you have to do it again :) With linux you dump the same image and switch either kernel or module config.

      Windows has it's strong points, but administration isn't one of them. At least if you are trying to do it well. In a Uni even "we are not mission critical, we don't need the best security" isn't argument, since what would better target for a hacker than a Uni with a lots of computers and students doing all kind of things with irregular patterns.

      Btw, the Windows 9x/ME policy system is a joke :) If you can't get past it whily you can still do something with the system, you probably shouldn't be securing anything ;-)

      --
      Software should be free as in speech, but if we also get some free beer, all the better.
    8. Re:Another Solution - Windows Policy Editor by Spy+Hunter · · Score: 2

      Have you looked at KDE's kiosk mode? I understand Waldo Bastian has done a lot of work locking down KDE to be suitable for use in a public environment. And with Unix, you can have reasonable security without doing silly things like disabling shell access. Unix was made for secure multi-user environments and remote administration.

      --
      main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
    9. Re:Another Solution - Windows Policy Editor by dmiller · · Score: 2

      Why don't you write up what you like as a proposal to the KDE and/or GNOME teams - the situation isn't going to change if people sit on their hands.

    10. Re:Another Solution - Windows Policy Editor by Plug · · Score: 2

      And there's no way of doing this from Linux. You either get a Win2K server, or you define policy on _EVERY_ local machine, which kinda defies the point.

      If you have a way of pushing policy to Windows clients from a Samba DC on Linux you will make at least one sysadmin very very happy.

    11. Re:Another Solution - Windows Policy Editor by Mongoose · · Score: 3, Interesting

      Listen that's not true at all. You can run anything you want when you rename the EXE to a runnable like 'notepad.exe'. Add to this Word VBA scripting and you'll have admin on the box in seconds. In our lab we have people still installing porn and crap b/c it's so easy to do this.

      On a floppy copy an alternative shell for windows and name it say winword.exe. You most likely can run anything you want off the floppy, so then you just run say the kernel debugger or the MS hole of the week ( ie is weak to loading HTML scripting attacks off disk also. ) -- and then you can use policy editor to start mounting all those hidden windows shares and hijacking other user's computers.

      This is why windows is a joke - suid programs and permissions controls by name of a file.

    12. Re:Another Solution - Windows Policy Editor by siliconjunkie02 · · Score: 2, Interesting
      There are alot of assumptions here.

      "You can run anything you want when you rename the EXE to a runnable like 'notepad.exe'"

      This assumes that they have write/change and execute in the same dir.

      "You most likely can run anything you want off the floppy"

      You are admitting that the machine is misconfigured

      "and then you can use policy editor to start mounting all those hidden windows shares and hijacking other user's computers."

      This also assumes that the shares have been modified since by default the $/admin shares are only available to admins. Also I would like to know how to use policy editor to mount a share.

      Don't mistake poor configuration for a poor OS. *nix has its strengths but management at the desktop level isnt one of them. Windows has it beat IF you know how. But that goes for both

    13. Re:Another Solution - Windows Policy Editor by jez9999 · · Score: 2

      Dont give the execute permissions on any folder they have write access too. Simple as that, No more running things from their desktops. Just lock the thing down tight, dont let the execute anything anywhere and try to do whatever it is they need to.

      But newsflash: that sucks. If a person doesn't have their own computer (I know I know, but some don't), they WANT to be able to download stuff and run it! Why should they only be able to run the crap (read: microsoft office 2000/xp) prescribed to them by the system admin?

    14. Re:Another Solution - Windows Policy Editor by jez9999 · · Score: 2

      Don't give them write/change AND execute access in the same dir. Then you can be pretty sure that they arent renaming or getting their own .exe's.

      OK, and what good is that to a class of students trying to learn C++? I'll just compile the program and ... wha? It says I can't run it!

    15. Re:Another Solution - Windows Policy Editor by mpe · · Score: 2

      In windows you have to options: either you allow people to do everything or you allow them to do nothing. The policy editor just stops working once you allow someone to run an .exe from his desktop since he can break the system (with one of the numerous exploit that for example the GUI gives you.

      Also in older to use the "only run allowed executables" policy option you need to know exactly which files you need to allow to be run. Which can translate into lots of trial and error everytime you install/update an app.

      Now, imagine that user has to do some task, and they have messed up their configs. Now on Windows you either repair their profile (which can take quite a time if you can't login as them, if possible at all) or take backup of files, create new profile and copy the files over,

      You may still have problems, since there might be some critical data in the USER branch of the registry, how do you examine and manipulate this other than trying to login with that .DAT file?

      And once you get new systems with different hardware you have to do it again :) With linux you dump the same image and switch either kernel or module config.

      You don't even need third party tools to copy a Linux workstation, since the regular utilities will do just fine.

      Windows has it's strong points, but administration isn't one of them. At least if you are trying to do it well. In a Uni even "we are not mission critical,

      The students might disagree about the "mission critical" issue :)

    16. Re:Another Solution - Windows Policy Editor by mpe · · Score: 3, Informative

      That's irrelevant. Ghost is not windows. Ghost is not unix either. Ghost is a separate program you can buy. You could set up linux, some unix, bsd, or whatever the heck you want and ghost it to a 100 boxes in the same amount of time.

      Except that you could clone 100 identical unix hardware workstations using basic unix tools. No need for a third party product.

    17. Re:Another Solution - Windows Policy Editor by mpe · · Score: 2

      And with Unix, you can have reasonable security without doing silly things like disabling shell access. Unix was made for secure multi-user environments and remote administration.

      One of these environments was UCB, another was MIT... Are Australian students somehow more destructive than American ones?

    18. Re:Another Solution - Windows Policy Editor by Tony-A · · Score: 2

      Locked down so that cmd.exe doesn't work.
      Problem is, you want it locked down and cmd.exe *does* work.
      You set it all up nice and perty, but some program you have to run requires administrator rights for the user, and poof goes all your security.
      ls -l conviently shows owner and group and permissions. DIR does not.

    19. Re:Another Solution - Windows Policy Editor by ink · · Score: 2
      You are admitting that the machine is misconfigured

      OMFG... Being able to run programs off a floppy is considered a "misconfiguration" in the Windows Wild World of Security now? And you people wonder why we laugh so hard.

      --
      The wheel is turning, but the hamster is dead.
    20. Re:Another Solution - Windows Policy Editor by weave · · Score: 2
      GPO has a lot of holes and ways to get around things. Many of the restrictions are only enforced in the windows explorer shell. As for restricting to a specific set of programs, all you need to do to get around that is rename the exe of the program you want to run to be the same as one of the permitted programs and away you go.

      Maybe with Palladin and code signing and only allowing signed code to run, this will finally work! (*ducks*)

      It's all getting better in each release of Windows, but there still is a long way to go. There are so many programs that are not Windows logo compliant and to get them to work you must do inane things like open up that program's program directory to change access or open up large sections of HKLM, all things that would prevent a program from getting the logo. But when you scream at vendors, their usual response is to just give people local admin rights or power user rights.

      Some vendors are really bad. Adobe, for example, only has one program that is logo compliant according to their web site.

      You try to tell an academic department that they can't install program x on lab machines and you don't get much sympathy. A call or two later and some administrator is saying how important this program is and the (academic) program needs it and this could affect accreditation, etc, etc... so just install it anyway.

      An install is only as strong as its weakess link. NT first came out what, almost 10 years ago, and network servers with file ACLs were out long before that. Yet vendors still write their code thinking they have absolute full access to scribble data to anywhere on the file system.

      At least in Unix, I've never seen a user app that won't run unless all users are given root access and or write access to /usr/bin, /etc, and other fun locations!

    21. Re:Another Solution - Windows Policy Editor by JKR · · Score: 2
      The context was "locked-down box". If I walk up to your secured linux system with a statically linked, suid copy of Vi on a floppy and you "misconfigured" your fstab such that I could mount and run it, that's the same problem.

      Please don't be an idiot. Thank you.

      Jon.

    22. Re:Another Solution - Windows Policy Editor by Fulcrum+of+Evil · · Score: 2

      how do you examine and manipulate this other than trying to login with that .DAT file?

      Graft the dat file onto the registry somewhere and examine it there. It isn't hard, and you can even do it over the network.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    23. Re:Another Solution - Windows Policy Editor by Enigma2175 · · Score: 2
      If you have a way of pushing policy to Windows clients from a Samba DC on Linux you will make at least one sysadmin very very happy.

      It was my understanding that you create the policy then drop the *.pol files in the netlogon share on your PDC and the workstations will download them and apply them upon startup. I am working on implementing a Samba DC myself, but it is like pulling teeth to get anything to work right. So for now it is relegated to the test network.

      --

      Enigma

    24. Re:Another Solution - Windows Policy Editor by jez9999 · · Score: 2

      Yeah, except here, we're talking about CS students, and they should not be limited in this fashion.

    25. Re:Another Solution - Windows Policy Editor by gl4ss · · Score: 2

      .. at this one place, the windows computers were set so that you could only run executables named something(for example telnet.exe and such), and those executables could then launch anything they wanted.

      needless to say there were lots of funny shit on all desktops, ftp.exe with winamp icon, telnet with a very funky icon & etc.

      --
      world was created 5 seconds before this post as it is.
    26. Re:Another Solution - Windows Policy Editor by Arandir · · Score: 2

      I'll second your comment. I've never tried to lock down a Windows machine, but from what I've heard, it takes considerably more knowledge then what you learned in "Be An MCSE in 24 Hours".

      On the other hand, install a BSD or reasonable Linux distro, and you're done. For the paranoid (and you can never be paranoid enough), disable CDROM and floppy booting in the BIOS, password the BIOS, make everything but /var, /tmp and /home read only, and keep up to date on the security issues.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    27. Re:Another Solution - Windows Policy Editor by Arandir · · Score: 2

      if you setup linux in ~40 hours (for shared use) you are pretty fast.

      I sure hope Linux isn't that horrible. I spent 20 hours setting up a FreeBSD box securely for shared use. 15 of those hours had nothing to do with configuration or security, but were peripheral tasks like writing site-specific admin and user manuals, testing, etc.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    28. Re:Another Solution - Windows Policy Editor by dvdeug · · Score: 2

      The context was "locked-down box". If I walk up to your secured linux system with a statically linked, suid copy of Vi on a floppy and you "misconfigured" your fstab such that I could mount and run it, that's the same problem.

      There would be no problem running it. But the floppy drive is usually set nosuid, so it would just ignore the suidness of the file. Nonprivliged users can't preserve the suidness of a file while copying, either.

    29. Re:Another Solution - Windows Policy Editor by SectoidRandom · · Score: 2

      I enjoy dealing with users with your attitude. As someone else pointed out since the use of Company/School resources is strictly controlled (and always should be), the first thing I do when a user complains about not being able to change the desktop walpaper is add that GPO (Group Policy Object) to the now heavily restricted user!

      hehe

    30. Re:Another Solution - Windows Policy Editor by jez9999 · · Score: 2

      I didn't know the BOFH perused the Slashdot discussions! :-)

    31. Re:Another Solution - Windows Policy Editor by deblau · · Score: 2
      Group Policy kicks ass. You can completely lock down a machine so that cmd.exe doesn't work no matter what and the only .exe's that do work are the ones you specify. You can let the user specify their Display preferences, but nothing else. Or everything except the Display preferences. The point is, Linux has nothing to compare with this.

      Sorry to burst your bubble, but it's called /etc/group, and it was invented long before Windows.

      If Linux had anything to easier to compare to this I'd be using it (admins being essentially lazy).

      Uh, no, that's users who are lazy. Just because you know how to admin, don't mean you're an admin. I run Windoze at home. Why? Because at home, I'm a lazy user. Says nothing about my day job...

      The FACT is no one has a better way to administrate and trouble-shoot end-user desktops than Microsoft right now.

      Uh, sorry to burst your bubble again, but that's an OPINION. Another opinion is that you're a troll.

      --
      This post expresses my opinion, not that of my employer. And yes, IAAL.
  5. the original quote by SHEENmaster · · Score: 2, Funny

    And 1.1.81 is officially BugFree(tm), so if you receive any bug-reports
    on it, you know they are just evil lies."
    (By Linus Torvalds, Linus.Torvalds@cs.helsinki.fi)

    --
    You can't judge a book by the way it wears its hair.
  6. People read the article! by Mustang+Matt · · Score: 5, Interesting

    By locking down, I think they mean students can go in and randomly format the drive like they could in a stock Win9x setup.

    They also mention that they like linux because it's easy to give to students. They don't have to worry about costs or licensing, they just hand the students a CD and they're on their way.

    "We'd rather explain how things work. We do that by taking things apart and putting them back together again, rather than just showing people how to use particular GUIs that other people have designed. It's our belief that open-source software better explains those concepts," he said.

    That seems pretty logical to me. The article really wasn't about taking away freedom at all.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  7. Learning Experience by Amigori · · Score: 2
    This will be an experience for all parties involved, students, teachers, and admins. The admins learn how to properly lock down a system, the teachers learn more of the nuances of the system as..., the students learn how to overcome the limits set by the admins. Good show, I say... I just wish more schools, specifically my old high school, would look into locking down there systems, even if they keep windows. Windows 2000/XP has a nifty policy editor that helps on preventive maintenance.

    Speaking of switching, and maybe OT, I've been contemplating more and more about switching back to a *nix based system as all the games that I want to play will not run on my system and I am not too keen on building another one that will just be outdated in a year...(Am I growing out of my geekness, or just tiring of spending so much money?)...Its almost as big of waste of money as my car is...No, I think I will just optimize the one that I have and probably load OpenBSD on it.

    Amigori

    --
    "The quality of life is determined by its activites."--Aristotle
  8. Windows Policy Editor - could it be any worse?? by dan_barrett · · Score: 5, Informative

    Yes, you *could* use windows policy editor, but there are some major issues with it (having just locked down a standalone windows box for kiosk use I'm well versed in the pain of poledit for Win 2000..)

    Note that policy editor is now primarily designed for a computer in a Active directory tree - without active directory you have to edit a "local" policy, ie edit the registry directly.

    A disclaimer: maybe an active directory policy is nicer to play with, I don't know - local policies were enought of a pain for me as it was..

    here's the fun with local policies..
    firstly - the policies affect ALL users, INCLUDING the administrator. (WTF?!?!? you say?) so.. lock out all registry tools, disable "command prompt" and run on the start menu - and you're screwed - no more windows administration. time to reformat the box. (or at least attempt to "rescue disk" it..

    second - policies quite often are applied in REAL TIME. hmm.. disable registry editing.. (screen flashes) - oh bugger, policy editor has stopped working..

    The way to get around this is to remove access to the %winnt%/system32/GroupPolicy dir for the administrator (that's right, you remove access to the root user to prevent the policy applying to that user.) of course, this dir has to be accessible to make any changes. And the changes apply immediately. Forget to reapply the restictions to the admin user and it's reformat time, again.

    if you want to use policy editor I suggest having a recovery cd lying around, as I guarantee you *will* be locked out of your system, unless you're extremely careful.

    I love windows security, it rocks.

  9. GNU/Linux is still usefull after lockdown. by XTerm89D · · Score: 2, Informative

    That's the difference between a secured Unix system and a 'Windows policy editor lockdowned' system.

    In windows you just have to close down all ways to do nasty things. End result : undestroyable but also completely useless pc. Nobody can do anything on it.

    With a Unix system, students can't mess around anything BUT they can do whatever they want in their personal enviroment and a Unix box is still a usefull tool without root access.

    1. Re:GNU/Linux is still usefull after lockdown. by mpe · · Score: 2

      In windows you just have to close down all ways to do nasty things. End result : undestroyable but also completely useless pc. Nobody can do anything on it.

      Assuming you don't miss some of the holes and end up with a trashed machine anyway. Maybe because of some piece of malware rather than user vandalism.

      With a Unix system, students can't mess around anything BUT they can do whatever they want in their personal enviroment and a Unix box is still a usefull tool without root access.

      It's even possible that they may mess up their user area so they can't log in, but that dosn't affect every other user. Quite often the attempts to make Windows multi-user don't quite work.

  10. Why use anything other than Linux for comp sci? by Omega · · Score: 5, Insightful
    When you think about it, Linux really is the best operating system for comp. sci students. It offers open source access to the kernel, so you can see the actual code for the operating system and how it interacts with many different types of hardware. Also you have low level access to many devices through the dev. tree so you can teach device programming methods. Not to mention the fact that the primary unix networking protocol (TCP/IP) is the same protocol that runs the internet. What better way to gain an understanding of packet based protocols than by experimenting with BSD sockets? "The Unix Time Sharing System" by Dennis Richie is one of the most elegant descriptions of an operating system that I have ever read. And by working with the text and the operating system together, students can gain a fundamental understanding of many basic low level concepts in modern computers.

    If all you want is to be an MCSE, then why waste you time with college? You can take a weekend course for a few hundred bucks (instead of 4+ years for several thousand dollars). This quote from the article by Dr. Chris McDonald of UWA pretty much sums it up:

    "Personally, I think that just showing students how to use operating systems tools and networking tools, is more training than education.
    Exactly. Showing someone how to point and click isn't teaching them anything. It's only training them how to use someone else's tools (and there are books that can teach you that in 24 hours). Real computer science education, where you gain a fundamental understanding of both high and low level concepts of the computer requires more than just clicking a start button.
    1. Re:Why use anything other than Linux for comp sci? by dubious9 · · Score: 2

      I can't say how much I agree with you. In interviews know I've been getting the question, "If you could give one piece of advice to an incoming CS student, what would it be?" My answer? Learn linux.(the reasons for this answer usually fly over the head of the HR interview person and I get blank stares)

      If I'm ever in the position to hire new graduates, I'll ask about their linux exposure in school. IMNSHO listing linux always looks better than listing windows. Microsoft is working hard to make sure that any old idiot can half work their computer, but to be functional in linux (now at least, ) require much more insight into the workings of a computer.

      Almost as valuable, would be commandline development familiarity instead of solely GUI IDE.

      --
      Why, o why must the sky fall when I've learned to fly?
    2. Re:Why use anything other than Linux for comp sci? by sheldon · · Score: 2

      "It offers open source access to the kernel, so you can see the actual code for the operating system and how it interacts with many different types of hardware."

      That's great if you are taking the OS track of ComSci... But that's only one small part of the entire CS curriculuum.

      "If all you want is to be an MCSE, then why waste you time with college?"

      The MCSE is a systems administrator certification. Presumably if you are in ComSci you intend to learn more about software development, so this argument appears to be a non-sequitor.

      "Real computer science education, where you gain a fundamental understanding of both high and low level concepts of the computer requires more than just clicking a start button."

      When I was in ComSci the students didn't even know how to load paper in the printer. I'd have to say some fundamentals of computer use are probably important. Disappointing perhaps, but important.

  11. Slashdot Social Experiment by kNIGits · · Score: 5, Interesting

    People have been saying for years that Slashdotters don't read the article, so I thought that I'd test the theory. I'd submitted the story and highlighted something insignificant about the article in the submission. Browsing through this page, I see lots of people discussing merely what I wrote at the top - 'locking down' students. If people actually read the article, they'd see that it was more about teaching software development in an open source environment, and also the fact that they can give free Linux cds to the students to replicate their training systems at home.

    What I'd like to know is - how can the Slashdot Effect exist when no-one clicks through to read the article?

    This karma-reducing social experiment was proudly brought to you by kNIGits in Australia.

    1. Re:Slashdot Social Experiment by sco08y · · Score: 3, Interesting

      The people who karma-whore try to get their posts in as quickly as possible because, as the FAQ says, if you get in sooner more people will read it and it's more likely to be higher ranked.

      Because of the karma system, you're only seeing people who employ karma-whoring strategies rather than intelligent commentary. That means making politically correct comments about whatever the submitter said. That means mouthing the standard, "freedom-reducing lock down is bad!" kind of remarks.

    2. Re:Slashdot Social Experiment by apol · · Score: 2, Insightful
      how can the Slashdot Effect exist when no-one clicks through to read the article

      Hmmm my bet is that while half of slashdotters are looking for the article and producing the slashdot effect the other half is busy writing "insightful" comments based on their guesses. Since the earlier you write the more likely you are moderated up, the most typical slashdotter is finally the one who does not read...

    3. Re:Slashdot Social Experiment by archen · · Score: 2, Insightful

      Theory A: Article never works because it's always slashdotted.
      Theory B: Some of us avoid reading an article to avoid slashdotting a server.
      Theory C: Some of us don't care about the topic and only want to read what others have to say. Then we randomly reply wherever we want, to stuff that was probably misinformed in the first place. If you want ontopic threads, post an ontopic summary.

  12. Re: Windows Policy Editor - could it be any worse? by agallagh42 · · Score: 4, Informative

    Just because you don't know how to use a tool, doesn't make that tool bad.

    A properly configured local policy can lock down exactly what you want to lock down, and affect only the users you want it to affect.

    Also, in Active Directory, you use things called "Group Policy Objects" to apply policies to workstations, and it's WAY more powerful than local policies.

    Go here for an overview of GPOs.

    --
    Carpe Cerevisi - Seize the Beer
  13. Don't fixate! Read! Read! by BiOFH · · Score: 4, Interesting

    It is making ground in IT courses because Linux is both easy to lock-down, easy to pull apart and offers simple licensing for distribution to students.

    Please stop fixating on the whole locking down bit!
    Timothy craftily negelected to list anything but the potentially inflammatory and sensational 'lock down' phrase. It's EASIER for them to use Linux (and makes more sense and it's CHEAPER), not "they can't lock down Windows". These are newbies who DO know how to fuck up a Window machine pronto. They'll have to do some learning before they can pull a good cock up of their Linux box. And since this is a Uni, students learning is kind of high on their list of 'things we want to happen'.

    And please take note this is not the whole Uni. My girlfriend works there and she (and her whole department) uses Macs. But it is a step, IMHO, in the right direction for UOW.

    --
    - I am made of meat.
  14. Answer by BiOFH · · Score: 2

    Answer: They only click through to look at pictures of Lego, Linux handhelds and case mods. ;)

    --
    - I am made of meat.
  15. As someone at an Australian university... by CaptainPotato · · Score: 4, Insightful
    ...who wishes to do convince the IT powers that be to do the same, I am very happy to hear about other institutions that are doing the same. Whilst there remains a need for Windows-based machines, Macs, and whatever else is used, there are many compelling reasons for switching to Linux - these are just a few I have (whilst on University time...).

    1. Control. Whilst I would normally shudder at the thought of restricting IT access, I do appreciate UOW's desire to better manage their machines. We recently had some new machines running Win2k installed in my area, and within a day, one was in poor shape thanks to a particular idiot installing the latest Windows Media Player version on it and somehow stuffing up the OSA installation. He was able to so do thanks to the IT stroke of genius of giving everyone admin access. Whilst this may be an human issue rather than an OS one, every bit helps :)

    2. Cost. We are all aware of the studies that compare the cost of Linux to other OSes. In any case, regardless of the outcome, I do know that my insitution will be spending multiple millions per year (as of next year) for desktop software licences for MS products because of the new licence arrangements. In a country that has mounting financial challenges in university funding, alternatives to MS software need to be found.

    3. Ethics. Maybe this is too strong, but IMO it is not. Why should tapayer money be spent on making a single corporation (even) richer? A centre of teaching and research ought to have academic independence of multinational corporations.

    These are just a few, IMO, valid thoughts about the issue. Regardless, UOW deserves to be applauded for the initiative.

    --
    I heard that your library burnt down and destroyed your only two books - and one was not even coloured in yet.
  16. Just be careful by albino+eatpod · · Score: 2, Interesting

    My University's PC lab ran linux (dual boot with Win 2k), but it also ran telnetd which anyone with a computer science login could telnet to. This led to some interesting fork bomb wars between 'friends', and didn't really help us get on with our (probably late) work. Ironically, although Linux is chosen (amongst other things) its security, it was Windows that was the most secure in this case, simply due to poor administration.

    They've actually removed Linux at the moment, as they attempt to change their linux policies.

  17. uow labs by Tristessa · · Score: 4, Interesting

    Being at UoW and knowing the people who did this I can't say it's a surprise. The only things that windows were really used for in those labs were software engineering type programs and Word/Excel for the first years and non-compsci people who used the lab.

    There are other compsci labs around that haven't been dual boot for longer than this. The article also doesn't mention anything about the proportion of CompSci(linux) machines compared the number of mac/wintel machines around the uni which I'd estimate at around 85-90%

    At least the compsci department support staff are always trying new things, actually being taking initiative about things. kudos guys. see you for a drink soon.

  18. This will by katalyst · · Score: 2

    either result in mundane Linux users, or HARDCORE linux hackers :D Both of which, I guess, are better than mundane Windoze clickers.
    Unfortunately,unless we have an industry standard office suit to compete with Microsoft Office, lots of companies are going to hold back. Comments,merging and other aspects of Word which make professional and academic documents exchanging and analyzing easier are still missing in Open/Staroffice. The publishing industry: they would love to shift to linux, but the fonts/word processor aren't up to the mark. But Linux will get there -> soon.

    --
    |/________
    |\A|ALYS|
  19. duel boot by Joakim+A · · Score: 5, Funny

    >The Uni of New South Wales Computer Science and
    >Engineering department has been running
    >unix/linux for years, no duel boot.

    Well, duel boot, that is something I would like to run. Just install windows and a few linux/BSD dists, turn on the machine and leave it over night. Then we finally could settle this thing.

    /J

    Ps My bet is on that spiky fish eventhough that little red bastard with the fork might be nasty. I mean, how hard can it be to beat a geek from redmond or a penguin? Hmm, could be a whole army of penguins of course, well that might get tricky.

    1. Re:duel boot by NoOneInParticular · · Score: 5, Funny
      I'm not sure about the geek from redmond, but before you belittle penguins, consider these words from Linus Torvalds:

      "Some people have told me they don't think a fat penguin really embodies the grace of Linux. Which just tells me they have never seen a angry penguin charging at them in excess of 100 mph. They'd be a lot more careful about what they say if they had."
    2. Re:duel boot by xchino · · Score: 2

      Haven't you ever seen the Quake logo of Tux with the rocket launcher? I think the BSD's definately got trouble :)

      --
      Everyone is entitled to their own opinion. It's just that yours is stupid.
  20. Just a Thought... by Hasie · · Score: 5, Insightful
    I see their point, and I agree that Linux has a place in any computer-related university curriculum as an introduction to UNIX (even ignoring the other advantagess it has), and I am a major Linux fan (to the point that I actually find Windows difficult to use).


    (You all know what comes next:) BUT, I don't think that Windows should be completely eliminated. Windows is still the de-facto standard in industry and universities owe it to their students to give them skills they can use. It is also essential that universities maintain neutrality in the sense that they do not give the impression that they are promoting one system over another - a university's role is to eductate and do research, not dictate what the world will do or follow current fads.


    Before everyone gets the wrong idea; I use the same argument to motivate the use of Linux at the university where I work (it is a very good way to teach students UNIX rather than only teaching them Windows). So what is needed is a balance.

    1. Re:Just a Thought... by dubious9 · · Score: 2

      How many computer science people do you know didn't already know windows when they got to school? It's not like they are going to stop using windows. If anything just for the gaming.

      What windows skills would they be missing? Visual C++/Basic/C#? I agree with other posters here that you teach skills, not languages.

      Most of what you learn (or what I learned anyway) in a CS program is OS independant. Linked lists, dynamic memory allocation, objected oriented structure, encryption, sorting etc. etc. will work the same on any operating system.

      In a windows based curriculum, however, you have to simulate more advanced things such as network layer protocol, interprocess communication, file systems, schedulers, i.e. anything implemented in the operating system. In an open source based you can actually do it and not have to use some crappy simulation code.

      In conclusion, what do you get from windows? Learing windows API maybe in one class? The advantages of linux outweigh the advantages of windows. Linux's main weakness is its strength here: it take someone who knows computers well to administer it.

      I assume the only thing holding a lot of universities back is retooling for linux. This will take a lot of infrastructure and writing a lot of new educational software (i.e. half complete, fill in the missing fuction stuff)

      --
      Why, o why must the sky fall when I've learned to fly?
  21. Dual-boot? by Z0mb1eman · · Score: 3, Insightful

    >machines in first-year labs that used to boot from either Windows or Linux have been changed to Linux only.

    That sounds like a LOT of hassle for the admins in the first place... University of Toronto has separate Linux Redhat, Win2000 with Netware, and (still a few) Solaris labs. Separate rooms, separate operating systems, just go where you need based on what you need to do. The Windows machines are even more "locked down" than the Linux ones - you can't even change the wallpaper, for example. Can't move/remove icons, can't change the start menu, can't (really) install programs. I've never seen a trashed Windows machine, whereas I've seen Linux machines that have gone belly-up with a rather pissed off admin trying to fix it. Then again, I spend more time in the Linux labs.

    The dual-boot idea for a public lab makes very little sense to me in the first place - if the university's THAT desperate to save money, maybe it's not the best place to go. More likely though, the admins realized the way they were doing things wasn't really the best way, and changed to something more logical and easier to manage (and not all that new or innovative at that) - how does that constitute news??

    --
    ClutterMe.com - easiest site creation on the Net. Just click and type.
    1. Re:Dual-boot? by g4dget · · Score: 2
      whereas I've seen Linux machines that have gone belly-up with a rather pissed off admin trying to fix it. Then again, I spend more time in the Linux labs.

      Linux machines don't just go "belly-up", and certainly not from normal usage.

      In any case, a common way of dealing with this is to not worry too much about students doing stuff as root at all--you just have the machine reboot on logout and restore the default installation with "rsync".

  22. just like USyd by djshiawase · · Score: 2, Informative

    The University of Sydney's got a huge unix tradition - not as much as UNSW but i think Aust has always been unix-inclined, out of the 'pressure spotlight' I suppose, or something. The admins love the linux computers here, they never have do anything to them. Especially the Tektronix dumb terminals, they just sit there and accept input. Slow as hell though, I use them only when I need to get an assignment done and there's no computers left. I think they're retiring them over the Christmas break, that whole lab area is being rebuilt.

    The whole backend runs on linux clusters (went to a little after-lecture talk about it). File servers, CPU servers, connection servers. They have a few sun servers but one of them explode every year and they haven't bothered replacing them. Clusters are so much cheaper!

    The last batch of new systems we got at the beginning of last year for 5 labs, P4s with TFTs, bucks this trend though, as 4 of these labs got Win98 and the other Linux. They don't even bother locking these Windows down either, they just wipe and upload drive images from the server every night.

    Though that kind of sucks, means we have to reinstall Warcraft 3 every day.

    --
    they made me do it
  23. Going towards it here... by imevil · · Score: 5, Insightful

    At my school the math section has linux-only PCs for the students. The CS section has Solaris (SUN) and Windows-only machines, and they justified the no-linux by saying that the companies use Windows so no point in teaching Linux to the students. I think they got it all wrong: more and more companies are migrating to Linux, and in a couple of years there will be a need for Linux experts.

    GNUWin: open your Windows!

    1. Re:Going towards it here... by Peyna · · Score: 4, Insightful

      A CS degress means you know how it all works, but you don't have be an expert in any particular langauge, operating system, or application. Instead you should be able to easily adapt to a quickly changing field.

      For all we know, there may be some new radical ideas in the next few years that void the need to be an expert in Linux or Windows. What a horrible waste of time to work at perfecting a restricted set of skills for a proprietary system.

      --
      What?
    2. Re:Going towards it here... by mpe · · Score: 2

      At my school the math section has linux-only PCs for the students. The CS section has Solaris (SUN) and Windows-only machines, and they justified the no-linux by saying that the companies use Windows so no point in teaching Linux to the students.

      Even if "the companies" do have Windows machines they are unlikely to be the same version of Windows or set up in the same way educational networks are set up.

  24. Looking down anything? please help me with.. by fractaltiger · · Score: 2

    I had just made a journal entry about this issue:
    how can i set a quota on solitaire's use on my box? :)

    dad will now have to find a second hobby or some other box. thanks, slashdot!

    --
    "Wireless : LAN :: Laptop : Desktop"
  25. The important thing by SLOGEN · · Score: 2, Insightful

    The important thing, is to not provide Free (as in beer) training to one OS vendor, radically unbalancing the competition in the OS market.

    The danish goverment spend millions of dollars each year on "teaching the people to use IT", which basically boils down to giving users a training course on all M$-OS and Office products.

    I suggest having a mix of OS'es, so that the students have different experiences and learn from comparing those.

    I myself is a student at DAIMI where machines with SunOS, HPUX (well not that many anymore) IRIX, GNU/Linux and Windows (Using vmware), and yes it's a pain with the differences between computers but:

    1. You can just select to use the same OS every time
    2. You learn a lot by seeing different solutions to the same problem

    --
    SLOGEN [ http://ungdomshus.nu : Sebastian cover music]
  26. Fools. Here's proof. by BiOFH · · Score: 2

    Tell your CS people they're living in a dream world. Linux has made great leaps and bounds inside corporate IT. If they only want their graduates working for small-time ISPs then carry on. It's nice to see they have Solaris, but that's probably only because of their mis-guided (and out-dated) view that Solaris==The Web.

    I just left Intel where my department (an IT group) supported _thousands upon thousands_ of Linux boxes both in the server room and on the desktop.
    Take a look at the length of this server room:
    http://www.anandtech.com/showdoc.html?i=158 4&p =10
    A good 3/4 is filled with machines running Linux.

    It's sad when consumer mentality leaks into the professional level. But that's what happens with America's backwards management ideas (if something makes sense and works, it probably needs more managers and those managers don't necessarily need to understand the 'product'...). Anyway... good luck to your school's CS curriculum. They need it.

    --
    - I am made of meat.
  27. it's a solution--just not a good one by g4dget · · Score: 2
    Group Policy kicks ass. [...] The point is, Linux has nothing to compare with this.

    Sure it does. By default, regular Linux users can perform no system management functions. You give them access to system management functions through setuid and setgid programs. You can control access to those on a per-user or per-group basis using standard UNIX protection mechanisms.

    If you like something more general, you can use the "sudo" program, which allows detailed policies to be specified of who can do what as who and when, and it also logs the actions.

    The FACT is no one has a better way to administrate and trouble-shoot end-user desktops than Microsoft right now.

    As usual, Microsoft has an in-your-face solution that screams at you "I let you edit policies; here is a point-and-click interface--isn't it easy?". Trouble is, in real life, the options it gives you are rarely the options that are needed, and extending and managing those policies is a chore.

    The UNIX/Linux solution is simple, elegant, powerful, and has proven itself for more than 20 years in large, multi-user environments.

    So, the "FACT" is, "Windows Policy Editor" is indeed like a lot of Windows: flashy but not all that useful in practice.

    1. Re:it's a solution--just not a good one by g4dget · · Score: 2
      FWIW, you can do all the things you mention with Windows. [...] Before you go bashing something, please be informed about it.

      Before you go criticizing something, perhaps read it more carefully: nowhere did I claim that you couldn't also use equivalent set-user-id mechanism under Windows; they just happen to be rather cumbersome to deploy and manage compared to the UNIX approach.

      You see, the value of the original UNIX design is in its minimalism: it makes it easy to use a small set of necessary and sufficient mechanisms. The UNIX designers were as busy removing features from the OS as they were adding new features.

      The Windows philosophy is to give you features and more features and more options, and to wrap that up in GUIs. Sorry, but more isn't better, it's usually worse.

    2. Re:it's a solution--just not a good one by g4dget · · Score: 3, Interesting
      as opposed to per machine is a HUGE advantage in my book

      You must be talking about what Windows used to be like a couple of years ago, since networks of UNIX workstations have never been managed like that. Come on, people have run UNIX networks with thousands of machines since the 1980's. Do you think they didn't figure out how to deal with those issues long ago?

      There are several common ways of setting up such networks, and they are generally much simpler to deal with than anything Microsoft offers even today. Adding a new machine to a UNIX network requires no more than just plugging it into the network and possibly adding it to a list of recognized clients. Users, data, and applications are installed centrally. Applications run transparently over the network, or locally, whichever way you prefer. "The latest patches" or "new applications" aren't even issues--things are just automatically consistent.

      Windows has taken some of those ideas and thrown them together into an inconsistent and cumbersome juble. But where networks of UNIX workstations just tick along by themselves, Windows-based networks require constant handholding, fixing, patching, and reinstalling. Microsoft is trying to paper over how messy and dysfunctional their system is with lots of dialog boxes and GUIs, but it just doesn't help: in the end, managing Windows networks is still a lot more work. Oh, of course, you can try and buy lots of expensive third party software to get some of the UNIX-like manageability, but that only makes things even more expensive and complicated.

      I used to manage networks of UNIX workstations with dozens of users on the side. If I had to spend more than an hour or two on it per week, that was the rare exception (and then it was usually due to some hardware failure on the server). And I certainly didn't need any expensive or complicated third party software for doing it either.

  28. at length == ~40 hours? by mangu · · Score: 2
    I have used Linux since 1995, let say a few thousand hours total. I have used different versions of MS-windows since 1990. THAT is "at length".


    On the administration issue, that "group policy" you mention and most other resources you find for managing windows machines depend on the GUI. You must sit at the machine in question and click the right boxes in the right windows. Try to do this on a few dozens, a few hundreds, a few thousands of machines without a mistake, without forgetting any step.

    1. Re:at length == ~40 hours? by mangu · · Score: 2
      maybe you should read more about applying GPO's to OU's.


      Why should I? If it works in Linux, if it has worked for decades in Unix and VMS, why should I read more about some crappy system with huge binary configuration files?


      The kind of configuration my company demands must be simple and reliable. It uses small text files, which can be printed on paper and filed away. The files must be small because one must be able to check them personally. They must be on paper because, when all else fails, when there are suspicions of intrusion, one must have a hard copy which one is absolutely sure is the trusted version.

    2. Re:at length == ~40 hours? by mangu · · Score: 2
      someone points out how you're wrong,


      How so? Who pointed out I was wrong? All he said was that I should read more about windoze system adnministration. What this proved is that it's MORE difficult to manage windows, since it takes a lot of study to learn how to do it not-so-badly.


      you can also use the Group Policy editor to export the settings to a text file, and it is pretty simple and reliable.


      No, it's not reliable. The registry is still a huge binary file, no matter how many .inf files you have. Crash that registry, your system config is lost. In Linux I can delete all my system directories; all it takes to recover is to put in the CD, copy the system directories and copy the back-up /etc directory. A couple of minutes at most.

  29. that's easy to deal with by g4dget · · Score: 2
    That's easy to deal with: either you adopt the Windows model and disallow remote logins for users different from the console user, or you set reasonable limits on the number of processes and amount of memory per user.

    Keep in mind that Linux, out of the box, is configured for single-user desktop use. You do have to do a little bit of configuration for a multi-user environment.

  30. Also at Auckland Uni in New Zealand by nzAnon · · Score: 2, Interesting

    Auckland Uni is expressin the dis-satisfcatin with Microsoft licenscing policy by moving to Sun Microsystems' Star Office.
    Read here: http://www.nzherald.co.nz/storydisplay.cfm?storyID =3047439&thesection=technology&thesubsection=gener al

  31. This is significant news by heffrey · · Score: 3, Insightful

    If the prestigious and world famous Department of Informatics at Wollongong University have taken this decision then I'm pretty sure the rest of the world will follow suit in short order.

    This story is typical Slashdot. Small university department moves to Linux (= big story); Multinational Company switches from Sun to Microsoft (=no news).

    Small earthquake in Chile, not many dead.

    Yawn.

  32. Maybe it's easier to lock down... by Kjella · · Score: 2

    ...but I know from experience that a windows box can be equally hard, and that was an all-software solution. I couldn't get *any* non-approved program running at all, even those that need no dlls or registry settings. I've always been able to get around it somehow before (find a temp dir where I have write permission or something) but no. Not at all. Even when I got my own laptop I had to struggle bad with the universitys firewall most ports both in and out, but I did manage to get past that at least. But noone tell me a windows box *has* to be easy.

    Kjella

    --
    Live today, because you never know what tomorrow brings
  33. In other news, the University of Queensland... by little_fluffy_clouds · · Score: 3, Interesting

    ... dumped all of their UNIX machines in computer science and bought new Windows labs about 3 years ago. I know, because I was there starting the undergrad. As of March, they claimed the course was not going to change at all - by November they had dropped such "obselete" subjects like Algorithms and Data Structures and picked up crap to do with web applications nobody will even remember in 2 years (it's been three and I have no clue). I was disgusted by their sellout, and moved to another, UNIX oriented University (University of New England), where each undergrad (I was external) is *required* to install Linux or another UNIX/UNIX like OS in first year, and all assignments from the very first are submitted on a Linux machine, where they must compile properly (I develop on NetBSD, but never had any issues at that level compiling and submitting on the Linux machine).

    Fuck UQ and their sellout for the almighty buck. If that is not what is was, I apologise, but it sure looked just like that from where I was at the time. I feel for the academics caught in the middle of it all.

    --
    What were the skies like when you were young?
  34. Re:Support by greenrd · · Score: 2
    Yeah, you can change the permissions on NT too, but then you run the risk that nothing will work.

    You have to have an admin who really knows what they're doing (unlike those at my school, who made it so that Explorer wouldn't run on login (!?) on the demonstration machines). And even then you still have lots of software that won't run properly except when run as Admin.

    On Red Hat you already have permissions set up for you, and you don't really have to change much. Yes, users can choose their own wallpaper etc. - but what's wrong with that? They should be allowed to do that if it doesn't affect anyone else or cause system instability.

  35. What a Joke by ink · · Score: 2
    Dont give the execute permissions on any folder they have write access too. Simple as that, No more running things from their desktops. Just lock the thing down tight, dont let the execute anything anywhere and try to do whatever it is they need to. Then open it up as needed. With GP you can disable Active X and all that in pages, so no more worries about that.

    So this is what passes for Windows security then?

    A secure UNIX system will allow the user to run ANY binary. Period. They may not have permission to write to some file in /etc, or they may not be able to install shared libraries in the system path... but I can't think of a bigger waste of time than having a default-deny policy on executables and then punching holes in it so that only "safe" programs are allowed to run. What happens after an upgrade? Do you have to do it all over again? What happens when users need a security patch? You have to re-mirror the box? Operating systems have built-in security mechanisms so that these things shouldn't need to be done. That the tools to do them exist under Windows, that they even ship with them and that they are the reccomended manner to secure them is just... laughable.

    --
    The wheel is turning, but the hamster is dead.
    1. Re:What a Joke by SectoidRandom · · Score: 2

      Not that im very keen to stand and defend Windows but you mention "A secure UNIX system" like it's an every day thing. But the fact is local-root exploits even effect OS's like OpenBSD! Sure *ideally* well administered and upto-date systems will be safe from 99.99% of people, but if you think that *any* system can be completly protected from a user with local access then I think that is what is laughable!

      The fact that you can lock down exe's in Windows from my experience was only useful (and necessary) in Windows 9x as since NT4 any good administrator could secure the box for all but that 0.01%.

  36. policy lockout by Erpo · · Score: 2

    firstly - the policies affect ALL users, INCLUDING the administrator.

    I have some experience adminstrating a win2k active directory domain so I can offer some advice in that area: policies only affect all users by default -- you can change this behavior. When you create the new policy, click the "edit" button (I think its this one. If not, it's the other button with a similarly suggestive name.) and you can edit the policy ACLs by hand. See that little check box marked apply in the "Authenticated Users" entry? Uncheck it. If you do this _before_ hitting apply you'll be fine every time.

  37. Oh, that's EASY by ink · · Score: 2
    You just need the Active Solitaire Group Policy Administrator t001 that ships with Windows 2000 SUPER Advanced Server. Microsoft has forseen your need for this problem and provided a complete API for Visual Studio dotInfo which allows IT profeshunals to not only control how many times Solitaire is run by individual users, but it supplies an ACL which allows the per-user limits to change based on how many times others have utilized this program. This means that your boss coule be allowed to play Solitaire only when your vacation requests have been properly filled out (see obscure documentation for the Active LookOut Vacation API Plugin -- and be sure to download the 27 hotfixes we have for this tool that runs with SYSTEM privileges).

    Yes, you can now use the Solitaire Administrata MMC Plugin from any other properly-licenced member of the 2000 SUPER Advanced Server domain (as long as it's using the latest version of Windows, anyway) to manage your company's ability to waste time all day. We plan to rollout future versions of this IT management tool for other titles such as Freecell and Pinball. Look for updates on MSDN.

    Microsoft. We not only make computing EASY, but we make it BLODDY STUPID to boot, by fixing the symptoms of problems INSTEAD of the root cause.

    --
    The wheel is turning, but the hamster is dead.
  38. Did this in 95 by KjetilK · · Score: 2
    Well, actually, I was the student's representative in the computing committee of the physics department of my university. I realized quite early that Linux was a lot better than Windows for most things physics students would want to use it for. Before I got into the committee, the committee held the opinion that Windows was what the students was familiar with, so they would want to use that. First, I persuaded them to start using dual-boot, but eventually we realized that becuase of the sheer time it takes to reboot, most machines would never be rebooted, people would use the OS there was. And for most of the time, that was Linux. So, I argued that it was better to have a small number of Windows-only boxes, and a bigger number of Linux-only boxes. Eventually, people would stop using the Windows boxes, so when I quit the committee, there were only Linux boxes there.

    Nowadays, they have a bigger room that is shared with students from other parts of the campus, so the number of windows machines have gone up. But the physics students stick to Linux.

    --
    Employee of Inrupt, Project Release Manager and Community Manager for Solid
  39. Speaking of Idiots... by ink · · Score: 2
    The context was "locked-down box". If I walk up to your secured linux system with a statically linked, suid copy of Vi on a floppy and you "misconfigured" your fstab such that I could mount and run it, that's the same problem.

    You make my point. A "locked-down" UNIX box wouldn't care if you managed to get a statically linked copy of vi on your system. You could get it over the network, too, so I suppose a "locked down" Windows machine disables the network device?

    Please don't be an idiot. Thank you.

    Eh, yes... good advice in heaps, I see.

    --
    The wheel is turning, but the hamster is dead.
    1. Re:Speaking of Idiots... by JKR · · Score: 2
      ...statically linked, suid copy of Vi...

      A "locked-down" UNIX box wouldn't care if you managed to get a statically linked copy of vi on your system

      Did you READ the word "suid" in that sentence? If I have a user account and can get or copy a suid binary somewhere I can write/copy over it (i.e. my home directory, /tmp...), your box is toast because I can make any program I like run as root...

      Jon.

    2. Re:Speaking of Idiots... by ink · · Score: 2

      Try it out. Once a user mounts a removable device, all the files are owned by that user; in your example vi would be suid to yourself.

      --
      The wheel is turning, but the hamster is dead.
  40. dual-boot... ugh by Darmox · · Score: 2, Interesting

    The university that I work at(CS dept.) has every now and then talked about going to dual boot machines in the lab. I just can't think of anything worse. We actually had some dual-boot machines in TA offices, did not work well for the most part, because any support we had to do on them(patches and such) all had to be done right there.

    Plus, if they're machines that someone in the dept. can just reboot like that, you really can't enjoy the idea of allowing remote access at all to them.

    Every now and then someone thinks this is a brilliant idea for the lab, and I have to come back and explain that there is *no reasonable way* to keep a beast like that up to date.

    Okay, done ranting

    --
    If I was that drunk, I would have remembered it -- H. Simpson
  41. Re:Policies work fine by mpe · · Score: 2

    Policy editor in NT4/9x and Policies in a Win2k environment lock down systems about as tight as you want. But no one at slashdot has ever read the Windows documentation,

    Probably because getting decent documentation out of Redmond is difficult and expensive.

  42. Re:Um, windows isn't any harder to lock down... by mpe · · Score: 2

    What, were these guys dual-booting into windows98? Or were they just idiots who didn't know Windows NT (and 2000/XP) has a multi-user system that will allow 'locking down' just as much as anything in Linux.

    In practice it is considerably more difficult to "lock down" Windows if you actually want to run applications on it. Because the vast majority of Windows applications are written with a single user, who can do anything they like, approach.

  43. As a former lab tech... Re:Hehehehe... by Eneff · · Score: 5, Interesting

    I worked as a tech at a local high school for a year.

    I can tell you that the lab tech who obsesses over Quake is going to lose. You've got 0 budget and the products to secure the network are chosen by unqualified people who got the job of head of IT in the district because in 1985 they were teaching second grade and happened to tinker with an Apple II at home...

    The smart ones just secure against the stupid people and look for the smarter ones and bargain with them that you'll let them play quake if they keep out of the pr0n and viruses, and they kind of keep their eye out for stupid people trying to ruin it all for them.

    BTW, Rarely are the colleges any better. They have better heads of departments, but their main workers are CS students without the motivation to find a higher paying job in industry. (I generalize, of course, but I haven't seen many exceptions.)
    _____

    (OBTopic: nice win for Linux. I always thought that Linux might make a superior corporate solution for precisely these reasons. In a non-development environment, only a system administrator should be able to install an applicaition, for example.

    However, I know that Apple tried to play both sides of the fence as well, and they never had much success breaking into the desktop side of Multinationalica.)

    1. Re:As a former lab tech... Re:Hehehehe... by Sj0 · · Score: 2

      We've got slightly different circumstances, I think. I too worked in a high school IT dept. for a year, but here's what I found; First off, it wasn't a high school IT dept. The three techs, including myself, were the admins for over 10 schools, with several large high schools with multiple labs. The techs in that lab were good at what they did -- if they weren't, they wouldn't be working in such a demanding job. They work 12 months a year(compare to maybe 10 months tops for teachers) at full-tilt, and when something went down, it needed to be up -- NOW. We're talking about dozens of servers, WAN connections into, out of, and within this area whose bandwidth was good enough to run video conferencing over while still allowing(already large amounts of) regular traffic to run, thousands of workstations... Needless to say, it wasn't exactly a walk in the part ensuring that both the school administrators(ie. principals and secrataries, not computer Administrators) and the thousands of students all were running fine.

      One year, they tried to lock everything down tighter than a drum. It all worked, but the security came at a huge cost in terms of flexibility and ease of use, so we were forced to take a different approach. This year, we've placed draconian terms of use onto the students (from the 'legislative' side, not the technical side) so they can't go installing kazaa and banzai buddy on their machines. I was against it when I was a student, but on the other side, it's obvious that the single greatest problem with most of the machines that came in was the fact that they were so crap-laden that nobody could use them, so we're forced to ensure that we could punish people who abused our network. During our summer software rollout, we took special steps to remove all students software from the machines.

      By the way, you haven't lived until you've tried to roll out over 10 schools in one month(the other month was dedicated to infastructure, inventory, and server stuff). Especially when A)you have to rewrite the installer because the IEAK installer is so flaky, B)you have to patch every computer in the board because of a bug in IE6 with the IEAK(those who know which one will grimmace with me), C)The Wan connections are going up and down like yoyos because of work being done to them, and D)some of the software on the list needs to be tricked into running as a regular user.

      --
      It's been a long time.
    2. Re:As a former lab tech... Re:Hehehehe... by kraksmoka · · Score: 2

      note, i spoke of college admins. the school district folks ive met usually have it rough, like u do. i have the utmost respect for those types of challenges. uniTards on the other hand dont know the difference between their a$$hole and their earholes.

      --
      "You never want a serious crisis to go to waste." - Rahm Emanuel
  44. Ob. Simpson's (mis)Quote by Mignon · · Score: 2

    Warning: disparaging the dual-boot is a bootable offense.

  45. University of Warwick by Shade,+The · · Score: 2

    The University of Warwick here in England runs mainly Windows NT, with some Unix workareas dotted about, but the Computer Science building runs only Linux (Redhat) and Solaris. There's quite a lot of work done in the Computer Science course here that needs a fairly good working knowledge of Linux. Which is a pretty good thing, IMHO :)

  46. Re:lol by 0x0d0a · · Score: 2

    Back when I was in HS, the school bought some (disgustingly pricy) IBM boxes running Surepath that didn't have a hardware password reset (or at least IBM claimed that you couldn't).

  47. Re: Windows Policy Editor - could it be any worse? by E-Rock · · Score: 2

    It's amazing how difficult something can be when you do it wrong. Try loading the MMC, then add local policies, no regedit needed. After it's locked to the Nth degree, load the same tool from a remote box and connect to your secured machine.