T.R | Title | User | Personal Name | Date | Lines |
---|
235.2 | Feature still there in other editors | CURRNT::OTTEN | Lead-Free and Ozone-Friendly | Thu May 18 1989 13:46 | 4 |
| The "Bug" still works in LSE, and ,I believe, EVE - even under V5
and V2.2 of TPU
David
|
235.3 | Sorry, NOT EVE. | CURRNT::OTTEN | Lead-Free and Ozone-Friendly | Thu May 18 1989 13:48 | 1 |
|
|
235.4 | | CURRNT::BADMAN | Nipple end in tears ... | Thu May 18 1989 13:52 | 10 |
| Unfortunately, LSE isn't always useful for some development ...
Could someone who knows please explain why we have captive accounts
on development machines ? I know it's a security standard; it's
a standard which is, to say the least, questionable when applied
to the development environment ...
Jamie.
|
235.5 | ;-) | CURRNT::ADDLETON | 4 sale - old Galasphere, reg 347 | Thu May 18 1989 14:50 | 5 |
| > Could someone who knows please explain why we have captive accounts
> on development machines ? I know it's a security standard; it's
Maybe it's to stop people choosing not to run their own LOGIN.COMs
;-)
|
235.6 | | HEAD::EBDON | Reality's on the blink again. | Thu May 18 1989 15:30 | 7 |
| If you want your development account not to be captive, just ask.
It worked for me. The purpose of the captive flag is to force the login
procedure to be run. It is not the correct method for utilities
to determine that they are in a "secure" environment. The bug is in
programs like MAIL and NOTES that assume otherwise.
Terry
|
235.7 | Question the unquestionable | CURRNT::BADMAN | Nipple end in tears ... | Mon May 22 1989 11:24 | 9 |
| Cor! You're right! Captive flag removed without hesitation on request!
I always thought it was one of those obscure security requirements.
Question now is, why is it set at all when Development accounts
are created ???
Jamie.
|