Unfortunately, David, you're right. If I want to log on remotely to
my company's intranet, first I've got to go through a complex security
verification system that uses a scure-ID card I can't read. Well,
they've come up with some software that emulates this card, but I
haven't seen it work yet, so the bottom line is, I've still got to get
somebody to read the ever-changing digits on my card, and at two in
the morning when I get paged, my fiancee's not happy about it. Second
thing, after I pass muster with the bank's security system, I've got
to log in to two more levels of nonsense before I can get to run
anything--Telnet, Lotus Notes, anything at all--all because our
corporate intranet has so many firewalls built into it because people
are so paranoid of security breaches. None of the login sequences
speak well with JFW, and if I don't catch the right messages in the
right places, I fail the login sequences and have to start all over.
This is crap on rye! None of it speaks well, and it could all be made
to speak well with very little trouble, they just don't wanna bother
because I'm their only blind employee who needs this access. TOo bad.
For me, unfortunately.
On Thu, 02 Sep 1999 09:23:49 -0400, you wrote:
>sorry, but telnet may not apply here.
>jambet wrote:
>>
>> That's what they made telnet for, friend. And jfw works wonders
with that
>> with a little adjustment. I speak from experience.
>> At 03:05 PM 9/1/99 -0400, you wrote:
>> >If you want to develop something ground-breaking for people using
screen
>> >readers, think about software that allows such persons to log on
to their
>> >servers remotely. Working remotely for governments/companies is
becoming an
>> >ever-expanding reality and, from what I have experienced to date,
one that
>> >leads me to believe that the only people who will be going into
the office
>> >in the near future will be ones using access technologies. Won't
that be a
>> >switch.
-
Visit the jfw ml web page: http://jfw.cjb.net
