|
|
| Author |
Message |
| 25 new of 292 responses total. |
tpryan
|
|
response 75 of 292:
| 
Oct 19 01:59 UTC 1999 |
I had the same dial-in problem earlier this evening.
|
mcnally
|
|
response 76 of 292:
|
Oct 19 04:40 UTC 1999 |
Hmmm.. I'd've thought that would've prevented me from ssh'ing in,
too -- or was it fixed by the time I posted #73?
|
gull
|
|
response 77 of 292:
|
Oct 19 05:05 UTC 1999 |
sshd generally isn't run from inetd. The reason is that inetd only launches
a program when there's an incoming connection. That's a bad idea for sshd,
because it needs to generate an encryption key when it's started, and that
can take 15 seconds or so. So usually it's just allowed to run all the
time, independantly of inetd.
|
mcnally
|
|
response 78 of 292:
|
Oct 19 05:27 UTC 1999 |
Makes sense..
|
scg
|
|
response 79 of 292:
|
Oct 19 05:42 UTC 1999 |
Running sshd and inetd independantly is also useful if one of them dies, since
it's then possible to access the system using the other one.
|
jazz
|
|
response 80 of 292:
|
Oct 19 15:27 UTC 1999 |
Naah, that's what modems're for! :)
|
richard
|
|
response 81 of 292:
|
Oct 19 15:28 UTC 1999 |
I dont really want to set up .yeswrite or .nowrite files because I dont
mind getting tels, and it feels anitsocial in this environment to be
using such files. I just want to permanently block any !talk requests
because anybody !talking me should really be !teling me, and I have
rarely ever had somebody !talking me from offsite. there isnt a way
to do that?
|
pfv
|
|
response 82 of 292:
|
Oct 19 15:57 UTC 1999 |
Damn, that's racist and antisocial - you should let EVERYONE tel &
talk to you! At *ALL* times!
Sheesh..
|
richard
|
|
response 83 of 292:
|
Oct 19 16:28 UTC 1999 |
its not racist, I dont mind if an Indian user !tels me-- some of them
are nice-- I just dont want to turn off !tels just because I want to
turn of !talk
|
pfv
|
|
response 84 of 292:
|
Oct 19 17:12 UTC 1999 |
Separationist!
|
omni
|
|
response 85 of 292:
|
Oct 19 17:30 UTC 1999 |
I'm getting sick of being constantly !tel'ed and talked. I come to grex to
do chat and I damn well aint going to start now. Wanna talk to me, send me
an e-mail
|
remmers
|
|
response 86 of 292:
|
Oct 19 17:35 UTC 1999 |
I think being able to turn off talk requests without turning off tel's
would be reasonable. I'd email janc about it - he's the
author/maintainer of the write/tel stuff.
|
gull
|
|
response 87 of 292:
|
Oct 19 22:26 UTC 1999 |
At very least, someone should hack the 'talk' source so it only pages you
*once*, instead of repeatedly. It's a very rude program.
|
pfv
|
|
response 88 of 292:
|
Oct 19 22:33 UTC 1999 |
It's garb- errr.. "it's not a problem" .."it's not an issue"
|
drewmike
|
|
response 89 of 292:
|
Oct 20 02:35 UTC 1999 |
(Hey, did anyone else notice that Peefv never mentioned any specific
ethnicity, which Richard instantly pegged as Indian? Hell's yeah, I still got
the instigator in me...)
|
mooncat
|
|
response 90 of 292:
|
Oct 20 12:41 UTC 1999 |
It may not be a probelm or an issue, but I would like to be able to turn
!talk off completely... I never use the program, and I don't like it.
|
pfv
|
|
response 91 of 292:
|
Oct 20 14:51 UTC 1999 |
Gee, youse guys make it sound like it's your RIGHT to control
the contents of yer CRT..
(while you are modding, set it up like bbs or party: user defined
filter-insertion)
|
gelinas
|
|
response 92 of 292:
|
Oct 21 01:17 UTC 1999 |
Edit your .login file and make sure it has the lines
setenv MESG mesg
mesg n
If you change your mind, change that final character to a "y".
|
davel
|
|
response 93 of 292:
|
Oct 21 01:47 UTC 1999 |
... or just do "mesg y" on the fly to change it for one session.
|
gelinas
|
|
response 94 of 292:
|
Oct 21 03:22 UTC 1999 |
I wish I could backspace at the login: and password: prompts. And I'm
not all that bad a typist.
|
gull
|
|
response 95 of 292:
|
Oct 21 04:33 UTC 1999 |
You have a problem with your terminal settings. Your backspace key is
probably set to send ^?, while login expects ^H.
|
gelinas
|
|
response 96 of 292:
|
Oct 21 04:49 UTC 1999 |
Nope. I can solve *that* problem. But when I do, grex reports, "Not allowed
to modify login" or words to that effect. And my terminal sends <CTRL>H,
which gets displayed as "^H", of course.
|
gelinas
|
|
response 97 of 292:
|
Oct 21 04:57 UTC 1999 |
Here 'tis:
} (ttyr6) grex login: gelasdfk^?^H^?^?^?^H^H^H^H^H^H^?^?^?^?^?^?
} You may not change $L0
} gelas's Password:
Hmmm... This gives me an idea.
|
gelinas
|
|
response 98 of 292:
|
Oct 21 05:01 UTC 1999 |
That did it:
} login: abcd^H^H^H^Hgelinas
} gelinas's Password:
So I just have to carefully count how many <CTRL>Hs I need.
|
mdw
|
|
response 99 of 292:
|
Oct 21 10:32 UTC 1999 |
If you type whitespace on the login line, the extra parameters get
converted to environment variables L0, L1, etc. Login checks for
various extraneous environment variables (such as LD_LIBRARY_PATH) that
have security implications, and rejects them. It uses the pattern L*,
which has the side-effect of rejecting L0,L1 as well. It might not be
obvious, but L0, L1 do have security implications -- sometimes people
who fat finger their password manage to get it into the login prompt,
and we don't want to export passwords or parts thereof into the
environment.
|
