(*** This bug was imported into bugs.kde.org ***) Package: konsole Version: KDE 2.2.2 Severity: wishlist Installed from: Mandrake RPMs Compiler: Not Specified OS: Linux OS/Compiler notes: Not Specified It would be nice to be able to select the Schema as well as the background/foreground colors from the command-line. One example application: I launch terminal sessions that ssh/rlogin/telnet to various remote hosts (-e telnet host). I use different colors depending on which remote host (e.g. red background for Production hosts etc.). Each host has its own shortcut on the KDE menu. It would be nice to be able to pass the standard X11 color (etc) arguments and/or the Schema on the command-line like Eterm which by the way I'm forced to use since Konsole lacks this feature. Only a suggestion. :-) Thanks Fred Wells (Submitted via bugs.kde.org)
This is a multi-part message in MIME format. ------=_NextPartTM-000-0dbb9d0b-302c-11d6-92b1-00d0b790a670 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable The original wish-list entry only mentions schema/colours - may I suggest t= hat the keyboard also be selected via command-line parameter. I frequently have to telnet into an old SCO box using vt-220 - It'd be very= useful to launch konsole from a menu entry with the keyboard and schema pr= e-set. - Alan ------=_NextPartTM-000-0dbb9d0b-302c-11d6-92b1-00d0b790a670 Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" This email and any attachment(s) is/are confidential and privileged. No contractual responsibility is to be assumed from this correspondance unless specifically stated. If you are not the intended recipient please accept our apologies; please do not disclose copy or distribute information in this email or take any action in reliance on its contents; to do so is strictly prohibited and may be unlawful. Please inform us that this message has gone astray by forwarding it to info@jarrold.com before deleting it. Thank you for your co-operation. ------=_NextPartTM-000-0dbb9d0b-302c-11d6-92b1-00d0b790a670--
Subject: Re: Firewall setup - Stage 1 Ok David I've finally got dsome of this info together. The whole system is something of a mess, primarily because we have inherited a system which was supposed to cover Jarrolds as a whole (Print, Retail and Publishing) and was originally set upon the understanding that there wouldn't be a lot of internet connections. This goes some way to explaining the Class C 194.70.191.0 network. The 150.150.0.0 sub-net range was also in inheritance and we intend to move away from this in the future to the 10.32.0.0/11 sub-net. Again, in the future, we may need to split this sub-net further into departmental levels and put routyers/firewalls between departments. The main reason for this being that CTP may want to put in public web services which may be insecure as far as the rest of the company is concerned.. The attached visio drawings should give the basic details of routers, external links, subnets etc. as these stand at present and how we intend to progress them. We don't currently have our own Web or FTP servers configured. These should go in the Vio firewall DMZ as and when we set them up. Currently we have the Insite Web Server which is to go via the Vio proxy server service and the MIS web server which is both our internal web server and provides access for external employees. I doubt that this covers all that you require but I thought it best to send this now so that you can let me know what other info you want. - Alan alan.prescott@jarrold.com >>> David Chitolie <dchitolie@vio.com> 24/09/02 11:52:24 >>> Hi Alan, As we described earlier on our conference call there will be three stages to completing the secure installation of your firewall. Stage 1 - Information gathering - Lan diagram A) Network Side - Please include any switches, routers, Sonicwall Firewall and any external links you have coming into your LAN (eg Vio or any other leased line, adsl etc). B) Hosts - It's important for me to know the type of access each machine or subnet will have, you will need to include host and subnet positions on this diagram. Hosts can be mail, ftp or web servers etc. I need to know where they currently fit in your LAN to define a secure policy for inbound access to these servers. One way to completely bypass the firewall is to dial up to an ISP etc while connected to the LAN. If you have any users dialing up from the office to another LAN (Finance department may dial up to banking or payroll system) please include the machine that uses the analogue/ISDN line. If you do not currently have a network diagram I have attached a powerpoint diagram that can be used as a template. Its not very pretty but it's easy to change around for your needs. Once I have this info we can move to stage 2 - Defining inbound access to servers then last to stage 3 Outbound access definitions. The actual firewall configuration is the last stage. This policy is not specific to the Sonicwall, It's a policy you can implement on almost any firewall. Regards David Chitolie Vio Worldwide Operations Senior Systems Engineer Telephone: 01923 698 055 Mobile: 07803 976 030 Vio address: Operations@Vio Worldwide Limited Created an attachment (id=106) subnet.vsd Created an attachment (id=107) subnet_current.vsd Created an attachment (id=108) Printing LAN.doc Created an attachment (id=109) InterScan_Disclaimer.txt
What is now the status of this bug ? Will the colors or a color schema as command line argument be supported and if yes in which version ??? If not the misleading help should be corrected. Only options which have an effect should be listed. Nothing else. Nobody cares about qt options which do not have any effect ... Rainer
I don't understand the second comment or attachments or why this is closed too.
You can use ' --schema <name> Use given .schema file'. Comment #1: There is also ' --keytab <name> Use given .keytab file' No idea what comment #2 is about. I would say this bug could be closed.
I agree.. will add --schemas to get a list of available schemas.
I agree with comment #3 that: "The misleading help should be corrected. Only options which have an effect should be listed." The references to -bg and -fg should be removed from the --help --help-qt, and --help-all screens.