Sponsored Content
Full Discussion: Securing remote connections
Operating Systems Linux Securing remote connections Post 302357322 by AlbertGM on Tuesday 29th of September 2009 10:47:48 AM
Old 09-29-2009
Securing remote connections

Hi all,

I have a couple of questions I've been searching on internet but I didn't find a suitable solution. The aim is that I'd like to access to my home Linux (an 8.04 Ubuntu) from outside. I already achieved with ssh, but I'd like to secure as much as I can. These are questions:
  1. The account I use to login is a sudoer user. So, I want to connect with an unprivileged user, and then, only if I need, reconnect with that user inside my linux. I'd like to disable that account (root is always disabled) from remote connections. How can I do that? or Where can I find some information to disable that account from remote connections?
  2. One of places I'd like to connect is from office, which has a proxy to connect to a computer out of LAN. Almost all ports are disabled. I'd like to know a way to find out which ports are open, to open in my own home the right one (a port also open in office proxy). I thought using "nmap" or "nc" to my own Linux, but it also has almost all ports closed. So connection is not possible unless I open all ports in my router, which is quite dangerous. Using nc or nmap I won't be able to know if a 'connection refused' is because my router has a certain port closed or because port in office proxy is close.
    For example I opened port 443 in my router which redirects to port 22 to my linux. I used this port, because I guessed HTTPS port was available in office proxy. I got right. However, this port is very used and I don't like to leave that port open at home.
Because of my english I don't know if my explanation is good enough, sorry Smilie Any help will be very appreciate.

Thanks
 

8 More Discussions You Might Find Interesting

1. Cybersecurity

securing a remote box

someone has access to my server... I've got a solaris 7 box with remote access only. many of the services don't have passwords and someone recently messed with the shadow file -the root: line was changed: . password field was changed to NP . the number after that was changed too The... (8 Replies)
Discussion started by: sphiengollie
8 Replies

2. Shell Programming and Scripting

Securing arguments

OK here is my problem. Ive been trying to write a script where i use the order "find". For example if i wont to find some file in the sql_work directory using the script. You use the command: loc sql_work "q*" in order to find all the queries in the directory. Is there any other way to do it,... (0 Replies)
Discussion started by: SolidSnake
0 Replies

3. AIX

securing a shell

I would like to secure a shell script from being broken out of with Ctrl-C or equivalent. Once a user logs in, he should not be able to exit to the command prompt. any ideas. Thank you J (1 Reply)
Discussion started by: jhansrod
1 Replies

4. Solaris

Unable to open remote connections

Hello everybody, This is an unusual problem that I am facing on my Solaris 9 on Sun Blade 150 workstation. I can ping remote machines (outside subnet) but I can't open up a connection/port on those machines. For example, `ping ftp.xyz.com` gives ftp.xyz.com is alive but if I do a `ftp... (1 Reply)
Discussion started by: red_crab
1 Replies

5. Cybersecurity

Securing Passwords

Hi All, I'd like to give you an example of what I am trying to achieve and perhaps you might be able to help me along. I would like to add the following criteria to new servers, from a password aging and lockout standpoint. -Number of failed logins before lockout: = 5 -Number of Passwords... (1 Reply)
Discussion started by: mkono
1 Replies

6. BSD

Remote connections unable after power falls

Hi everyone: I have a server used for testing running FreeBSD, last weekend we had power cuts in my job and our server was constantly rebooting. since then the network connections are very slow, it's almost impossible establish a remote connection with the server, however running any... (2 Replies)
Discussion started by: edgarvm
2 Replies

7. AIX

Securing AIX

Guys, i want to securing AIX after install by scratch. Is anybody can inform about the standard port which used by AIX? (4 Replies)
Discussion started by: michlix
4 Replies

8. UNIX for Advanced & Expert Users

See AIX server remote connections

Good morning, Is there any command to view remote conxiones an AIX server? Thank you very much and best regards. (1 Reply)
Discussion started by: systemoper
1 Replies
aconnect(1)						      General Commands Manual						       aconnect(1)

NAME
aconnect - ALSA sequencer connection manager SYNOPSIS
aconnect [-d] [-options] sender receiver aconnect -i|-o [-options] aconnect -x DESCRIPTION
aconnect is a utility to connect and disconnect two existing ports on ALSA sequencer system. The ports with the arbitrary subscription permission, such as created by aseqview(1), can be connected to any (MIDI) device ports using aconnect. For example, to connect from port 64:0 to 65:0, run as follows: % aconnect 64:0 65:0 The connection is one-way, and the whole data to the sender port (64:0) is redirected to the receiver port (65:0). When another port (e.g. 65:1) is attached to the same sender port, the data is sent to both receiver ports. For disconnection, use -d option. % aconnect -d 64:0 65:0 The address can be given using the client's name. % aconnect External:0 Emu8000:1 Then the port 0 of the client matching with the string "External" is connected to the port 1 of the client matching with the "Emu8000". Another function of aconnect is to list the present ports on the given condition. The input ports, which may become sender ports, can be listed with -i option. % aconnect -i client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 64: 'External MIDI-0' [type=kernel] 0 'MIDI 0-0 ' Similarly, to see the output ports, use -o flag. You can remove all existing exported connections using -x option. This function is useful for terminating the ALSA drivers, because the modules with sequencer connections cannot be unloaded unless their connections are removed. OPTIONS
CONNECTION MANAGEMENT -d, --disconnect Disconnect the given subscription. -e, --exclusive Connect ports with exclusive mode. Both sender and receiver ports can be no longer connected by any other ports. -r, --real queue Convert time-stamps of event packets to the current value of the given real-time queue. This is option is, however, not so useful, since the receiver port must use (not necessarily own) the specified queue. -t, --tick queue Like -r option, but time-stamps are converted to the current value of the given tick queue. LIST PORTS -i, --input List existing input (readable) ports. This option is exclusive to -o. -o, --output List existing output (writable) ports. This option is exclusive to -i. -l, --list List the current connection status. The connected and connecting ports from/to each port are listed together. The suffix flag [ex] means the connection is exclusive. The suffix flag [real:#] and [tick:#] mean the connection includes real-time and tick conversion on the listed queue, respectively. REMOVE ALL CONNECTIONS -x, --removeall Remove all exported connections. SEE ALSO
aseqnet(1), aseqview(1) AUTHOR
Takashi Iwai <tiwai@suse.de> August 31, 2000 aconnect(1)
All times are GMT -4. The time now is 08:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy