"prompt" keyword not recognised in tac_plus-ng.cfg about event-driven-servers HOT 14 CLOSED

Hi Phil,

thanks, looks like a documentation error. "welcome message" instead of "prompt" should work, I've dropped the "prompt" keyword there.

Thanks,

Marc

from event-driven-servers.

Hi Phil,

sorry, "welcome banner", not "welcome message".

Thanks,

Marc

from event-driven-servers.

Many thanks Marc

I think SecureCRT might have been part of the problem as it was not displaying the the welcome banner correctly. Are you aware of any known issues with truncation of welcome banner text? Also is it possible to serve a custom password prompt?

Kind regards Phil

from event-driven-servers.

Hi Phil,

whether the welcome banner is displayed or not largely depends on the implementation. It may work, or the router drops it, or the SSH client does so. I'm not a SecureCRT user myself, I think both putty and openssh work.

Custom prompts have been on my to-do list for quite some time. I'll have another look at that later.

Best regards,

Marc

from event-driven-servers.

Hi Phil

the answer to "custom prompts" did just changes to "yes".

message PASSWORD = ...

Cheers,

Marc

from event-driven-servers.

from event-driven-servers.

Hi Marc,

I'm not sure which configuration context to place the message keyword in, I tried this ....

    host corporate {
        address = 0/0
        key = {{ key }}
        message PASSWORD = "Password: "
    }

and got this .....

Nov 28 12:34:13 rocky1 tac_plus-ng[7646]: Error /etc/tac_plus-ng/tac_plus-ng.cfg:62: Expected 'host', 'parent', 'authentication', 'permit', 'bug', 'pap', 'address', 'key', 'motd', 'welcome', 'reject', 'enable', 'anonymous-enable', 'augmented-enable', 'single-connection', 'debug', 'connection', 'context', 'rewrite' or 'script', but got 'message'

kind regards Phil

from event-driven-servers.

Hi Phil,

I've actually implemented this at realm (or default) level, but moving the functionality to host level might indeed be an option. I'll have a look at that.

Thanks,

Marc

from event-driven-servers.

Hi again,

the "message ..." directives should now work in host context.

Cheers,

Marc

from event-driven-servers.

from event-driven-servers.

Hi Marc,

Thanks for the explanation about context, I've tried the following in both default realm and hosts contexts and this is confirmed working for Putty and Rocky Linux ssh clients.

message PASSWORD = "Password"

I have a question about intended behaviour of this feature which relates to a trailing ": " being added to the prompt, is this needed?

Regards Phil

from event-driven-servers.

Hi Phil,

I originally thought that adding the trailing characters would be a good idea. The latest commit drops that idea.

Cheers,

Marc

from event-driven-servers.

Thanks Marc

That'll do nicely, consider this issue closed.

Regards Phil

from event-driven-servers.

Hi Phil,

great, I've been waiting for that, I don't like open issues ;-)

Thanks,

Marc

from event-driven-servers.