Many countries/people around the world play violent video games and watch horror movies and manage not to kill anyone.
The prevelance of video games around the world makes drawing these sort of conclusions statistically meaningless. So many people play games it hard finding someone who hasn't, let alone someone who hasn't AND killed a bunch of people. You may as well say drinking coffee causes people to flip out.
The problem you refer to seems limited to America. Watch "Bowling for Columbine" for an interesting point of view on this.
Novell's strengths are no longer in the Network Operating System space, which is what made them. Nowdays their focus is on getting your network to act as one, regardless of the underlying operatings system or applications.
Take a look at eDirectory, which is far superior to MS AD and runs on almost any OS. Identity Manager (formerly DirXML) can syncronise information across your enterprise.
Zenworks delivers applications/patches to your workstations, servers, laptops and handhelds based on who you are and what relationship you have with the company (employee, division, position, customer, business partner, etc). Furthermore, it does not care how you connect!
Adding linux to the mix gives existing Netware installations an alternative future and piggybacks off OSS - smart move. For some interesting reading have a look at Open Enterprise Server - all your favorite Novell utilities on a linux platform. I for one will be making use of this....
Maybe a directory would be better?
Most directories have optional values on objects and many do not store the attribute if there is no value (assuming you count nulls as not valuable).
It is then trivial to determine who has died based on ldap searches:
ldap:///o=org??sub?(died=true)
or
ldap:///o=org??sub?(objectClass=died) (assuming aux classes)
Nested groups are a good way to overcome the group management problem alluded to here.
Since AD does not allow OU's to be security principles (or anything apart from users, groups and computers), you cannot leverage the directory structure to assign rights.
Hence, you must create another heirarchy via nested groups that will largely reflect the existing directory structure in most organisations. This seems to be a doubling of effort to me, complicating management and imposing additional work loads on IT staff.
Yes, except that (in typical MS style) the ACL's are stamped onto EVERY folder and file.
Making changes to file system security consumes vast amounts of CPU and thrashes the HDD.
Plus, you can't assign secuity based on the AD structure (everyone is sales has read access to this directory). Only groups and users will do.
Microsoft file system security os only a little better than Linux. Both still are missing very granular rights - try revoking permissions to list, read, rename, delete, copy or execute individually on these platforms.
Security is just passwords
on
Real Security?
·
· Score: 2, Insightful
I hear people worry about security on a daily basis and what many of them fail to realise is that is essentially a problem of identity.
Security is the process by which you determine if somebody is allowed to see the information concerned - this hinges on who they are and what they are trying to access.
How to do proof you are who you say you are?
This is actually a very difficult question.
hat aside (for now), all security/identity is built around 3 things:
1) Something you know (usernames, passwords, etc)
2) Something you have (secureid cards, tokens, passes, etc)
3) Something you are (biometrics, fingerprints, retina scans, genetics, etc)
The first two are easily overcome with some creative thinking - read Kevin Mitnick's "The Art of Deception".
The third has the same problems the other two have - how do you establish identity to begin with?
Anyone can claim an identity, all you need is the documentation to "prove" it and these can be forged or obtained with little effort. So how can you ever really know who you are dealing with?
OMG !
The security groups first priority is to be "Microsoft's first and best customer", while the last is to "Run a world-class utility".
Shouldn't this be the other way around?
Here's an idea - why not use the best technology available?
If it is not yours - look, listen and learn.
You are confusing technology with the *use* of technology.
Sure, Flash has been abused and misused to display all sort of "cute" animations, but so has a lot of other technologies.
Good web designers understand the benefits Flash provides and use them properly. The rest use it as a means to make their site look good, without actually being good.
ISPs blocking outgoing SMTP will not solve the problem in itself.
Users would have to forward mail to the ISPs smart host for delivery, which should only accept mail from their own IP ranges, BUT it is still delivered.
The trick may be to add another layer - restrict the number fo emails from a single server over a specific time period. This puts a bottle neck on spammers and helps, but does not eliminate the problem.
The real problem is the immaturity of the internet as a technology. Each layer in thr OSI must authenticate to the layer below and be signed so we can be certain of the traffic received, accept upon and transmitted. Bring on IP6 for a start!
At least logs of email traffic can be obtained and serious offenders kicked & banned.
I agree spam is a social problem, but it is a global society we are dealing with, so we need global laws to deal with the problem.
I agree spammers annoy, harras and steal from us all, but legislation only acts as a deterent, not a remedy. People still steal, cheat, lie, kill, etc even when we have laws that prohibit these behaviours. You cannot legislate against greed.
As long as there is a way to abuse the system, they will. If the technology makes it impossible for them to disguise their location or identity we can block them with confidence - this is differnt to what we are doing now.
Legislation is not the answer.
There are too many juristictions in which you cannot enforce *your* law. Even if the UN stepped in - who will prosecute?
The answer is in the technology.
Where is SMTP version 2 (or whatever) that fixes this shit?
Let's rollout IP6 and change the protocols so typing in any old crap into an MTA makes it work !
Sure spammers will still spam, but they could no longer lie about who they are or where they are sending mail from. Don't want it - block it.
Also - all you ISP's out there that host open relays for networks other than your own - you suck!
Webmaster//The function will append "@domain.com" to the name provided and return a "mailto:" type link.
function Email(name)
{
var EmailLink = "mailto:" + name + "@domain.com";
parent.location=EmailLink;
}//-->
email me here
Lots of things in Windows 200 / AD do not work as expected or at all.
I work for a global company that is trying very hard to use nothing but MS - they are finding it hard going....
It gets better with Netware 6.5 - Full file versioning in the system.
Imagine being able to restore a previous version of the file you were working on because you stuffed it up !
The problem is that people are still thinking Novell = Netware.
While Netware has traditionally been the cash cow of Novell, it is not where their future lays. The acquisition of Cambridge and Silver Stream completes Novell's direction into web-based services. Couple these with eDirectory, DirXML, Zenworks and Portal and you have a very powerful solution to overcome many problems facing large enterprises.
BTW "failing dead last [samag.com]" has no reference to Netware at all and Kreskin [amdest.com] is a dead link. I have no idea how you get OS statistics from a web server survey and who the hell is "Theo" on which you base wild guesses into the number of Netware *administrators* (not users!)?
Slashdot Mirror
What a bunch of crap!
Many countries/people around the world play violent video games and watch horror movies and manage not to kill anyone.
The prevelance of video games around the world makes drawing these sort of conclusions statistically meaningless. So many people play games it hard finding someone who hasn't, let alone someone who hasn't AND killed a bunch of people. You may as well say drinking coffee causes people to flip out.
The problem you refer to seems limited to America. Watch "Bowling for Columbine" for an interesting point of view on this.
Novell's strengths are no longer in the Network Operating System space, which is what made them. Nowdays their focus is on getting your network to act as one, regardless of the underlying operatings system or applications.
Take a look at eDirectory, which is far superior to MS AD and runs on almost any OS. Identity Manager (formerly DirXML) can syncronise information across your enterprise.
Zenworks delivers applications/patches to your workstations, servers, laptops and handhelds based on who you are and what relationship you have with the company (employee, division, position, customer, business partner, etc). Furthermore, it does not care how you connect!
Adding linux to the mix gives existing Netware installations an alternative future and piggybacks off OSS - smart move. For some interesting reading have a look at Open Enterprise Server - all your favorite Novell utilities on a linux platform. I for one will be making use of this....
.... and the new hardware it on on.
They probably migrated off a 10-20 year old clunker.
Maybe a directory would be better? Most directories have optional values on objects and many do not store the attribute if there is no value (assuming you count nulls as not valuable).
It is then trivial to determine who has died based on ldap searches:
ldap:///o=org??sub?(died=true)
or
ldap:///o=org??sub?(objectClass=died) (assuming aux classes)
Nested groups are a good way to overcome the group management problem alluded to here.
Since AD does not allow OU's to be security principles (or anything apart from users, groups and computers), you cannot leverage the directory structure to assign rights.
Hence, you must create another heirarchy via nested groups that will largely reflect the existing directory structure in most organisations. This seems to be a doubling of effort to me, complicating management and imposing additional work loads on IT staff.
...or much easier to manage with federated identity.
I want to decide the information about me a company sees and who they can share it with. This is what Liberty provides.
I have great reservations about giving ALL of my details to any company or government.
Yes, except that (in typical MS style) the ACL's are stamped onto EVERY folder and file. Making changes to file system security consumes vast amounts of CPU and thrashes the HDD. Plus, you can't assign secuity based on the AD structure (everyone is sales has read access to this directory). Only groups and users will do. Microsoft file system security os only a little better than Linux. Both still are missing very granular rights - try revoking permissions to list, read, rename, delete, copy or execute individually on these platforms.
You are partly correct, but there are a couple of points to make:
1) IPX/SPX is a routable protocol, so it is not limited to the LAN.
2) IPX/SPX is better than TCP/IP in mnay respects, but the Unix community was committed to a non-proprietory protocol.
3) Early versions of Windows used NetBIOS, which is no good for the routed world.
4) Short sighted managers figured since they have Microsoft on the desktop in front of them, doesn't it make sense to have a Microsoft Server?
Taxelation = The joy of receiving your tax return, which lasts until you realise it was your money to begin with.
Since when has anything the ATO done made sense?
I hear people worry about security on a daily basis and what many of them fail to realise is that is essentially a problem of identity.
Security is the process by which you determine if somebody is allowed to see the information concerned - this hinges on who they are and what they are trying to access.
How to do proof you are who you say you are?
This is actually a very difficult question.
hat aside (for now), all security/identity is built around 3 things:
1) Something you know (usernames, passwords, etc)
2) Something you have (secureid cards, tokens, passes, etc)
3) Something you are (biometrics, fingerprints, retina scans, genetics, etc)
The first two are easily overcome with some creative thinking - read Kevin Mitnick's "The Art of Deception".
The third has the same problems the other two have - how do you establish identity to begin with?
Anyone can claim an identity, all you need is the documentation to "prove" it and these can be forged or obtained with little effort. So how can you ever really know who you are dealing with?
OMG ! The security groups first priority is to be "Microsoft's first and best customer", while the last is to "Run a world-class utility". Shouldn't this be the other way around? Here's an idea - why not use the best technology available? If it is not yours - look, listen and learn.
You are confusing technology with the *use* of technology.
Sure, Flash has been abused and misused to display all sort of "cute" animations, but so has a lot of other technologies.
Good web designers understand the benefits Flash provides and use them properly. The rest use it as a means to make their site look good, without actually being good.
A "proper open-source directory service"?
Novell's eDirectory is by far the best directory in the market today and already runs on Linux.
I hope Novell port their file system (NSS) to Linux - that would be awesome!
Two words - Novell Zenworks.
Install you patch to mobile users securely over the internet automatically.
Problem solved (mostly).
ISPs blocking outgoing SMTP will not solve the problem in itself.
Users would have to forward mail to the ISPs smart host for delivery, which should only accept mail from their own IP ranges, BUT it is still delivered.
The trick may be to add another layer - restrict the number fo emails from a single server over a specific time period. This puts a bottle neck on spammers and helps, but does not eliminate the problem.
The real problem is the immaturity of the internet as a technology. Each layer in thr OSI must authenticate to the layer below and be signed so we can be certain of the traffic received, accept upon and transmitted. Bring on IP6 for a start!
At least logs of email traffic can be obtained and serious offenders kicked & banned.
I agree spam is a social problem, but it is a global society we are dealing with, so we need global laws to deal with the problem.
I agree spammers annoy, harras and steal from us all, but legislation only acts as a deterent, not a remedy. People still steal, cheat, lie, kill, etc even when we have laws that prohibit these behaviours. You cannot legislate against greed.
As long as there is a way to abuse the system, they will. If the technology makes it impossible for them to disguise their location or identity we can block them with confidence - this is differnt to what we are doing now.
Legislation is not the answer. There are too many juristictions in which you cannot enforce *your* law. Even if the UN stepped in - who will prosecute? The answer is in the technology. Where is SMTP version 2 (or whatever) that fixes this shit? Let's rollout IP6 and change the protocols so typing in any old crap into an MTA makes it work ! Sure spammers will still spam, but they could no longer lie about who they are or where they are sending mail from. Don't want it - block it. Also - all you ISP's out there that host open relays for networks other than your own - you suck!
Webmaster //The function will append "@domain.com" to the name provided and return a "mailto:" type link.
function Email(name)
{
var EmailLink = "mailto:" + name + "@domain.com";
parent.location=EmailLink;
} //-->
email me here
Lots of things in Windows 200 / AD do not work as expected or at all. I work for a global company that is trying very hard to use nothing but MS - they are finding it hard going....
It gets better with Netware 6.5 - Full file versioning in the system. Imagine being able to restore a previous version of the file you were working on because you stuffed it up !
The problem is that people are still thinking Novell = Netware. While Netware has traditionally been the cash cow of Novell, it is not where their future lays. The acquisition of Cambridge and Silver Stream completes Novell's direction into web-based services. Couple these with eDirectory, DirXML, Zenworks and Portal and you have a very powerful solution to overcome many problems facing large enterprises. BTW "failing dead last [samag.com]" has no reference to Netware at all and Kreskin [amdest.com] is a dead link. I have no idea how you get OS statistics from a web server survey and who the hell is "Theo" on which you base wild guesses into the number of Netware *administrators* (not users!)?
You only need a DOS partition the size of RAM if you want to do a core dump of memory for diagnostic purposes.
You can unload DOS from memory using "secure console"
Update? Maintain?h tm
http://developer.novell.com/ndk/perl5.
Version 5.8, no doubt...
Yeah - and remove lilo from linux and it does not boot. So it is fair to say that linux runs on lilo by your logic...