Sponsored Content
Full Discussion: Communication over firewall
Special Forums Cybersecurity Communication over firewall Post 302231563 by bbala on Tuesday 2nd of September 2008 03:40:49 PM
Old 09-02-2008
when `ForwardingX11 yes ` is set all users are able to ssh with x term i.e they can use display or GUI..
Is there any way to restrict to few users alone..
i.e only some special users can use ssh -XCPY
and others cant use the above option...
where to edit for giving certain users more previleges??
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

serial communication

This isn't really a unix question, or even a programming question, but I hope you guys can help. I want to create a program to control the electricity on a model railway. I have created the program to that it sends characters over the serial cable, but now I need to do the switch that will... (1 Reply)
Discussion started by: KrazyGuyPaul
1 Replies

2. UNIX for Advanced & Expert Users

Interprocess communication status

hello gurus, I was wondering if someone would help me shed more light on this command. What I know so far is ipcs - stands for inter-process communication status and it reports on the following types of system resources. 1) Message queues 2) Shared memory and 3) Semaphores Please explain... (4 Replies)
Discussion started by: jerardfjay
4 Replies

3. Solaris

help on network communication

Hi, Can anyone suggest a Unix command or c-shell algorithm to simulate to behavior of "wall" command minus the "all users"? What I'm trying to do is to send a notice to just one particular user but i dont want other remotely-logged-on users to receive the message (on the pseudo-terminals). I... (3 Replies)
Discussion started by: Deanne
3 Replies

4. HP-UX

Communication Failures

HI ALL, I have been trying to install a particular software using remote linux server. some thing like this: rsh <host ID> /usr/sbin/swinstall -x autoreboot=true -s /tmp/<software> <Product name>. The problem is whenever I try to install the product through a shell script the installation... (1 Reply)
Discussion started by: barun agarwal
1 Replies

5. AIX

communication problems

hello i'v two aix servers 4.3. last night the goes down becuse electrical f problems. when the servers comes up i've notice that file /unix is gone. i've fix it and the problem fixed. after few hours the same crash becuse elctrical problems. file /unix is there , but now i've a... (0 Replies)
Discussion started by: ariec
0 Replies

6. UNIX for Dummies Questions & Answers

Interprocess Communication

Hiya Everybody just joined, Not sure if this is the right section:o I require abit of an assistance with IPC! I know there are different types of IPC porcesses like signals, semaphores, mutexes, shared memory, message queues, pipes and sockets. Now say a system has a number of... (4 Replies)
Discussion started by: G.I.Joe
4 Replies
MASON(1)																  MASON(1)

NAME
mason - interactively create a firewall SYNOPSIS
mason < logfile > rulefile DESCRIPTION
This manual page briefly documents the mason command. mason interactively generates a set of firewall rules for a Linux-based firewall. This is done by turning on full IP logging, watching the logs for connections, and generating rules describing the connections seen. mason is familiar with most of the quirks of various connec- tion types (such as ftp and IRC), and can output rules for 2.0.x ipfwadm, 2.2.x ipchains, and Cisco packet filters. mason operates by reading in log file information from standard input and writing firewall rules to standard output. This allows mason to work offline or on a separate system. Real-time firewall generation can be achieved with a command like tail(1). Most users will want to run mason with a user-friendly interface such as mason-gui-text(1). ENVIRONMENT
mason is configured using the following environment variables. ECHOCOMMAND Sets the type of firewall rules that mason should output to standard out. Allowed values include "ipfwadm" and "ipchains". By default, mason outputs whatever kind of rules are supported by the currently running Linux kernel. DOCOMMAND Sets the type of firewall rules that mason should run immediately when a rule is generated. Allowed values include "ipfwadm" and "ipchains". By default, mason outputs whatever kind of rules are supported by the currently running Linux kernel. HEARTBEAT If set to "yes", mason will output a "+" or "-" to standard error whenever a rule generated by mason has been triggered. DYNIP Set this to the list of interfaces that have dynamically assigned addresses, separated by spaces. SEE ALSO
mason-gui-text(1) AUTHOR
This manual page was written by Jeff Licquia <jeff@luci.org>, for the Debian GNU/Linux system (but may be used by others). MASON(1)
All times are GMT -4. The time now is 08:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy