Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment Hey wait a second y'all! (Score 1) 161

"Windows" was Orange Book C2 Rated in the 90s on WindowsNT v3.5SP3 on 3 certain Compaq Hardware Specs, with no CD Drive, Floppy Drive, no modem and no network connection. How much different could it be now. We have been told Windows 7 is the MOST SECURE Windows yet... so its gotta be better now than in the 90s. Right? The saying "Remember Ed Curry!" keeps popping up in my head for some reason.

Comment Re:What an over sensationalist title (Score 1, Informative) 899

Stop complaining. Vote with your feet, and take your business elsewhere.

Where? All the Big Box electronics stores where the average consumer buys things are all this way. Oh you mean the specialty shops only available on the Internet... Oh you mean Dell. Ohhh... right, try and find it on a powerful machine or laptop... Oh back to those Specialty shops on the Internet. Oh, Lenovo... try and order it from the website. Oh back to those Specialty shops on the Internet. Dude, you are batting pretty badly.

Comment Welcome to Debian SID (unstable) (Score 1) 246

I've been using Debian Sid for years, on all of my servers that aren't under contract.

I've also been using it on my desktops since *forever*

I've been using it on my laptops since about 2004.

I've had a total of a couple of hours of limited functionality, between my laptops and desktops. X barfs or my primary Desktop (Gnome or KDE) gets horked for a bit. I move to XFCE or andother Window Manager.

Servers have been rock solid except for a short time when the whole udev/hald/something changed its rules on how my NICs were named... no longer were they eth0/1/2 but eth4/5/6... Hurrah. Debian Sid is going mainstream.

Comment Re:Serious first post (Score 1) 230

Did you read TFA?

They said that the level of bugs per 1000 lines is very much less than half the "normal" amount. Though yes more than the Linux kernel itself, but some of the bugs were already addressed before release. I'd like to see *YOU* do better with getting the OS on a Mobil Device.

I mean, come on, exactly how is a remote exploit (quite a few of the bugs are this type) going to happen on these phones when these things don't even listen on what is typically expected on the "network" and then even if it does, its typically been "rooted" (and they should get all they have coming to them if they don't know why they rooted and expect it to behave just like a non-rooted one) and even then... at least on Verizon doesn't allow any connection listening services on its "mobile" ip address ranges in any case.


How about Apple let Coverity do the same run down on iOS? Never happen, at least with public results.
Better yet, Windows Phone 7? Hah... never happen period.
Nokia's stuff? better chance of winning the Mega Lottery.

Comment Release it. This is old hat. (Score 2, Interesting) 600

I'm sorry, but running userland "daemons" is child's play. This has been around for EONs. Please don't think you have something new here.

You problem here is that, you idea will only affect the *USER* environment, not the machine. Anything you run or install into the user environment will be bound by the standard user accounts everyone should be running as, without privileges (such as root/super user)

This separate the privileges from the user and the system quite well and delineates it.

Lets compare Windows and *NIX (in general):

Windows, I can send you and e-mail and you standard user just looks at my e-mail and via ActiveX can leverage a 10 year old exploit to install a service as a *SYSTEM ACCOUNT*. This means my process then has full access to the system... Possibly being able to wipe out the machine period, or use it for a launching pad to send out e-mails to other accounts on the system or other account in any address book or just grab your passwords (probably being abcd1234 or password or or what have you (Think Sarah Palin's Yahoo account... wooo really good password there)) for your Bank account. Its very much *THAT* simple, no stupidity involved.

Now, if for some reason ActiveX is disabled, I can just tell you how important the Microsoft update is and it needs to be run... and how you *MUST* forward it to your friends so they can be safe... Sheeple are gullible and will never be safe from this stupidity.

Now speaking of stupidity, its really the only way Linux/*NIX/*BSDs will be compromised... even then most likely only the *user's* data will be flogged. Not the whole system. Now, let us just say *I* download and run your program/update/shell/python script/perl script/etc... Sure it downloads and installs the BOINC daemon and runs in the background... to be honest who cares. Any program you run or have running to capture data from the user will only affect the *USER* not the whole system. Separation of privileges is pure and simple why the *NIX systems will not seriously fall prey to these kinds of things. And to be honest, unless you install a persistent AT job for the BOINC daemon to start or at the very least a cronjob that runs every minute... a reboot will kill your pitiful attempt.

Slashdot Top Deals

Digital circuits are made from analog parts. -- Don Vonada

Working...