|
Grex > Helpers > #122: Grex System Announcements - Fall 2003 |  |
|
| Author |
Message |
| 25 new of 68 responses total. |
cross
|
|
response 14 of 68:
| 
Oct 22 17:24 UTC 2003 |
This response has been erased.
|
gull
|
|
response 15 of 68:
|
Oct 22 17:40 UTC 2003 |
A bigger problem is that if your password expires, ssh will not let you
in. You have to telnet in to set the password, which means the new
password gets sent in cleartext across the network.
|
tod
|
|
response 16 of 68:
|
Oct 22 17:52 UTC 2003 |
This response has been erased.
|
cross
|
|
response 17 of 68:
|
Oct 22 17:53 UTC 2003 |
This response has been erased.
|
tod
|
|
response 18 of 68:
|
Oct 22 18:03 UTC 2003 |
This response has been erased.
|
cross
|
|
response 19 of 68:
|
Oct 22 20:46 UTC 2003 |
This response has been erased.
|
jhudson
|
|
response 20 of 68:
|
Oct 22 21:15 UTC 2003 |
After we get to the openBSD machine, why don't we scrap the
password expiration system altogether?
|
remmers
|
|
response 21 of 68:
|
Oct 22 22:14 UTC 2003 |
Here on Grex, when connected via ssh, I have SSH_CLIENT and SSH_TTY
environment variables set.
|
cross
|
|
response 22 of 68:
|
Oct 22 22:49 UTC 2003 |
This response has been erased.
|
malymi
|
|
response 23 of 68:
|
Oct 23 08:28 UTC 2003 |
the problem with sshd is that it believes it knows how to process a
login. the authors found that not all systems would even allow sshd to
do what it tries to do, so the arrogant fools were forced into providing
a method whereby the system login program can be invoked -- this via
`uselogin yes'.
|
gull
|
|
response 24 of 68:
|
Oct 23 13:30 UTC 2003 |
Though you have to be careful. A fair fraction of the security holes in
ssh were related to the use of "uselogin yes".
|
jp2
|
|
response 25 of 68:
|
Oct 23 13:31 UTC 2003 |
This response has been erased.
|
remmers
|
|
response 26 of 68:
|
Oct 23 13:35 UTC 2003 |
As I'm not all that knowledgable about the fine points of ssh,
please explain what "uselogin yes" is. Am I reading correctly
that it's a configuration option that, among other things, would
cause the same info to be displayed to the user on login that
would be displayed with a telnet login?
|
jp2
|
|
response 27 of 68:
|
Oct 23 15:35 UTC 2003 |
This response has been erased.
|
remmers
|
|
response 28 of 68:
|
Oct 23 17:29 UTC 2003 |
But does this have the effect I asked about?
|
jp2
|
|
response 29 of 68:
|
Oct 23 19:12 UTC 2003 |
This response has been erased.
|
tpryan
|
|
response 30 of 68:
|
Oct 25 15:10 UTC 2003 |
I thought grex had more lines? What is with the busy signals
on -3000?
Where was the announcement here about the dial-in lines
being disconnected?
Does any staff care anymore about the trunk hunt not working?
Again, an item 3 or 4 response would be nice if it is the process
of being fixed.
|
keesan
|
|
response 31 of 68:
|
Oct 25 15:16 UTC 2003 |
The dial-in cancellation was mentioned in the coop conference. I have not
had any problems but I dial 5041.
|
aruba
|
|
response 32 of 68:
|
Oct 25 15:54 UTC 2003 |
Sorry, TIm, you're right - I should have posted here. We are now down to 4
dialin lines: 761-3000, 5041, 3411, and 3451. Are you saying that the trunk
hunt isn't working at all, or just that all four lines were busy when you
tried to call?
|
gelinas
|
|
response 33 of 68:
|
Oct 25 16:41 UTC 2003 |
BTW, we should figure out which modems are no longer connected and unplug
them.
|
aruba
|
|
response 34 of 68:
|
Oct 27 15:43 UTC 2003 |
I called Ameritech this morning to get them to fix the hunting on our lines.
(I was afraid that if I called on the weekend, I'd get someone who would
make the problem worse.) I spoke with a gentleman named Jim, who checked
and found that all our numbers *except* 761-3000 had been programmed to
hunt. He sent a request down to the programming department to fix things,
and they should be better in a few hours. Please post here or send me mail
if there continue to be problems.
|
tpryan
|
|
response 35 of 68:
|
Oct 27 17:23 UTC 2003 |
Thank you for attention in getting this fixed.
I just dialed into -3000, any easy way to find if I did hunt down?
|
tpryan
|
|
response 36 of 68:
|
Oct 27 17:24 UTC 2003 |
I am currently on ttytf, but that might tell us if we hunted down
from -3000
|
scott
|
|
response 37 of 68:
|
Oct 27 17:33 UTC 2003 |
who | grep 216.93.104.37
will give a list of people currently dialed in, and from there you can guess
whether you successfully trunk-hunted.
|
aruba
|
|
response 38 of 68:
|
Oct 27 21:15 UTC 2003 |
Or you can dial 761-3000 with one phone, and dial it again with another.
|