SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Novell (NOVL) dirt cheap, good buy?
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Paul Fiondella who wrote (28503)10/6/1999 8:11:00 PM
From: Paul Fiondella  Read Replies (2) of 42771
 
Roger Thomas --- A note for SI on Bordermanager and Authentication

Wed, 06 Oct 1999 18:14:33 +0100

Currently I can't post to SI as they don't seem able cope with UK based credit cards due to their input forms, and they seem to treat it as my problem (must be a MS company)

I have seen one or 2 points I would like to comment on, could you post the following for me.

BorderManager and Authentication

BM does not use MAC addresses as a way to tell nodes apart. Instead it currently has 2 solutions. The first is a SSL based login, so creating a session between the browser and the BM server. The second is background with the workstation itself, currently this works by running an extra programming at the workstation which validates the workstation by the fact that it has been logged into an NDS Tree.

Future versions will use fingerprints, swipe cards and even pictures of your face. Intel came up with the idea of using a unique ID within its processors - look what happened to that!!!!!

BorderManager (or any firewall) against NAT users.

Features such as the one above, will allow ISPs to limit the use of NAT over their connections. Via QOS software authenticated sessions will be given higher priority than non-authenticated sessions. This will removes many of the advantages of NAT solutions.

This will provide connections a bit like ISDN where you have B channels at 64Kbits or 56Kbits and a background 16Kbit channel for session/connection information.

Digitalme security.

The current level of security means that Novell, can not directly data mine the details entered by reporting out the contents of its NDS tree. Single sign on encripts the data it stores with the users password. Of course Novell could code their CGI scripts to log details as they are accessed (including the password), that comes down to who you trust.

Currently once shared information becomes insecure - guess why there are no fields for credit cards details yet. I guess there will be extra security levels as the system grows, I can see the following

1) current - very basic but it has more features than most other systems.
2) controled access - details are shared between Digitalme accounts and you can revoke rights and maybe see an access log - this is not hard to do its part of NDS. At this level you could store credit card details.
3) Three way - transactions take place without credit card details being passed on, instead you inform the seller(small company) that a transaction can take place, this is then actioned by a third party(big safe! company) who does have access to your full details.

Roger
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  

HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2025 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News