Bug 118180 - unable to toggle on telnet using yast2-xinetd
Summary: unable to toggle on telnet using yast2-xinetd
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 4
Hardware: Other All
: P5 - None : Minor
Target Milestone: ---
Assignee: Lukas Ocilka
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 97395
  Show dependency tree / graph
 
Reported: 2005-09-21 07:45 UTC by Martin Mrazik
Modified: 2005-09-22 08:35 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
y2logs (537.29 KB, application/x-gzip)
2005-09-21 07:45 UTC, Martin Mrazik 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Mrazik 2005-09-21 07:45:24 UTC 
I need to enable telnet. In the "Network Service Configuration (xinetd)" window
of yast2 there are two telnet daemons I can choose from - /usr/sbin/telnetd and
/usr/sbin/in.telnetd. I want to toggle on the first one (/usr/sbin/telnetd).

Now a dialog box apppears saying me "These packages need to be installed:" and
there is empty list of packages that should be installed. Click
"Continue"..."Reading package information"...."Package was not installed. The
service cannot be edited."

/usr/sbin/in.telnetd works fine.

y2logs attached.
Comment 1 Martin Mrazik 2005-09-21 07:45:51 UTC 
Created attachment 50518 [details]
y2logs
Comment 2 Michael Gross 2005-09-21 10:40:34 UTC 
This sounds like a bug. Reassigned.

I think you're quite aware that telnet is really a large security-hole and you
should use SSH instead ;) Don't get me wrong but I had to mention this... if not
for you but for all the others.
Comment 3 Lukas Ocilka 2005-09-21 10:44:07 UTC 
This part of source code is a crap, just inspecting another bug around...
Comment 4 Lukas Ocilka 2005-09-22 08:35:59 UTC 
Hmm, that had been very strange util I've found what was wrong: yast2-inetd
generates the default config file by hand and that one was too old. New one has
been generated.