STREAMS T_CONN_IND messages in Solaris 10

Question

We have a STREAMS module that we push on top of TCP to intercept both inbound and outbound connections. We have recently discovered that our module no longer seems to work on Solaris 10. It appears that for inbound connections (i.e. those coming in from the wire), the T_CONN_IND messages do not seem to be passed to our module's rput routine. Anyone know what gives? We know that TCP and IP have been merged in Solaris 10, but we didn't think that would affect modules pushed on top of TCP. Is one of the optimizations that was made to skip the STREAMS messaging for connection indications and do something more direct between TCP and sockmod?
Any help would be appreciated.
Thanks,
Tony

Answer 1

janp2 wrote:
I hit this issue right now so I'm pasting a part of my reply to another list.
It might help other people:
==
The "Warning: Your password has expired, please change it now." comes in a
separate SSH_MSG_USERAUTH_INFO_REQUEST packet. This packet in general has an
"instructions" field, and some "prompt" fields. SunSSH server sends the warning
in a separate info-request packet, with 0 prompts, and with the warning message
in the instruction field. That's fine according to the spec (rfc 4256):
The num-prompts field may be `0', in which case there will be no
prompt/echo fields in the message, but the client SHOULD still
display the name and instruction fields (as described below).
however, when the number of prompts is 0, putty ignores the instruction field.
SunSSH client does the right thing, OpenSSH client as well. In theory, we could
put the warning message in the next info-request packet together with the "New
Password" prompt but that decision was intentional, we would be really "fixing"
stuff to workaround problems somewhere else.
so, my conclusion is that they should file a bug againt those SSH clients they
use. It's not a problem in the SunSSH server at all.
==
BTW, the putty's file is ssh.c, the instruction field is set on line 7474:
s->cur_prompt->instruction = ...
but add_prompt() function that prints the stuff out is called inside of the
following loop:
for (i = 0; i < s->num_prompts; i++)
so, as we can see, if the number of prompts is 0, we get no instruction
field printed.
Jan.Thank you very much, Jan. That was very helpful - at least now I have confirmation.
Update: I contacted the dev team for PuTTY and they let me know that this bug has been fixed in the latest Development version of PuTTY but there isn't a firm release date planned. Anyway, it'll be fixed in the next release of PuTTY
Edited by: dubitancy on Jan 7, 2010 6:33 AM