Trocar a senha via um script

chpasswd

Com o comando "chpasswd" da seguinte maneira:

echo "nom:password" | chpasswd

Authentication refused: bad ownership or modes for file .ssh/authorized_keys

When configuring SSH keys to be able to login to a server without a password you mighkeys2t run into a permissions error. If the authorized_keys or authorized_keys2 file has the incorrect permissions it will not authenticate with your ssh-rsa key but instead still require a password. If you are having trouble configuring SSH keys you should check the /var/log/secure file to see if there is an error displaying in that log. You may see the error displayed below.

Error: Authentication refused: bad ownership or modes for file .ssh/authorized_keys

If you see this error it means that the authorized_keys or authorized_keys2 file has the incorrect ownership or permissions. Make sure that the authorized_keys file is owned by the user that will be logged into and the permissions are 600. So if the username is backup you would want the file to look like the below when issuing the “ls -alh” command.

1        -rw------- 1 backup backup 409 Mar 23 19:56 authorized_keys

If the ownership or permissions are different than the above you can accomplish setting the proper ownership and permissions by using the below two commands.

1        chown backup.backup authorized_keys

2        chmod 600 authorized_keys

That should resolve your problems and now from the remote server you should be able to SSH to this server and login without a password.

Fonte: http://www.question-defense.com/2009/03/23/authentication-refused-bad-ownership-or-modes-for-file-sshauthorized_keys

A configuração do Certificado digital no IIS 7 é excluída automaticamente.

Sintoma:

O certificado digital desaparece da configuração do IIS e no event view é exibido a mensagem:

SSL Certificate Settings deleted for Port : 172.17.0.22:443 .

Solução:

Locate the following property in the section of the applicationHost.config file, and delete it:

     5506" dataType="Binary" userType="1" attributes="None" value="oXiHOzFAMOF0YxIuI7soWvDFEzg=" />

This property is a legacy feature from Internet Information Services (IIS) 6.0 and is no longer needed.

Colado de <http://support.microsoft.com/kb/2025598>

O arquivo applicationHost.config pode ser encontrado em:

%windir%\system32\inetsrv\config\applicationHost.config

Colado de <http://learn.iis.net/page.aspx/129/using-configuration-history-with-iis-7-and-iis-8/#Restoring>

 Como testar as operações de SMTP utilizando o Telnet

1. Ligar o Telnet ao Exchange Server que aloja o serviço IMS utilizando a porta 25.
Comando telnet 25
 
2. Ligar o local echo no cliente de telnet para poder ver o que está a escrever.
No Telnet do Win 9x e NT 3.5/4.0 fá-lo através da opção “preferences” do menu “terminal”, e seleccionando o botão de opção do local echo. No Telnet do Windows 2000, escreva o comando "set local_echo", no command prompt.

3. Execute a seguinte sequência de comandos smtp
helo                  
a resposta deve ser a seguinte
250 OK
mail from:
a resposta deve ser a seguinte
250 OK - mail from
rcpt to:
a resposta deve ser a seguinte
250 OK - Recipient
data
a resposta deve ser a seguinte
354 Send data.  Finalizar com CRLF.CRLF
To:
From:
Subject:
.
a resposta deve ser a seguinte
250 OK
quit

Fonte: http://www.rsoutlook.com/exc/telnetsmtp.htm

Backup commands for AIX

Creates image.data and system backup (-X expands /tmp if required):
#mksysb -i -X /dev/rmt0

Creates image.data file with map file and system backup:
#mksysb -m /dev/rmt0

Creates system data but excludes the files listed in /etc/exclude.rootvg:
#mksysb -e /dev/rmt0

Creates /image.data file:
#mkszfile

Creates system boot backup to the CD-R device /dev/cd1:
#mkcd -d /dev/cd1

Creates backup of vg vg00 to CD-R device /dev/cd1:
#mkcd -d /dev/cd1 -v vg00

Creates generic boot backup:
#mkcd -d /dev/cd1 -G

Creates vg00.data image file and backup vg vg00:
#savevg -i -f /dev/rmt0 vg00

Creates vg00 backup but excludes files listed in the /etc/exclude.vg00:
#savevg -ef /dev/rmt0 vg00

Backup entire system to rmt0:
#find / -print | backup -ivf /dev/rmt0

Backup /home directory to rmt0 with backup level 0:
#backup -0vf /dev/rmt0 /home

List the archive in rmt0:
#restore -Tvf /dev/rmt0

Restore /home from archive in device rmt0:
#restore -xvf /dev/rmt0 /home

Restores particular file from /export/mksysb image:
#restore –xvf /export/mksysb ./etc/sshd.conf

Archives /home directory:
#find ./home -print |cpio -ocvumB > /dev/rmt0

Create an archive of /home directory:
#tar cvf /tmp/home.tar /home

Restores cpio archive from rmt0:
#cpio -icvdumB < /dev/rmt0

List the contents of cpio archive from rmt0:
#cpio -ivt < /dev/rmt0

Restores /home directory from rmt0:
#cpio -icvd < /dev/rmt0 /home

Archives /home to rmt0 device:
#tar -cvf /dev/rmt0 /home

List the archives in rmt0:
#tar -tvf /dev/rmt0

Extract /home from rmt0:
#tar -xvf /dev/rmt0 /home

Convert and copy ascii file si to ebcdic si1:
#dd if=si of=si1 conv=ebcdic

To copy blocks from rmt0 with 512 blocks to rmt1 with 1024 blocks:
#dd if=/dev/rmt0 ibs=512 obs=1024 of=/dev/rmt1

To rewind the tape:
#tctl -f /dev/rmt0 rewind

To eject the tape:
#tctl -f /dev/rmt0 offline

To show the status of tape:
#tctl -f /dev/rmt0 status

To change the block size of the tape to 512:
#chdev -l rmt0 -a block_size=512

How to restore a file from mksysb:
# listvgbackup -f /path/to/mksysb.image -r ./etc/file

Fonte: http://docs.gz.ro/node/20



SRC – Gerenciamento de daemons no AIX

O AIX tem um gerenciador de daemons, chamado SRC, em inglês, “System Resource Controller“.
Através do SRC podemos verificar se um serviço está ativo, parar, iniciar ou reinicializar um serviço.

Isto pode ser feito através dos seguintes comandos:

startsrc: iniciar
refresh: reiniciar
stopsrc: parar
lssrc: verificar status

O SRC permite trabalharmos com um serviço ou um grupo de serviços. Para um serviço, usamos a opção “-s” e para um grupo, “-g”.
Por exemplo, para gerenciar os serviços de NFS:
Verificando status do grupo de serviços:

# lssrc -g nfs
Subsystem            Group    PID    Status
biod                nfs                                     inoperative
nfsd                nfs                inoperative
rpc.statd         nfs                inoperative
rpc.lockd         nfs                inoperative
rpc.mountd          nfs                inoperative

Iniciando um serviço:

# startsrc -s nfsd
# lssrc -g nfs
Subsystem         Group            PID     Status
nfsd             nfs              23672   active
biod             nfs                      inoperative
rpc.statd        nfs                      inoperative
rpc.lockd        nfs                      inoperative
rpc.mountd       nfs                      inoperative

Iniciando um grupo de serviços:

# startsrc -g nfs
0513-059 The biod Subsystem has been started. Subsystem PID is 17242.
0513-029 The nfsd Subsystem is already active.
Multiple instances are not supported.
0513-059 The rpc.statd Subsystem has been started. Subsystem PID is 19862.
0513-059 The rpc.lockd Subsystem has been started. Subsystem PID is 24236.
0513-059 The rpc.mountd Subsystem has been started. Subsystem PID is 6802.

# lssrc -g nfs
Subsystem         Group            PID     Status
nfsd             nfs              23672   active
biod             nfs              17242   active
rpc.statd        nfs              19862   active
rpc.lockd        nfs              24236   active
rpc.mountd       nfs              6802    active

Parando um grupo de serviços:

# stopsrc -g nfs
0513-044 The nfsd Subsystem was requested to stop.
0513-044 The biod Subsystem was requested to stop.
0513-044 The rpc.statd Subsystem was requested to stop.
0513-044 The rpc.lockd Subsystem was requested to stop.
0513-044 The rpc.mountd Subsystem was requested to stop.

# lssrc -g nfs
Subsystem         Group            PID     Status
biod             nfs                      inoperative
nfsd             nfs                      inoperative
rpc.statd        nfs                      inoperative
rpc.lockd        nfs                      inoperative
rpc.mountd       nfs                      inoperative

Fonte: http://www.unixnotes.org/2007/01/31/src-gerenciamento-de-daemons-no-aix 

AIX - Identificando portas abertas

É muito importante conhecer o ambiente que está sendo administrado. Em se tratando de servidores, muitas vezes temos em um ambiente muitas portas abertas (em modo listen), e é importante saber qual processo está ouvindo em uma determinada porta, por questões de segurança e até em situações de troubleshooting.

A dica de hoje é identificar, no AIX, qual processo está sendo executado em uma porta específica.

Método 1 - Usando os comandos netstat e rmsock

Protocolo TCP:

# netstat -Aan |grep *.1334
f1000e0002b753b0 tcp4       0      0  *.1334             *.*                LISTEN

# rmsock f1000e0002b753b0 tcpcb
The socket 0x2b75008 is being held by proccess 5701822 (writesrv).

# ps -ef |grep 5701822
root  5701822  1507536   0   Jun 10      -  0:00 /usr/sbin/writesrv

Como podem ver o processo writesrv está sendo executado na porta 1334.

Protocolo UDP:
# netstat -Aan |grep *.514
f1000e0002a67e00 udp4       0      0  *.514              *.*

# rmsock f1000e0002a67e00 inpcb
The socket 0x2a64c08 is being held by proccess 5308580 (syslogd).

# ps -ef |grep 5308580
root  5308580  1507536   0   Jun 10      -  0:36 /usr/sbin/syslogd

A porta 514 UDP está sendo utilizada pelo processo do syslogd.

Método 2 - Utilizando os comandos netstat e kdb (kernel debuger)

# netstat -Aan |grep 1334
f1000e0002b753b0 tcp4       0      0  *.1334             *.*                LISTEN

# kdb
(0)>
(0)> sockinfo f1000e0002b753b0 tcpcb

[... A saída do comando kdb é bem detalhado, e por isso foi truncado. O importante para nós é a ultima linha, como mostrado abaixo ... ]

proc/fd: 87/3
proc/fd: fd: 3
              SLOT NAME     STATE      PID    PPID          ADSPACE  CL #THS

pvproc+015C00   87*writesrv ACTIVE 05700BE 01700D0 0000001190239480   0 0001

O importante é saber o PID do processo, que está em hexadecimal na coluna PID.
 
Para converter de hexadecimal para decimal, basta utilizar o comando hcal, dentro do prompt do kdb. Como mostrado abaixo.

(0)>
(0)>
(0)> hcal 05700BE
Value hexa: 005700BE          Value decimal: 5701822
(0)> quit

De volta ao shell, verificar qual programa pertence ao PID 5701822.

# ps -ef |grep 5701822
root  5701822  1507536   0   Jun 10      -  0:00 /usr/sbin/writesrv

O mesmo procedimento pode ser utilizado para portas UDP, sempre trocando o parâmetro tcpcb por inpcb.

Dica válida para AIX versões 5.3 e 6.1

Fonte: http://www.vivaolinux.com.br/dica/AIX-Identificando-portas-abertas