Topic: Changes in setprop syntax between 6.0 and 7.0?

[ddougan]

I have a new client whose server I will upgrade from RH 7.0 to SME Sever 6.0 next weekend. This client has a core business application that is currently accessed on the server via Procomm Plus using Wyse 60 emulation (and, of course and unfortunately, telnet).

As I need to move them forwards a step at a time, I want them to be able to continue to use Procomm on the local network for the time being. I can achieve this on 6.0 by enabling telnet by executing

"/sbin/e-smith/db configuration setprop telnet status enabled PermitRootLogin yes access private"

I've tested this and it works. It also enables remote access if I set up a PuTTY session and forward the telnet port.  As I also plan to get them up to 7.0 as soon as is practical after release, I've been testing the same scenario on 7.0rc1. I've found that the setprop command doesn't seem to work, so I'm assuming that the syntax may have changed.

I realize telnet is a bad thing, and normally I wouldn't go within 500 miles of it; however, given the dearth of Wyse 60 emulators, and the need to educate the client in improving his security, locally-enabled telnet is a fair compromise, given the office is small and access is easily managed.

So, all that said, has the setprop syntax changed, and is so, what should be used now (or, preferably, where can I find examples)?

Thanks,

Des

[CharlieBrady]

So, all that said, has the setprop syntax changed ...?

No.

What does "doesn't seem to work" mean exactly?

[JonB]

There is no database entry for telnet as a service in SMErc1.

Code: [Select]

#config show telnet
#

There also no e-smith-telnet or smeserver-telnet rpms.

Code: [Select]

# rpm -qa *telnet*
telnet-0.17-31.EL4.3
#


It would appear that telnet as a SME service is totally removed from SME7.

If this is a bug it should be reported.

Jon

[ddougan]

Charlie,

When I run the setprop command on 6.0, I can see the database entry in the configuration file, see the warning in the Server Manager panel and can log in. None of this occurs in 7.0.

Jon's reply looks like it answers why. I don't think raising a bug is particularly productive, given the desire to not use or support telnet. I can plan a migration away from Procomm along with the 7.0 upgrade.

Thanks to you both.

Des