Hello,
On Aug 21, Jon Spencer wrote
> session - when you cross the system boundary and connect to a
> system, you create a "session,"
The problem with this is, that the session is only enforced within the B2
Systems. If you plug a B2 Firewall to a Unix/NT Intranet and allow Access from
authenticated Users to some internal Hosts there is no way the firewall can
enforce the protcetion which data is visible and which not. In fact the
Firewall is unable to know. (The Firewall can't look inside a telnet
connection to a 'non-B' Unix Host and control which files are allowed to
touch and which not). This means all of your applications have torun on B2
Systems to gain from that Session controlling.
Greetings
Bernd
BTW: how does B2 Systems communicate and send the information about the
Trust you (dont) put into a sesion? Is there a kind of Kerberos Token
Parsing or Global User Token System?
--
(OO) -- Bernd_Eckenfels @
Wittumstrasse13 .
76646Bruchsal .
de --
( .. ) ecki @
{inka .
de,linux.de,debian.org} http://home.pages.de/~eckes/
o--o *plush* 2048/93600EFD eckes @
irc +4972573817 BE5-RIPE
(O____O) If privacy is outlawed only Outlaws have privacy
Follow-Ups:
References:
|
|
