Discussion Locked

The Gauntlet (What's missing in windows?)

0 helpful
320 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is page 3 of the discussion. Read the opening post

320 replies

by jmgarvin

1) I agree with your assessment of the registry. I was being overly general and I didn't want to leave out the older OSs. SAM is pretty good, but it is too easy to get to and steal. I wish MS would also work on the predictable hashing (did they fix this in Win2k3?) for passwords.

2) The registry is VERY cryptic, esp with 3rd party apps. Various keys don't quite describe what they do or what they are for. I also had AD not turn on all the AD keys, so I had to go manually find all the AD keys and update them.

I also agree with the protection against idiots, but I also think the registry should be able to defend itself against simple things like writing raw data into it.

I had an unrecoverable registry when I was poking around in Windows looking for something to do with AD or Kerberos...I managed to munge something up and that was that. It propogated to the temp backups on the system and it was a nightmare...I'm not saying it happens often, but it can happen.

3) Ya...Shared DLL/COM are what I'm talking about. However, Windows does shared libs in such a wonky way, it is hard to code securely. The APIs aren't always documented very well and sometimes you can get into places you didn't mean to go.

IMHO people tend to use COM because it is documented pretty well and is VERY common across the platforms.

What do you use in place of COM? I'm curious because I hate COM with a passion!

by ungle

1. I assume you're refering to LM hashes (which were particularly weak)? These are generated if the password is less than 15 characters and stored in AD...unless you turn this off...which is a valid point people have been making, windows security is often left wide open.

You can turn it of by (you're going to love this) editing the registry. Here's a link: http://support.microsoft.com/default.aspx?scid=kb;en-us;299656&sd=tech

2. Agree on the 3rd party apps. It drives me NUTS. I have spent YEARS (Literally) trying to teach developers where and how to store stuff in the reg. On that count, I guess it is cryptic. I blame THAT on MS for nto educating a developer properly during thier MCSD!

To help recover from these errors I recommend getting a copy of WinPE. It's a cut down version of windows you can boot to on a CD. From there you can load the hives on your system and correct the problems.

3. OK, I conceed this point. :-) It is hard to code securely. Another education campaign I've been on. I'm suprised about your comment re APIs though, I've always been pretty happy with MS documentation on that one. Can you think of an example?

I remember when I first started on Java, I hated the online docs. After a while, though, I discovered they weren't bad...just very different to what I was used to.

Agreed the final comment on COM. It is easy to use. I often create COM objects for people to use in scripts...because that's the only lib you can access from script (I'm going to duck here from the return swing :-) )

Rather than COM? Develop in C++ and you'll find COM is PAINFULL to use. Just use a standard C/C++ lib and link the headers into your main app.

Then, you drop the DLLs into the same dir as the app, and you app uses them exclusively.

In your app you can decide if you want to use shared libraries or specific libraries. Declare the full path to the lib within your app (it can be relative) and you will always use that lib. Specify only the name of the lib itself and the DLL loader first looks in the app directory, then system folder, then the rest of the path. You can control this behaviour through manifests (you can put your libs into assemblies)

Does this help?

by maldain

Except the basic architecture of both Unix and Linux limit the amount of damage a hack can go with the exception of the root user. Anybody who allows remote login to root is asking for trouble even if you need to use root for management you can always switch user to root while already logged in.

by maldain

There are a number of programs like that or that can be configured like shadow copy. sync would be one which lets you synchronize somebody's home directory capturing changes to the files there on a timed frequency that you set up. It works quite well. I use it to keep our warehouse inventories safe and secure from those stupid user tricks. I use a simple sftp to pull down grap back up data from our stores on a nightly basis. Both do exactly what I need them to do.

by ungle

and I have done so. During a recent headoffice move I was involved in I built 70 machines in under an hour.

It's really just a matter of understanding and using the tools at hand.

by ungle

I'll say it again: I worked for a number of years ensuring that applications did not require users to have admin access to any area of the machine, and was only beaten by one - which we then did not allow in our environment.

I was also heavily involved in a big drive for "application isolation" meaning that applications did not need shared dlls. We chose to allow it occasionally, it it is NOT required. This was, of course, in the post XP/2k3 world. Seems we're headed back to where we started??

Yes, the escallation bug is common. It would be my number one complaint with MS. They need some code auditors.

I don't know of any area of Windows that "forces" developers to do stupid things...they can handle that all by themselves!! :-) I could be corrected on this, though...Examples?

by jaqui

get an nt box to access an ext2fs partion on the same hard drive.
or a reiserfs, or ext3fs, or any of the other *x filesystems.

on the same physical drive as the ntfs nt system.
no network connection.
not shared resource connection
straight disk access.
if it can't, then nt doesn't have the ability to access other filesystems.

all *x systems will read ms filesystems on any drive physically attached to the machine.

by jaqui

I'm saying that windows uses the hardware as if it's one ring, not the 4 it should be.

the way windows itself tries to fix thier corruption of the hardware design isn't relevant.

by jaqui

be a battle for them to do so.
since most linux users have open source, free software that offers the same functionality, any linux based novell customers will most likely come from established customer base or people new to both linux and novell.

by jaqui

linux missing?
I use linux for everything, and have yet to find anything missing in it's capabilities.

by apotheon

There's a reason that privilege escalation is such a common bug, beyond simply a need for code auditing. The reason is, simply put, that it's difficult to write code that doesn't allow privilege escalation on a Windows system.

Much of the functionality written into the Windows environment bypasses user-level security and, as I've seen jmgarvin put it, "smudges" the line between user space and other supposedly separate operational spaces. When that happens, development of new privilege escalation exploits approaches triviality.

by apotheon

I know some of this has already been mentioned, and for all I know it might all have been mentioned already in this discussion. I'll list 'em anyway.

1. strict privilege separation

2. strict operational space separation (user/admin/executive/kernel)

3. configuration separation (Do the words "corrupted registry" mean anything to you?)

4. built-in enterprise-class firewalling capability (iptables vs. "Windows Firewall")

5. SELinux

6. avoidance of intrasystem RPC abuse

7. services independence (nothing necessarily loaded that you don't want)

8. rapid patch development (thank the fact it's open source for that)

9. no vertically integrated "hostageware" problem

10. heterogenous systems compatibility

11. platform portability Windows can only dream of

12. supercomputers

13. a cool mascot

14. LUGs and other incredibly good community support options

15. admirable security record

16. legal free copying and distributing

17. completely customizable GUI environment

I forgot about five or six while I was coming up with those. Maybe I'll come back to add to this if I remember them later.

by jmgarvin

Without going into tons of detail, DirectX is one big stupid programmer trick.

The idead is to make you code secure, but you have to fight like a dog to even figure out where things are going sometimes...While DirectX is a god send in many ways, it also helps to kludge up the some of the kludgy APIs and "system calls" that you have to make.

A prime example is when you need video card memory access, it gets pretty ugly esp if you need DirectX or need to isolate specific memory for simulation data...gah!

by jmgarvin

1) Thanks...I had no idea.

2) I was under the impression that WinPE was slow (or at least took a long time to boot). I think I'll check it out for myself though...

3) One of the buggaboos I ran into was thin documentation when it came to lower level APIs. While they explain what it does, they don't really get down to the nitty gritty. Some are VERY well documented. Hmmm...Threading comes to mind with poor documention. IIRC it was something with creating multiple user threads somewhat dynamically.

4) *Swing* Ya, I wish that MS would finally kill off COM stuff and move to something a little more strict like the C++ libs.

Thanks for the ideas with the DLLs and "soft" linking them into my app...that will help when building for multiple platforms that may or may not have the same directory structure...ug!

hmmmm...You aren't so bad after all ;-)

by apotheon

In GUI applications, generally, Ctrl-C copies, Ctrl-X cuts, and Ctrl-V pastes, just like in Windows. Just don't use Ctrl-C to try to copy at the command line: that'll close a CLI application.

The reason such functionality exists in Linux GUI environments is, of course, that Linux developers decided to accomodate Windows users trying to migrate to Linux.

by apotheon

Windows handling of threading is sorta faux, anyway, jmgarvin. It's difficult to make threading easy to code when the OS doesn't implement it worth a damn (and, depending on your definitions, doesn't implement it [b]at all[/b]).

by ungle

I'll take that as a compliment!

2) WinPE is PAINFULLY slow to boot...once it's up and running screen refreshes are slow - it uses a generic driver. Move a window around you'll see the CPU usage go through the roof! But it'll help getting a dead machine up again.

3) Comment on docs - yeah, I've never looked at the MS documentation on threading. When I started threading way back...:-)...I had a couple of top notch developers scare the living daylights out of me in regards of thread synchronization...so I invested mega bucks on a couple of good books on threading. You may be right. I'll look at it.

4) They are. It's called .NET :-) Take a look at the WinSxS stuff - they are slowly trying to wean people off shared libraries.

Despite some people's complaints, I've found .NET excellent to work with...it's strictly type cast, and since it's running managed...no more buffer overruns. Of course it was another MS theft. I learnt the most about c# while doing a Java course! There is of course .NET runtimes for Linux (http://www.mono-project.com/Main_Page) which means you could develop your c# projects on a linux box using SharpDevelop (http://www.icsharpcode.net/OpenSource/SD/) - it's all written in c#

by keyguy13

Don't compare apples to oranges.

Vi is an editor and it kicks Notepad's (and notepad is the only fair comparison) ass.

Openoffice works almost as well as word 2003 and yet costs nothing.

Go figure...

by keyguy13

Since you don't even know how to spell the OS that you are claiming is inferior to UNIX, you don't really have much credibility...

by keyguy13

No, Linux nor Unix do NOT have the same amount of security vulnerabilities. The difficulty of scripting hacks is due to less vulnerabilities...

And while Windows networks tend to get hacked more because of their popularity, they also get hacked because they are less secure.

It's stupid comments like yours that keep people from going with Linux or Unix. Some people actually believe you and therefore we all lose, because windows IS much less secure than Linux/Unix. Period.

by keyguy13

Yes it's true that the dumba$$ malware writers write their code for the prevalent OS. However, they also do it because it's easy. It is NOT easy to write malware for Linux/Unix because Linux/Unix is more secure. And A LOT more secure.

A more appropriate analogy would be that more theives break into a house that has a security system they know and is easy to defeat, than a house that they don't know and actually has a good security system.

I don't care what you M$ lovers want to say out of ignorance, Linux/Unix is WAY more secure than windows.

by lord deonast

I work for an Australian government agency. Money doesn't matter to them. Well to put it bluntly saving tax payers money doesn't matter.

Our federal government has an allocation system, if a department doesn't spent all the budget, they get less allocated the next year. Result, they don't want to save money, they want to spend it. In this environment TCO doesn't count. I once saved them $40 000 AUD on a project (back when I hadn't realised this), I expected praise only to find they were unhappy as they had to find a way to spend the money.

TCO matters to business, unfortunately to some government departments the converse is true.

by too old for it

I worked for a guy right around Y2K that used vi for everything ... word processor, development environment, web page editor .. might have used it to edit spreadsheets too for all I know.

Refused to buy Dreamweaver to replace vi for the web development staff because "why would anyone want to do that?" They are out there, and generally in management.

by black-eyed pea

I too work for a government agency. I agree that money may not matter for some government agencies or their decision makers. That is why I wrote that what matters in *business* is money. What is supposed to matter to a government is protecting a countries interests, assets, and people. What also seems to matter in my government is communicating and using a common platform - even to the detriment of security and common sense.

Consequently, there is a move in my agency to centralize IT operations, streamline communication, and use Microsoft products as much as possible. This includes the largest ever implementation of Active Directory. I do not know whether or not that rollout was because no other vendor could effectively accomplish such a common directory service for so many objects. The fact is that they did and it actually works well - much to my surprise. (I had to include the last bit lest someone accuse me of steering away from the topic of this discussion board.)

by roger

I have a serious response to your question! I believe your question was what can't you do with the ??? operating system? My response is that I can not run a web server, FTP server and web browser on Microsoft Windows XP SP2 at the same time due to speed issues. Also, I can not install applications on my Windows XP SP2 without requiring restarts for the machine to function correctly. However, I have a RedHat Linux 9 system running as a web server, ftp server, web browser, game server, instant messenger server, email server, (Can I think of anything else?) and it's still way faster than my Microsoft system. By the way, the Linux machine is 900Mhz and the Windows machine is 1.2Ghz. I am having difficulties getting linux to correctly initialize the GUI so I don't do the majority of my web browsing with Linux. However, lynx was very useful in searching for a solution when my Windows system mysteriously crashed after I tried to speed it up. My Linux system has been running for 11 days and 20 hours, my Windows system has been running for less than 24 hours. Tbe only reason my Linux box has not been functioning longer is that my UPS died, and took the power down with it! Unfortunately the reliability of the OS is not the only thing one needs to consider when looking at how to keep a system running reliably.

by chriske911

the site I work for at the moment still runs on Novell 4.x
they are desperately trying to get away from Novell
however for the sake of their main application running on DBAdvantage they still need the novell client

I've used NDS and I have to say it is not only very costly in terms of licensing but also too damn confusing, the options and tabpages in the user administration console never seem to end

and the novell client has in my experience always been the brake on network speed experience
everything comes to a crawl the minute it gets installed on a workstation
also the deployment of all kind of innovations get hold back, eg a biometric authentication

grtz

by tony hopkinson

I'm a real software engineer.
Windows is like any aging un-refactored un-reengineered piece of software. Never had anything to do with engineering crieria for a long time, business criteria, well lots.

Taking a wild stab in the dark I'd say every competent software engineer who looks at the source must have to be physically restrained from fixing it, take at least six bean counters to hold the guy down.

by tony hopkinson

remembering 'abtruse' commands multiple switches and redirection operators is not what Microsoft are selling, if you want a compound task you pay for an application.
VBS doesn't even come close to a scripting environment as a 'nix or even a VMS head would define it.

by tony hopkinson

F'ing horrible isn't it. The annoying is like javascript if they were interested in it being real application scripting language they could fix it very easily, it's not as if it's new tech or anything. You know what they were after when one of your less technical colleagues approaches you with a small problem with his multiuser business wide ... admininstration application with it's powerful access database, that isn't performing up to spec in the real world.

by bfilmfan

Although there are probably few of the younger engineers have ever even seen Banyan, those of us that used it find AD a nice upgrade to Street Talk.

by ungle

Apotheon, I assume you are refering to the Apartment threading model of the COM world? In which case, I agree with you in part. Fortunately COM does also support the free threading model. Your choice is determined (as an overview) on whether you require cross thread communication. Apartment threading incurs an enourmous overhead in this case.

Fortunately in the non COM Windows world threading is pretty standard and simple...laden with all the usual gotchas of thread synchronization.

Dare I say MS offers a choice??? OK, that's going too far :-)

by apotheon

keyguy13: I'd say, actually, that OpenOffice.org is better in many ways than MS Office, even aside from price. It's also not quite as good in some areas. It's a trade-off that needs to be examined before choosing one or the other on technical merits.

Too Old For IT: That guy sounds like a problem child, and judging vi based on his example is not a smart approach. I use vi as a code editor, text editor, text processor, system configuration tool, and email editor. I also use OpenOffice.org, Thunderbird, Webmin (for CUPS), SciTE, and a slew of other things that overlap. I find vi to be much more effective for those tasks for which it is fully functional than anything else I've used for those tasks, but it's not the panacea for all conditions at all times.

If the vi user to whom you refer refused to let others use tools that would make them more productive, that's a problem with him, not with vi.

by apotheon

It's possible I'm slightly out of touch with that subject in the Windows world. I haven't paid too much recent attention to how threading is handled on the Windows platform for the last couple years or so. In fact, for the last year I haven't touched any application development or administration scripting on (non-PocketPC) Windows at all, threading or no. I'll have to check into that.

by philchil

I definitely have to agree with you. I've managed several thousand shops with NDS and it works wonderfully, securely, and easily, if you are proficient in what you do. It all boils down to the learning curve. All the OS's have different aspects that are both good and bad. It's up to us, as the implementers, to maximize the good, limit the bad. Do the job right, do it well, and don't get sloppy just because, lets say, Windows 98 is too hard for you to understand, or you think a tree is what fruit is grown on.

by jmgarvin

I can check my mail, read newsgroups, program in multiple windows, have perty colors, AND talk to a psychologist!

by apotheon

Every application gains functionality and features until it eventually incorporates the capabilities of an email client, at which point it becomes obsolete. It's some kind of a law of computing, like Moore's Law (processing speed doubles every 18 months) or Parkinson's Law (data will grow to fill available storage), but I'm having a little trouble tracking it down online right now.

by lord deonast

Yes Licensing can be costly, but then you get what you pay for. You say you are still running 4.1x, you won't be getting much value, that is an old platform, Think winNT equivalence. You say no biometric, well newer versions of edirectory (what the new NDS is called) support this, you just need to move forward.

You can't complain about not getting value from a platform and new features when you stay with an ancient version. The same would apply if you were on WinNT and tried to achieve the same things.

Netware 4.1x isn't even supported anymore, so for your licensing you will get nothing, move forward and you will get a better value proposition.

by mark.paris

Microsoft does many things with many programs. Playing well together is not one of them. Witness their own service pack approach to fixing their own products. Case in point: when Win2k shipped, it shipped with over 25,000 known bugs (Microsoft's own admission, check it out). Four service packs and a "major revision" to W2003 later, it still needs rebooting twice a month in our 24-point network, more often in the larger 100+ point network.

In the world of communications, high-speed multitask switching, serious uptime (>99.9%), WinX stands alone: it cannot do any of it. Everything else can.

by jdclyde

If I have to go work on someone elses server, I KNOW that it will have vi.

If I have a server go down and is in a limp mode, I KNOW vi is on my boot disk.

What is the "best" tool isn't always what makes it the best tool. Being able to use it anytime, anyplace means more to me than if one has more features or not.

But that is just me.

by apotheon

That's why I initially decided to concentrate on vi more than emacs. Now, much later, I keep seeing reasons I'm glad I went with vi as my primary CLI text processor instead of emacs. One of these days, though, I should get around to being functional in emacs as well.

by apotheon

Just run a versioning system, like Subversion or CVS. Unlike in the Windows environment, it's a trivial task to turn a versioning system into an incremental compressed backup system allowing you to "roll back" data states to earlier versions, thus duplicating the functionality of tools like Shadow Copy.

There are also direct rip-offs of such tools available for DEs like KDE, and as stand-alones, but I'd really tend to prefer something using a versioning system because of the leaner operation of it, greater flexibility, greater orthogonality of functionality, and greater potential for use of one tool for many jobs.

by apotheon

Apparently, you're not familiar with Linux software management tools. You want to ensure that everything installed is also uninstalled? Try this:

# apt-get --purge remove [packagename]

Voila. Complete, clean uninstall.

The Windows way of doing things with the Registry instead of config files doesn't reduce code: it just reduces orthogonality. The windows way of doing things with OS hooks doesn't reduce code, either: it just reduces orthogonality as well, since Linux provides the same level of avoidance of redundancy through the use of non-OS-integrated libraries.

If you use a well-maintained distribution like Debian, you don't have to worry about dependency upgrades breaking things, and (unlike Windows) it's even possible to have multiple versions of the same dependency installed if you really, really have to have different versions of the same library or the same "subprogram" (to use your term) to support separate applications. You get the best of both worlds: redundancy if you want it, and not if you don't.

by ungle

apotheon...not to cause trouble...

All you describe is also available with Windows...multiple versions, clean uninstalls.

That said, you need to know how - and there in lies the difficulty.

The whole SxS thing was introduced to remove the dll hell problem you mentioned, and it was extremely effective. Now I can have shared libraries or "shared libraries" that aren't.

Windows installer is very effective at installing and uninstalling cleanly - but again, packages need to be built right.

by apotheon

You want LAMP that's easy to set up? Try RHEL, SuSE, or even Debian with Tasksel.

If you want something that looks exactly like Word 2003, you're probably going to have to get Word 2003. Then again, Word Vista (or whatever comes along with the Vista platform's release cycle) won't look exactly like Word 2003 either, so if that's your real set of criteria, you're at an evolutionary dead-end for office software.

If you want Y!M, MSN Messenger, AIM, and ICQ on your Linux box, [b]choose any major distro at all[/b]. Come on, now, don't tell me you didn't realize they'll all run Gaim, Centericq, and a slew of others. Do you really think only RH can do it? In fact, Gaim is a far better graphical IM client than any other I've used, including the native clients for any IM protocols, Trillian, and several others of which I'm sure you haven't heard.

by apotheon

It's a hell of a lot easier to type "apt-get --purge remove" than it is to do an interative search through the registry trying to memorize what changes in the registry when you install something, compare it with what changes when you install other stuff, and make changes to the registry to bring it back in line with what it would be if you'd never installed a given program but hadn't ever done anything else differently. In fact, it's pretty much humanly impossible. The same isn't true of clearing out Linux config files.

Yes, it's technically possible to do the same stuff in Windows, but I'm not about to do the Windows Registry equivalent of playing a grandmaster chess game entirely in my head. Nor are you, for that matter, especially since the chess grandmaster would fail at this task.

Major Linux distributions have centralized package configuration control and, even if such control fails and something slips through, it only affects that one program and disk space. It certainly doesn't affect your entire system in a manner that no human being is going to be able to fix, as Windows registry problems do. Worse yet, with the registry, if the data gets corrupted, you're screwed unless you have a backup of the entire registry [b]in its current configuration[/b] on-hand. God forbid you might have accidentally installed and/or uninstalled two or three things in the interim. Meanwhile, with Linux config files, unless your entire hard drive gets hosed up, you're unlikely to have to do more than fix some text in a single config file.

The real benefit of Linux over Windows for configuration is twofold:

1. It's orthogonal.

2. It's human-readable and human-editable with nothing more than a text editor.

Combine those two, and all problems become trivial to fix.

by jmgarvin

Pico seems to have enough functionality and nobody really loves or hates it...

The whole vi vs emacs thing is strange, but understandable...but NOBODY can get excited about pico ;-)

I should probably more proficient in vi (I can edit, save, open multiple windows, etc), but I'm not a speed demon like most vieeks are.

by jaqui

only reason vi is available is it's in the standards for lsb.

I'm trying to get them to change it to something that is modeless, like joe.

since this command mode to tell app what to do and edit mode to change files is from the stone age, and should be killed.

emacs isan't any better, an antiquated design that has seen it's heyday and needs to be put to rest with the other dinosaurs.

one of these years I'm going to go through the sources for building a system and rip out all sections that require vi(m) and change it to a better editor.
then I can have a system that doesn't require an app I'm never going to use.

by apotheon

How do you move around and perform complex editing tasks with a modeless text processor without ever having to leave the home row on the keyboard? The whole point of the mode style of control is to speed up the editing process by allowing one to perform certain operations very quickly, which requires as little deviation from the keyboard home row as possible.

Hmm. I've been thinking of looking into learning the Dvorak keyboard layout, and it suddenly occurs to me that this would mightily screw with my use of CLI applications like Vim.

by jaqui

they refuse to update vi(m)'s interface to keep with the home row of the keyboard?!?!?!

it still sucks.

I would rather use ms" notepad than vi(m) or emacs for text editing.

or the old dos edit.
far simpler usage than either of them

you don't need a million features in a text editor that is required so that you can edit configuration files.

editing to add:

besides, for some reason unkown to me I work best when using one hand only ( left ) and not even looking at the keyboard.
so an interface designed for 8 finger usage is completely at odds with my keybarding style.

by jaqui

proper filesystem ( partition included ) maintenance, by system developers says 6 months then rebuild partition structure and format.

any longer is asking for un-acceptable error levels.

by apotheon

I don't know what you're saying about updating vi. If you're referring to my comment about Dvorak keyboards, I'm just saying that I don't know whether the used for movement and other functionality would be the same letters or the same locations, and in either case the adjustment would screw with my head.

In any case, as I tried to convey, I'm a touch-typist home row kinda guy, and like vi's approach to that.

By the way, when you talk about all you need from a text editor for editing configuration files, you seem to be forgetting that vi is designed to do more than simply edit text files. It's not a text editor: it's a text processor. It's capable of everything a word processor can do, and then some, with the mere addition of a couple of things like tex for formatting, and it does it much faster and more efficiently for the experienced vi user. It's also fantastic for development, with parenthetical matching and context highlighting, scripting, macros, and so on, all without the sort of security issues endemic to office suites.

. . . and it's nowhere near as bloated as emacs, for all that.

by jmgarvin

Here it is...the total problem. I was teaching vi to a few students and they had trouble grasping the whole concept of running command line stuff in a text editor. It seems the "command" area of vi (to them) should only be for text processing and not for navigating the system and running commands there.

The other problem is that "modern" computers come with keys to the right of the enter key. This is pretty problematic in vi. Another point is navigation doesn't map to what they know, FPS games. HJKL does NOT map to WASD at all...so students have trouble rembering that L means RIGHT!

I joke about Emacs, but honestly, there are far better text processors than vi. It takes a LONG time to learn and many admins just aren't good with it. I think something like joe (as metioned) or at very worst pico/nano should replace vi ASAP.

by apotheon

If all you want is a text editor, use ed. If you want a text processor, that's where vi is strong.

I really don't know a whole lot about joe, pico/nano, and all the rest of that half-measure stuff. I'm sure it's great. On the other hand, vi is available everywhere, and I like it a darn sight better than emacs. For a CLI text processor, it works great.

by oz_media

It's obvious that MS had nothing to do with NDS, NDS works.

As for NT being a spawn of NW, MS would LIKE peple to believe that anyway. THys don't hold a candle to whet they have been competing with from Netware.

MS offers cool features and that's about it.

by jaqui

but vi isn't included because it's a text processor.
it's required for standards compliancy for it's use as a text editor for fixing config problems.

like using a 20lb sledge hammer to drive a finishing nail.

the lightweight editors are all that is needed for that purpose, yet the standards say that vi(m) is the editor to be used.

note, standards say editor, not processor.

why do the standards require overkill for the default editor of ttext files?
that's my issue with them.

I just don't think that any app that is running "moded" should be continued.
( includes emacs you know )
the modeless editors don't have the complexity of switching modes to move around the file, and edit it.
yet they don't all lack the abilities of vi(m)

emacs is more a complete user interface.. a cli windows. ;)
kludge after kludge with it.
try reading emacs tutorial in console.. carefull it will dis-appear on you and lock emacs up.
( happened to me 6 times. un-installed emacs. )

by apotheon

I'm pretty sure that vi is included for reasons of A) compatibility with the hundreds of applications that integrate with vi, and B) historical reasons of its ubiquity on unix systems, as well as C) the fact that it operates perfectly well as a mere text editor when it needs to but also allows for a helluva lot of power in the hands of someone that knows how to exploit it.

I don't disagree that something much leaner might be a better choice but, in a world where even Debian is including less in the "minimal" installation now, you're not going to see vi thrown over for something smaller. In fact, if you actually change anyone's mind about replacing vi with something else, they'll probably pick something more bloated at this point. If you want something smaller, you're going to have to simply assume LSB noncompliance.

"[i]I just don't think that any app that is running 'moded' should be continued.[/i]"
I disagree with that. There are things that vi(m) can do because of the modes it uses that it would not otherwise be able to accomplish with any efficiency. Please stop arguing for making it into abandonware just because you don't like the interface. A lot of other people do.

by Former member

From running other browsers. But most people didn't want to bother. what was already there was "good enough".

Yes, MS leveraged their OS dominance, and took unfair advantage of Netscape by subsidizing their browser. No one is suggesting that MS business practices are especially Moral.

But that has little to do with their ability to market their products to the public. How many people even know what Biztalk server does?

by Former member

Someone has found yet another flaw in a libray or app which can be exploited to gain root priv's on the machine.

So the effective level of security is the same.

by jmgarvin

Ok...give me 10 examples of app/lib exploits that can give me root.

They can't have been in the 2.4.20 or below kernel or the 2.6.9 or below kernel. They also can't be in apps that should have been patched many moons ago.

If you bring up the fork attack, I'm going to put a dunce cap on you and sit you in the corner.

by Former member

Interesting. It was my understanding that they were both separately derived implementations of X.500 standards (NDS adhered to the standards more closely than AD, but that is no real surprise.).

by apotheon

The problem isn't with not being able to use other browsers. Obviously, you can use Firefox or Opera if you really want to on a Windows system (and I would, if I really wanted to use a Windows system at all). Nothing prevents me from doing so. That's absolutely correct.

The problem is with not being able to avoid using IE. Internet Explorer is integrated tightly with the OS, and its rendering engine is ubiquitously used throughout the operating environment of Windows systems. There's no way to avoid it. You have no choice in the matter, as long as you're using Windows.

by Former member

In Linux it is a minor modification to a text file, and the account is blocked from logging in.

In Windows, well quite honestly, I am not sure what all needs to be changed. In the User Righrs assignements in policy (group or local), There are quite a number of entries to allow/disallow logon locally, via terminal services, etc. I realize it is ignorance on my part. But it would be nice if I could just hit a checkbox when creating the user account.

by Former member

The key with Sudo (as I recall, haven't used in awhile), is that you don't have to provide the user with a user/pass. with runas, you have to provide a user/pass, in order for the priveleve elevation to occur.

by Former member

Being able to grant elevated priveleges required for app installs is the main value I see. Certain progs (ACAD for instance) require the user to be Admin to install.

by Former member

That is really the big sticking point. Much as MS has annoyed me over the years. I still continue to use them the most. Why, cause it "just works".

It may not be as efficient in resource use, or as fundamentally secure, but The fact that 90% of the programs work - with no tweaking, patching, hunting for dependancies, or digging through obscure documentation to find the right arg to add to the cmdline or the cfg file - keeps me coming back.

by gary_griffith

What - with all these dual-core Opteron + 64-bit Windows OS options available, you can really make a fine server, but you're missing a mature resource manager (like HP-UX's PRM, AIX's WLM, or Solaris' SRM) to keep individual processes from taking the whole box. Get good PRM, and you can safely consolidate apps onto these potentially scalable machines. WSRM looks OK, but from Microsoft's presentations on the technology, it appears to be lacking. Is anybody out there using this?

by apotheon

It would be trivial to develop some third-party application for managing admin installs when signed in as a non-admin user. The problem, of course, is that in a Windows environment you'd have effectively created an exploit, because rather than having separate user operational spaces Windows just uses file and directory permissions coupled with weak privilege separation to fake it. This prevents proper assignment of operational space for admin operations vs. non-admin user operations, and thus prevents limited applications of single-action admin capability.

Rather than assigning limited capability from the system level, you're doing so from the application level, if you write a third-party app to manage admin permissions for one-shot installations. This means that the only thing preventing full admin access if you create and use such a third-party utility would be the utility itself, and not any characteristic of the mechanism for granting elevated permissions.

Now, granted, if you write your application to control that sort of thing, it will itself be fairly secure, but such a utility would essentially be a proof-of-concept for an endemic Windows security weakness.

The proper way to do it would be to separate user spaces and use strict privilege separation. Thus, you'd be able to both provide tightly controlled limited privilege escalation for allowed users, and you'd allow users the ability to install and run anything they like within their segregated user spaces in such a manner that they affect no other users' operational spaces. Since Windows only barely separates privileges and doesn't have any true operational space segregation at all, it's incapable of providing the same level of security when also providing the same level of flexibility to users.

I feel like I've mangled the phrasing of all this. I blame the late hour and the strange evening I've had. Suffice to say it involved a girl. Heh.

by jaqui

check out the last 4 issues of @risk from sans.org
there were 2 or 3 newly discovered root priveledge exploits in most of them, for linux, unix and bsd systems.

by ungle

apotheon,

You didn't mangle it, in fact you did a pretty good job of describing how Windows Installer works!

I was going to write an in depth description about how the whole thing works, but time...ya know!

Anyway, in regards to your comments...

Windows installer is actually a service that runs as system. Msiexec.exe, when run interactively, connects to the service and allows user interaction. The actual install is performed by the service, the windowed application you can see is just reporting on the service's activities. Thus MSI can offer privilege escallation securely, since the system space and user space are not compromised. Note that Windows INstaller is a part of the OS effectively...

There's a lot more to it, I'd be happy to expand on it if you're interested. There isn't much written on the topic, unfortunately.

NTW, if an application is certified under the Made For Windows logo program, the way to get a clean uninstall is similar to you r earlier description - msiexec.exe -x . Part of the logo program states that an installation must full uninstall itself.

by phoward

What I really like about linux is the flexible command line.

Lets me do things like synchronize directories on different computers by just typing.
rsync 192.168.1.100:/home/philh /putfileshere

Copy a file from a remote computer
scp 192.168.1.100:/home/philh/myfile file here

Piping and command redirection lets you chain together programs and commands
more textfile | cat anothertextfile

I really like having software written with security seperation in mind (Most Windows apps assume Administrative priveledges)

I like the speed of editing files directly from the command shell.

I like how easy it is to install software
yum install newsoftware

Most of these things could probably be done on Windows but not without significantly more effort, and probably additional cost.

by Former member

copy from a remote computer - copy \\host\share\file

piping and redirection work, you just don't have as many cool commands (I miss less)

Security separation... Not sure whether this really differentiates. You see the problem on both platforms, but it doesn't have to be on either. It's mostly lazy programming.

by jmgarvin

I usually get the SANS news letter, but I must have missed that one!

That just stinks. Is it just me or the the 2.6 kernel a little less secure?

by Former member

I'd much rather use a spoon!! ("It's dull you twit, It'll hurt more!") ;)

Just to clarify a bit. I am not saying the Linux is just as bad as windows where security is concerned. I am just saying windows is catching up really fast. Therefore I don't think security differences are a valid argument anymore. The most recent service packs have made great strides towards locking down unnecessary services, adding firewalling (more specifically app-aware firewalling), malicious code detection, etc.

by jcwuerfl

Managers if you are reading this beware sometimes you make decisions that are worth of dilbert comic strip and yes, we do send all of those into Scott Adams, and you wonder why they are sound so familiar... =)

Managers really need to listen more and stop making knee jerk decisions and going with something without doing the due dilligence it needs. so true..

by jmgarvin

Ya, I agree. Windows is making great strides to be secure, but they STILL mudge the user space and kernel space so that executing malicous code is too easy.

I hope Vista fixes many of the "typical" security issues we've seen so far...

by Member 22744991

After being in the industry for 10+ years, there has not been one OS that has not at one time or another (all for their own individual reasons) sucked! The likes of BSD, Windows, Redhat, AIX, Solaris, Netware, etc. . . I?m starting to think manually optimizing memory under DOS/Win 3.11 was really not that bad :-).

Mind you, I?m not complaining . . . It?s the developer?s faults that I have a semi-lucrative career, so all and all, I can?t be to bitter. Now, before some zealot gets on their soapbox and tried to ?deliver me to the light? by preaching their OS, save your time and don?t insult the intelligence of some people here. Lets face it, if any one OS' was all that great, we would not have some many different companies working so hard to grab our IT dollars.

I?ve seen the FUD, the embellishments, the fabrications, and just the plain outright lies that so many developers have stepped up with, and well, my personal feel is that many of them need to be shut down for false advertisement. Keeping me employed due to complex system and integration problems is one thing, but for some of these vendors to release the sheer crap they do, well, they need to have their fingers lopped off.

??by following the paths of lies and deceit, and one can not help but to discover truth and honesty?.?

by johnaaaaaa16

You are absolutely right. MS had produced a fine OS that just about everyone can use and enjoy. Of course, this factors into larger decisions but this gets factored into the TCO calcs - after all, fewer users needing to be trained on the US equate to lower training costs and lower TCO.

by parier

I'm still happy with my C64...I keep hearing of these IMB's, or IBM compatibles coming out soon....Im tired of hearing that, when are they coming out, and what are they compatible with, the microwave?

C64 Lova'

by nighthawk808

"I use both vi and emacs."

We should ask Laura DiDio which one she would use, then use the opposite. That should settle things once and for all.

by nighthawk808

...and it's not what you think. Knocking out 100k Windows machines isn't news precisely because it happens all the time. Knocking out 1k Linux boxen would be on Micro$oft's Get the FUD website faster than you can say Slammer. They would ship out 60" monitors to anyone who asked just so they could read the 512-point font headline. Laura DiDiot would laugh so hard that she'd have to wear Depends for a week just to keep her pants dry. A major--hell, even a minor--Linux-based worm would be big news precisely because it doesn't happen every single day. That old, peabrained argument about Linux being safe because of its market share is plain, unadulterated BS: it would be on every single news program in the world if Google went down because of a worm. And they have thousands of computers running what? Yes, that's right: Linux.

All of this hasn't happened and won't happen any time soon because of the different structure of the two operating systems. Comparing the security of Windows and Linux is like comparing bleu cheese and a Ferrari.

by nighthawk808

I think the closest you'll get to beating that is the line "That's a feature, not a bug*. Rebooting is good. Resistance is futile." There's a reason that Windows has no simple equivalent to Linux's "uptime" command out of the box. If you want to coax the uptime out one of them, you have to sort through a bunch of system info junk or download an extra program. In Linux, you simply type "uptime" and you get something like, "8:42 a.m. up 154 days 11:07, 3 users, load average: blah blah blah".

It's one of life's little ironies that Linux, which rarely needs to be rebooted, has at least three ways to do it from a CLI: "reboot", "shutdown -r now", or "init 6". If you want to reboot Windows (like, for example, if you just edited a letter to Grandma in Notepad, played a game of Solitaire, or some similar heavy-duty work that requires a reboot) you have to type "shutdown -r -t 00".

*"It's a feature, not a bug" is a registered trademark of the Microsoft Corporation.

by apotheon

Actually, the three-finger salute works on both Windows and (at least from a tty) Linux, too. Of course, that's not really issuing a command so much as unceremoniously killing all processes. Then, of course, there's the GUI option, for which there's one choice in Windows (the Start button) and any number of choices under Linux, depending on which GUI environment you have decided to use.

There's so much functionality lacking in Windows that I usually don't even know where to begin when asked to compare and contrast the two.

by halibut

I have been a windows admin for a number of years now and do like the OS. But some issues I find with the OS that Linux does not have for the most part has to be the command line functionality.

Windows focuses way too much on the GUI side of the OS having to have a good portion of their tools GUI only based. Whereas Linux usually has the opposite, CLI based tools first and then someone wraps a GUI frontend to it for the less experienced Admins.

So many "IT professionals" I have heard from speak how unstable windows is and how stable Linux is in comparison. But I have found that any OS that runs a GUI is exponentially more unstable than one running a CLI only. Linux or windows or Mac, it doesn't make any difference.

With that being said, all the OS's have improved substantially in the past couple years but I still find this fact is still true.

by lonnie

Pretty much what happens when you unplug a thin client on any network.
Haven't noticed a Linux or Windows box crash when I pull their network cable, and I don't recall any of the computers on the last Novell network I worked on crashing if the network cable was pulled.
At least TRY to make sense in your responses.

by 3kl

The danger and insecurity is largely in the admin. The vast majority of system hacks (windows or otherwise) come due to lack of patching and securing a system. Windows 2003 is "more secure" than Windows 2000 largely because M$ turned more features off by default. A poorly configured *nix system is at risk as is any OS that isn't locked down. I won't disagree with anyone that feels Bill Gates could be compared to the spawn of satan at times, but I'll take my locked down M$ systems over the old *nix systems that got hacked due to lack of proper securing by their sys admins. (and yes, I am speaking from personal experience on that one.)

by apotheon

You seem to be unaware of the significant, fundamental system architecture flaws in Windows that decrease its security viability. For instance, weak privilege separation (an improvement over earlier Windows versions' "no privilege separation") is a terrible problem with Windows security: sure, you might make it difficult for someone to break in using a firewall, but once they're in, it's a relatively trivial thing to achieve privilege escalation and own the box in very short order. Another issue: RPCs are a security risk (any service is a security risk), and it's true that basically every modern system runs RPCs no matter what OS, but if you want to see how pervasive RPC use is on a Windows system, how widely it spreads its vulnerabilities, and tightly integrated those vulnerabilities are with core OS functions, try turning 'em off. You'll suddenly find that without RPCs you can't even log in to the system.

These are only a couple out of thousands of individual problems in the way the Windows line of OSes have been designed from the ground up.

by jmgarvin

This is, in essence, a portal to the kernel. Why should the user have such privelged access to such a sensative part of the OS?

Also, why do all the users "share" the same registry? It just doesn't make sense!!

by apotheon

GUIs tend to be unstable. That's true. It largely has to do with sloppy coding and the increased likelihood of bugs in increasingly complex code.

Luckily for Linux users, if the GUI crashes, you still have a running, fully functional OS. On a Windows machine, if the GUI crashes, you're hosed.

by ungle

Sorry, you have missed the point of the registry. It's not one big repositry, it's just represented that way.

The user has free access to HKEY_CURRENT_USER (which is the ntuser.dat inside the user's profile). This contains user specific settings, kind of like a user accessible config file in linux.

The critical machine settings are under HKEY_LOCAL_MACHINE\System, and in it's correct config the user does not have access - and it's contained in a separate file in an area not accessible to the user. If users have access here, fire your admin.

The main reason people object to the registry is lack of understanding - again it's represented as one big repository for simplicity. My biggest complaint is not so much the concept of the registry, but rather the way it is used by application developers who simply don't know enough about Windows!

by jmgarvin

Ok fine:

HKEY_CURRENT_USER - Contains info on the current user

HKEY_USERS - Contains info on the actively loaded user profiles on the computer. HKEY_CURRENT_USER is a subkey of HKEY_USERS.

HKEY_LOCAL_MACHINE - Contains configuration information particular to the computer (for any user).

HKEY_CLASSES_ROOT- Is a subkey of HKEY_LOCAL_MACHINE\Software. The information stored here makes sure that the correct program opens when you open a file by using Windows Explorer. Starting with Windows 2000, this information is stored under both the HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER keys. The HKEY_LOCAL_MACHINE\Software\Classes key contains default settings that can apply to all users on the local computer. The HKEY_CURRENT_USER\Software\Classes key contains settings that override the default settings and apply only to the interactive user. The

HKEY_CLASSES_ROOT key provides a view of the registry that merges the information from these two sources. HKEY_CLASSES_ROOT also provides this merged view for programs designed for earlier versions of Windows. To change the settings for the interactive user, changes must be made under HKEY_CURRENT_USER\Software\Classes instead of under HKEY_CLASSES_ROOT. To change the default settings, changes must be made under

HKEY_LOCAL_MACHINE\Software\Classes. If you write keys to a key under HKEY_CLASSES_ROOT, the system stores the information under

HKEY_LOCAL_MACHINE\Software\Classes. If you write values to a key under HKEY_CLASSES_ROOT, and the key already exists under

HKEY_CURRENT_USER\Software\Classes, the system will store the information there instead of under
HKEY_LOCAL_MACHINE\Software\Classes.

HKEY_CURRENT_CONFIG Contains information about the hardware profile that is used by the local computer at system startup.

So you are trying to haze me. You skipped out on HKEY_CLASSES_ROOT, which as defined BY MICROSOFT can effect ALL USERS on the local machine.

Yes, some of us DO know what we are talking about and won't be hazed by your overly general BS.

It isn't a lack of understanding it is a FACT OF HOW THE REGISTRY WORKS. Don't try to BS that the registry is pure as the driven snow and can only be accessed by 'privileged' users. If that was the case malware wouldn't exist in Windows world.

Windows does not properly separate user and kernel space (or user and user space for that matter). It has issues that are FAR deeper than the registry, but that is a good start.