Hi,
Paul van der Vlis (p...@vandervlis.nl on 2018-03-19 11:57 +0100):
>
> Het zou behulpzaam zijn, als ik had kunnen nagaan wat ik om 21:15 voor
> commando had gegeven. Om het voor een volgende keer te voorkomen.
>
> bash_history is een goede zaak, maar eigenlijk zou ik
>> Er bleek een enorm bestand in /var/tmp/.guestfs te staan.
> >>
> >> Het zou behulpzaam zijn, als ik had kunnen nagaan wat ik om 21:15 voor
> >> commando had gegeven. Om het voor een volgende keer te voorkomen.
> >>
> >> bash_history is een
15 voor
> commando had gegeven. Om het voor een volgende keer te voorkomen.
>
> bash_history is een goede zaak, maar eigenlijk zou ik het loggen van
> commando's graag wat beter geregeld hebben.
> Zoals een timestamp voor elk commando.
Er is HISTTIMEFORMAT
zie
https://askubuntu.com
Hoi,
Vanochtend was een systeem volgelopen waarop ik gisteren had gewerkt.
Er bleek een enorm bestand in /var/tmp/.guestfs te staan.
Het zou behulpzaam zijn, als ik had kunnen nagaan wat ik om 21:15 voor
commando had gegeven. Om het voor een volgende keer te voorkomen.
bash_history is een goede
Subject line about says it.
Didnt exactly disappear but became zero-length.
Checked because there seemed to nothing in the history.
Closed that shell and restarted.
The last shell's commands were there, nothing else
Wouldn't bother asking were it not for shellshock...
Debian jessie (with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Buenas
¿Sabe alguien cómo cambiar esos números raros que mete en el
bashrc_history por lo que se muestra en el comando history.
Una vez me dijeron como estaban codificados y como sacarlos pero no he
conseguido recordarlo.
He visto un script
.bash_history
#1342427709
history
#1342427763
set
#1342427846
mc
#1342428059
exit
Esos números los mete en el bashrc_history al meter estas dos
El Sat, 14 Jul 2012 01:50:00 +0200, Ramses escribió:
El 13/07/2012, a las 18:40, Camaleón noela...@gmail.com escribió:
El Fri, 13 Jul 2012 12:44:59 +0200, Ramses II escribió:
(...)
¿Habría alguna forma de que en el .bash_history anteponga/postponga
a cada comando la IP de la Sesión que
pasar lo que suele pasar, yo no he tocado,
yo no he hecho eso,...
Claro, si en esos casos tiramos de .bash_history (contando que no se
haya sido malo y se hayan borrado rastros), ahí aparecen los
comanditos, pero claro, no sabemos quién los ejecutó...
¿Habría alguna forma de que en el
se debería tener un usuario por administrador...
Bien, en estos casos suele pasar lo que suele pasar, yo no he tocado,
yo no he hecho eso,...
Claro, si en esos casos tiramos de .bash_history (contando que no se
haya sido malo y se hayan borrado rastros), ahí aparecen los
comanditos, pero
mismo usuario para
administrar, cuando se debería tener un usuario por administrador...
Bien, en estos casos suele pasar lo que suele pasar, yo no he tocado,
yo no he hecho eso,...
Claro, si en esos casos tiramos de .bash_history (contando que no se
haya sido malo y se hayan borrado rastros
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jmramirez (mas_ke_na) escribió:
Buenas
En base a lo que comentaba. Puedes poner la hora de la ejecución
delante de cada comando del history así:
$ HISTTIMEFORMAT=%d/%m/%y %T
$ echo 'export HISTTIMEFORMAT=%d/%m/%y %T '
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jmramirez (mas_ke_na) escribió:
jmramirez (mas_ke_na) escribió:
Buenas
En base a lo que comentaba. Puedes poner la hora de la ejecución
delante de cada comando del history así:
$ HISTTIMEFORMAT=%d/%m/%y %T
$ echo 'export
Buenas,
El día 13 de julio de 2012 14:12, jmramirez (mas_ke_na)
mas_ke...@hotmail.com escribió:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jmramirez (mas_ke_na) escribió:
jmramirez (mas_ke_na) escribió:
Buenas
En base a lo que comentaba. Puedes poner la hora de la ejecución
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Buenas...
Ya me encontré. Para hacer lo que pide Ramses seria:
export sship=`cat /var/log/auth.log | grep ssh | grep Accepted | head -1
| gawk '{ print $11}'`
Y luego
export HISTTIMEFORMAT=`echo $sship %d/%m/%y %T `
Ahora ya sale
=
=YEcr
-END PGP SIGNATURE-
El único inconveniente que le veo es que si el usuario deja un espacio
antes del comando, este no se registra en .bash_history, entonces solo
queda registro de que estuvo, pero no qué hizo.
Saludos.
Sergio D. Gómez
Tostado (SF)
--
To UNSUBSCRIBE, email
Yo solo hago una pregunta..
Probaste con auditd ?
Asi seteas que archivos a auditar (configuraciones, binarios, etc)
# auditctl -w /etc/passwd -p war -k password-file
Y así, buscas al culpable:
# ausearch -f /etc/passwd -i | less
La salida del comando anterior, será similar a esta:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sergiogomez escribió:
El único inconveniente que le veo es que si el usuario deja un espacio
antes del comando, este no se registra en .bash_history, entonces solo
queda registro de que estuvo, pero no qué hizo.
Saludos.
Buenas
Eso
On Fri, 13 Jul 2012 15:33:07 +0200, jmramirez (mas_ke_na) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sergiogomez escribió:
El único inconveniente que le veo es que si el usuario deja un
espacio
antes del comando, este no se registra en .bash_history, entonces
solo
queda registro
Buenas,
El 13/07/2012, a las 14:55, jmramirez (mas_ke_na) mas_ke...@hotmail.com
escribió:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Buenas...
Ya me encontré. Para hacer lo que pide Ramses seria:
export sship=`cat /var/log/auth.log | grep ssh | grep Accepted | head -1
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ramses escribió:
Buenas
Veo que te ha gustado la idea, yo no tengo tanta experiencia como tú,
pero intento aportarte otra ayuda, a ver si así puedes solucionar el
tema del posible error al obtener sship:
Que posible error? a mi no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jmramirez (mas_ke_na) escribió:
Ramses escribió:
Buenas
Veo que te ha gustado la idea, yo no tengo tanta experiencia como tú,
pero intento aportarte otra ayuda, a ver si así puedes solucionar el
tema del posible error al obtener sship:
, este no se registra en .bash_history,
entonces solo
queda registro de que estuvo, pero no qué hizo.
Saludos.
Buenas
Eso es algo genérico del history, por lo que actúa como debe actuar.
Un saludo
Si, si. No digo que lo esté haciendo mal, sino que para la idea de
saber quién hizo
El Fri, 13 Jul 2012 12:44:59 +0200, Ramses II escribió:
(...)
¿Habría alguna forma de que en el .bash_history anteponga/postponga a
cada comando la IP de la Sesión que lo ejecutó?
Pues no lo sé... pero sí podrías hacer algo sencillo que es activar la
variable HISTTIMEFORMAT para registrar la
Buenas,
Enviado desde mi Móvil
El 13/07/2012, a las 18:40, Camaleón noela...@gmail.com escribió:
El Fri, 13 Jul 2012 12:44:59 +0200, Ramses II escribió:
(...)
¿Habría alguna forma de que en el .bash_history anteponga/postponga a
cada comando la IP de la Sesión que lo ejecutó?
Pues
it is kind of weird when i checked my .bash_history, it is empty.
#set give me
HISTFILESIZE=500
HISTSIZE=500
right now it work normal. after my last login it is not zero size anymore.
what i want to ask is, if the file (.bash_history) automatically empty
after the filesize reach 500KB
On 2009-08-13 10:00 +0200, paragasu wrote:
it is kind of weird when i checked my .bash_history, it is empty.
Did your computer crash recently? Some filesystems (e.g. ext4 before
kernel 2.6.30) might cause empty files under some conditions.
#set give me
HISTFILESIZE=500
HISTSIZE=500
svenj...@gmx.de wrote:
On 2009-08-13 10:00 +0200, paragasu wrote:
it is kind of weird when i checked my .bash_history, it is empty.
Did your computer crash recently? Some filesystems (e.g. ext4 before
kernel 2.6.30) might cause empty files under some conditions.
#set give me
HISTFILESIZE=500
I've been going thru a number of bash related web sites looking for the
way to eliminate duplicates in ~/.bash_history. So far I've turned up
export HISTCONTROL=ignoredups
export HISTCONTROL=erasedups
awk '!x[$0]++' .bash_history .bash.tmp mv -f .bash.tmp .bash_history
export HISTCONTROL
On Wed, Nov 26, 2008 at 5:28 PM, Robert Holtzman [EMAIL PROTECTED] wrote:
I've been going thru a number of bash related web sites looking for the way
to eliminate duplicates in ~/.bash_history. So far I've turned up
export HISTCONTROL=ignoredups
export HISTCONTROL=erasedups
awk '!x[$0
On Wednesday 2008 November 26 16:28, Robert Holtzman wrote:
I've been going thru a number of bash related web sites looking for the
way to eliminate duplicates in ~/.bash_history. So far I've turned up
I use:
export HISTCONTROL=ignoredups:erasedups
My .bash_history doesn't have any adjacent
Am 2008-11-26 15:28:47, schrieb Robert Holtzman:
I've been going thru a number of bash related web sites looking for the
way to eliminate duplicates in ~/.bash_history. So far I've turned up
export HISTCONTROL=ignoredups
export HISTCONTROL=erasedups
awk '!x[$0]++' .bash_history .bash.tmp
On Wed, 26 Nov 2008, Boyd Stephen Smith Jr. wrote:
On Wednesday 2008 November 26 16:28, Robert Holtzman wrote:
I've been going thru a number of bash related web sites looking for the
way to eliminate duplicates in ~/.bash_history. So far I've turned up
I use:
export HISTCONTROL
I got the above message last night from chkrootkit. I haven't touched
my /root/.bash_history. Are there any programs that modify this?
There's no other evidence of a break-in.
I've confirmed that this file has zero size:
# cd
debian:~# ls -l .bash_history
-rw--- 1 root root 0 Oct 28 08:03
On Tuesday 28 October 2008, Robert Schmidli
[EMAIL PROTECTED] wrote about 'Chkrootkit
reports Warning: `//root/.bash_history' file size is zero':
I got the above message last night from chkrootkit. I haven't touched
my /root/.bash_history. Are there any programs that modify this?
bash
lineas del bash_history y no hay forma de saber que es lo que
estubieron haciendo. Por suerte, para dejarlo todo intacto, la maquina
Xen fue apagada con un Destroy, así que ahora hay la oportunidad de
hacer un analisis forense, lo que pasa esque no tengo ningun
conocimiento sobre el tema
Muy buenas listeros,
este fin de semana entraron en mi servidor de pruevas (la seguridad
era de 'estar por casa'), presuntamente entraron para perpetar un
ataque contra otras maquinas, lo malo esque borraron las últimas
lineas del bash_history y no hay forma de saber que es lo que
estubieron
bash_history y no hay forma de saber que es lo que
estubieron haciendo. Por suerte, para dejarlo todo intacto, la maquina
Xen fue apagada con un Destroy, así que ahora hay la oportunidad de
hacer un analisis forense, lo que pasa esque no tengo ningun
conocimiento sobre el tema :( ¿Alguien podria
Marc Aymerich escribió:
Muy buenas listeros,
este fin de semana entraron en mi servidor de pruevas (la seguridad
era de 'estar por casa'), presuntamente entraron para perpetar un
ataque contra otras maquinas, lo malo esque borraron las últimas
lineas del bash_history y no hay forma de saber que
bash_history y no hay forma de saber que es lo que
estubieron haciendo. Por suerte, para dejarlo todo intacto, la maquina
Xen fue apagada con un Destroy, así que ahora hay la oportunidad de
hacer un analisis forense, lo que pasa esque no tengo ningun
conocimiento sobre el tema :( ¿Alguien podria orientarme en
On Mon, 2008-09-08 at 23:58 +0200, nx wrote:
Hola, por mi experiencia pienso que mas que borrar las últimas líneas
del .bash_history lo que han hecho habrá sido un unset $HISTFILE, es
más
rápido y más limpio y no es posible su recuperación.
Uff! no sabía eso, que pasada!
Hay alguna forma
del bash_history y no hay forma de saber que es lo que
estubieron haciendo. Por suerte, para dejarlo todo intacto, la maquina
Xen fue apagada con un Destroy, así que ahora hay la oportunidad de
hacer un analisis forense, lo que pasa esque no tengo ningun
conocimiento sobre el tema :( ¿Alguien podria
.
I have seen this today too, with my normal user account under X (debian
lenny | kernel 2.6.22.1). I use a crypted ext3 file system.
I worked in Eterm, and suddenly my history of the Eterm session was cut
off (only the last 500 commands | LIMIT of the bash_history is 50.000)
I think that Eterm
hey,
(i'm using debian unstable )
i am totally confused. suddenly, my .bash_history file for root did not
exist
anymore. now, i've been checking for rootkits, sniffers, listening ports and
all that, and did not find anything suspicious. is it possible, that the
file
could have been
Hi Anna.
Anna Machens, 08.07.2007 15:48:
(i'm using debian unstable )
i am totally confused. suddenly, my .bash_history file for root did not
exist
anymore.
That’s really odd; I experienced the same thing yesterday. Suddenly there was no
history anymore but since then, the file has been
Hi Anna.
Anna Machens, 08.07.2007 15:48:
(i'm using debian unstable )
i am totally confused. suddenly, my .bash_history file for root did not
exist
anymore.
That’s really odd; I experienced the same thing yesterday. Suddenly
there was no
history anymore but since
Eduard Bloch wrote:
Hi Anna.
Anna Machens, 08.07.2007 15:48:
(i'm using debian unstable )
i am totally confused. suddenly, my .bash_history file for root did not
exist
anymore.
That’s really odd; I experienced the same thing yesterday. Suddenly
there was no
history anymore
Quoting Eduard Bloch [EMAIL PROTECTED]:
I have seen this several times in the past, still having no idea how
this happens. For a while I suspected bash_completion but I think I
saw this also without bash_completion. Finally I am suspecting the
filesystem journaling doing weird
Hello,I'm running sarge.I rebooted this morning and root's bash history disappeared. I have a mail from a chkrootkit run by cron just before the reboot, and this doesn't flag it up, but a manual chkrootkit run just after the reboot did - that's how I discovered it. I can't see anything suspicious
Oops; sorry about the line-length.
' in
'man bash'.
I assume that my .bash_history gets converted to binary at some point by
bash. I can see that bash is using .bash_history now, but it's not clear
why the file should become binary on my system.
Adam
anoop.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
C. Chad Wallace on 22/11/05 02:38, wrote:
Stephen Rueger wrote:
Adam Hardy [EMAIL PROTECTED] writes:
This used to work until recently when I found that the .bash_history
had been transformed into a data file, instead of the ASCII text that
I was used to.
How exactly did you find that out
On (20/11/05 21:41), Ralph Katz wrote:
On 11/20/2005 05:20 PM, Adam Hardy wrote:
I rely on .bash_history alot to remind me what command syntax to use - I
don't scroll back thro the history with the up button, I just grep the
.bash_history file for the command I want to run.
This used
On Sun, 2005-11-20 at 23:45 +, Oliver Lupton wrote:
On Sun, 20 Nov 2005 22:17:59 +
Adam Hardy [EMAIL PROTECTED] wrote:
I rely on .bash_history alot to remind me what command syntax to use - I
don't scroll back thro the history with the up button, I just grep the
.bash_history
Clive Menzies on 21/11/05 10:23, wrote:
On (20/11/05 21:41), Ralph Katz wrote:
On 11/20/2005 05:20 PM, Adam Hardy wrote:
I rely on .bash_history alot to remind me what command syntax to use - I
don't scroll back thro the history with the up button, I just grep the
.bash_history file
On Mon, Nov 21, 2005 at 10:00:33PM +, Adam Hardy wrote:
thanks for the tips about C-r Is there some sort of documentation on this?
I'd
like to see how much history it keeps. It's a seperate program from history,
right?
HISTSIZE
The number of commands to remember
the command from
the history list.
OK thanks.
I assume that my .bash_history gets converted to binary at some point by
bash. I can see that bash is using .bash_history now, but it's not clear
why the file should become binary on my system.
Adam
--
To UNSUBSCRIBE, email to [EMAIL
Adam Hardy [EMAIL PROTECTED] writes:
This used to work until recently when I found that the .bash_history had
been transformed into a data file, instead of the ASCII text that I was
used to.
How exactly did you find that out? If it's merely because grep says
something like binary file
Stephen Rueger wrote:
Adam Hardy [EMAIL PROTECTED] writes:
This used to work until recently when I found that the .bash_history had
been transformed into a data file, instead of the ASCII text that I was
used to.
How exactly did you find that out? If it's merely because grep says
something
I rely on .bash_history alot to remind me what command syntax to use - I
don't scroll back thro the history with the up button, I just grep the
.bash_history file for the command I want to run.
This used to work until recently when I found that the .bash_history had
been transformed
On Sun, 20 Nov 2005 22:17:59 +
Adam Hardy [EMAIL PROTECTED] wrote:
I rely on .bash_history alot to remind me what command syntax to use - I
don't scroll back thro the history with the up button, I just grep the
.bash_history file for the command I want to run.
This used to work until
On 11/20/2005 05:20 PM, Adam Hardy wrote:
I rely on .bash_history alot to remind me what command syntax to use - I
don't scroll back thro the history with the up button, I just grep the
.bash_history file for the command I want to run.
This used to work until recently when I found
Hallo
Der mc produziert nach beenden mit F10 immer komische Steuerzeichen in
meine bash_history.
beispiel:
PROMPT_COMMAND='pwd7;kill -STOP $$'
cd `echo -e '\057'`
PROMPT_COMMAND='pwd7;kill -STOP $$'
Kann man das abstellen?
Gruß Florian
--
Haeufig gestellte Fragen und Antworten (FAQ):
http
* Florian (flobee) [EMAIL PROTECTED] [05-05-05 18:57]:
Hallo
Der mc produziert nach beenden mit F10 immer komische Steuerzeichen in
meine bash_history.
beispiel:
PROMPT_COMMAND='pwd7;kill -STOP $$'
cd `echo -e '\057'`
PROMPT_COMMAND='pwd7;kill -STOP $$'
Kann man das abstellen
export HISTIGNORE=*PROMPT*:[ ]cd*
^^
Sorry, da fehlt ein ''
--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail
On Thu, May 05, 2005 at 06:57:41PM +0200, Florian (flobee) wrote:
Der mc produziert nach beenden mit F10 immer komische Steuerzeichen in
meine bash_history.
beispiel:
PROMPT_COMMAND='pwd7;kill -STOP $$'
cd `echo -e '\057'`
PROMPT_COMMAND='pwd7;kill -STOP $$'
Machte meiner auch, sobald ich
Dirk Salva wrote:
On Thu, May 05, 2005 at 06:57:41PM +0200, Florian (flobee) wrote:
Der mc produziert nach beenden mit F10 immer komische Steuerzeichen in
meine bash_history.
beispiel:
PROMPT_COMMAND='pwd7;kill -STOP $$'
cd `echo -e '\057'`
PROMPT_COMMAND='pwd7;kill -STOP $$'
Machte meiner auch
Bonjour, bonsoir
En voulant chercher dans l'historique du shell de mon super utilisateur, je
me suis rendu compte que son bash_history était à poil. Il s'agit bien d'un
fichier régulier, pas un lien vers /dev/null.
Ma sarge est à jour (plus exactement, de la veille ;).
Pensez vous que je devrais
On Fri, 2003-11-07 at 13:45, Mike Egglestone wrote:
Hi,
My server was trojaned recently, not sure how.
It looks like /bin/ps was modified or replaced with
a trojan.
The /root/.bash_history file is set to this:
chsslx1:~# ls -la .bash_history
-rw-r--r--1 root root0 Nov
Hi,
My server was trojaned recently, not sure how.
It looks like /bin/ps was modified or replaced with
a trojan.
The /root/.bash_history file is set to this:
chsslx1:~# ls -la .bash_history
-rw-r--r--1 root root0 Nov 7 05:31 .bash_history
and I can't edit it or delete
Mike Egglestone wrote:
Hi,
My server was trojaned recently, not sure how.
It looks like /bin/ps was modified or replaced with
a trojan.
The /root/.bash_history file is set to this:
chsslx1:~# ls -la .bash_history
-rw-r--r--1 root root0 Nov 7 05:31 .bash_history
and I can't
Hello
Mike Egglestone ([EMAIL PROTECTED]) wrote:
My server was trojaned recently, not sure how.
It looks like /bin/ps was modified or replaced with
a trojan.
The /root/.bash_history file is set to this:
chsslx1:~# ls -la .bash_history
-rw-r--r--1 root root0 Nov 7 05
Quoting Andreas Janssen [EMAIL PROTECTED]:
Maybe the file is immutable. Check with
lsattr .bash_history
You can use chattr to change it:
chattr -i .bash_history
Yes, that was it. It had a bunch of those permissions set.
I chattr'd them all to off, and the file returned to normal.
Thank
On Fri, Nov 07, 2003 at 10:45:32AM -0800, Mike Egglestone wrote:
Hi,
My server was trojaned recently, not sure how.
It looks like /bin/ps was modified or replaced with
a trojan.
Out of curiosity--how can you tell?
The /root/.bash_history file is set to this:
chsslx1:~# ls -la
Quoting J. Bruce Fields [EMAIL PROTECTED]:
On Fri, Nov 07, 2003 at 10:45:32AM -0800, Mike Egglestone wrote:
Hi,
My server was trojaned recently, not sure how.
It looks like /bin/ps was modified or replaced with
a trojan.
Out of curiosity--how can you tell?
I could tell because the ps
Hi,
I use Debian unstable. After booting up the machine in the morning, I
found that root's .bash_history file is missing.
Suspecting a break-in, I searched for any other traces, examined all
/var/log/* files thoroughly, did chkrootkit, tried to locate any
suspicious-looking files, processes
Hallo,
nicht zum ersten Mal ist meine /root/.bash_history leer. Das letzte
Mal liegt allerdings schon lange zurück. chrootkit (sid) hat davon
abgesehen auch nichts unauffälliges entdeckt:
Searching for anomalies in shell history files... Warning:
`//root/.bash_history' file size is zero
Mon fichier .bash_history est créé avec les droits rw- --- --- or j'ai un
umask de 022, comment puis je faire pour changer celà pour tous les
utilisateurs actuels et à venir ?
La solution chmod -R ... ne me plaît pas ...
-
/° Eric Berthomier
(V)_
Le Tue, 19 Feb 2002 à 11:45:25AM +0100, Eric BERTHOMIER a écrit :
Salut,
Mon fichier .bash_history est créé avec les droits rw- --- --- or j'ai un
Ce fichier n'aurait pas ces droits là par défaut pour que les données
des utilisateurs ne soient visibles que par eux par hasard ?? Ca ferait
pas
Le but est simplement que le serveur WINS puisse sauvegarder sans faire de
message d'erreur sur ce genre de fichiers ...
Le Tue, 19 Feb 2002 à 12:20:11PM +0100, Eric BERTHOMIER a écrit :
Le but est simplement que le serveur WINS puisse sauvegarder sans faire de
message d'erreur sur ce genre de fichiers ...
Donc tu cherches à abaisser le niveau de sécurité de système au niveau
d'un système Winxx ... ya pas
consulta 1
bas_history: un compañero y yo manejamos un linux potato, pero me
rompe los esquemas que se ande fijando en el bash_history a ver lo
que hago o no.(Les aseguro que no es con el animo de aprender)
Pregunta: ¿Como puedo hacer para que no quede nada en el
bash_history?
Alguna sugerencia
On Wed, Nov 21, 2001 at 05:32:37AM -0700, daniel cabello wrote:
consulta 1
bas_history: un compañero y yo manejamos un linux potato, pero me
rompe los esquemas que se ande fijando en el bash_history a ver lo
que hago o no.(Les aseguro que no es con el animo de aprender)
Pregunta: ¿Como
Bueno, si mal no recuerdo, lo que hacía en algún tiempo era borrar el
contenido del archivo .bash_history que puedes encontrar en tu home. Ya si
quieres, te creas un script que borre el contenido de este archivo, o que lo
reempleace con un espacio.
sale..
Ing. Francisco Rivera
ScotiaBank
El mié, 21-11-2001 a las 17:22, Francisco Rivera escribió:
Bueno, si mal no recuerdo, lo que hacía en algún tiempo era borrar el
contenido del archivo .bash_history que puedes encontrar en tu home. Ya si
quieres, te creas un script que borre el contenido de este archivo, o que lo
On Wed, 21 Nov 2001, Francisco Rivera wrote:
Bueno, si mal no recuerdo, lo que hacía en algún tiempo era borrar el
contenido del archivo .bash_history que puedes encontrar en tu home. Ya si
quieres, te creas un script que borre el contenido de este archivo, o que lo
reempleace con un
bash_history a ver lo
que hago o no.(Les aseguro que no es con el animo de aprender)
Pregunta: ¿Como puedo hacer para que no quede nada en el
bash_history?
Alguna sugerencia
PD: Puede ser que me este volviendo paranoico !!!
*** ***
La otra vez escuche algo de
Hola
bas_history: un compañero y yo manejamos un linux potato, pero me
rompe los esquemas que se ande fijando en el bash_history a ver lo
que hago o no.(Les aseguro que no es con el animo de aprender)
Pregunta: ¿Como puedo hacer para que no quede nada en el
bash_history?
Pues hay una variable de
PROTECTED]
To: debian-user@lists.debian.org
Sent: Sunday, October 22, 2000 12:16 AM
Subject: Re: bash_history
I think you can turn saving of the history on/off, see man bash:
...
HISTSIZE
The number of commands to remember in the command
history (see
Yes this is a typo! Do you have any answere of my questions?
- Original Message -
From: Moritz Schulte [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Friday, October 20, 2000 10:30 PM
Subject: Re: bash_history
Matthias Mann [EMAIL PROTECTED] writes:
Is there a bug in bash
in which command history is
saved (see HISTORY below). The default value is
ß/.bash_history. If unset, the command history is
not saved when an interactive shell exits.
HISTFILESIZE
The maximum number of lines contained
Hi people!
Is there a bug in bash (Debian 2.2.0 potato)? When i go as root into my
system the bash don´t save anything to /root/bash_history. Is this a bug or
default? If default, how can i configure my bash to save the history?
Have a nice day!
Matthias
Matthias Mann [EMAIL PROTECTED] writes:
Is there a bug in bash (Debian 2.2.0 potato)? When i go as root into my
system the bash don´t save anything to /root/bash_history.
Is this a typo? Bash's history should be in ~/.bash_history.
moritz
--
/* Moritz Schulte [EMAIL PROTECTED
Can someone help me figure out this
"/.bash_history" from my
computer that someone cracked into and did some
damage.
I'll probably re-install the box, but I'd like to
see what they did
before I destroy it. I've attached the
"/.bash_history".
Dzuy
w
ifconfig
ls -la
log
a 'cat .bash_history', but didn't delete it.
Maybe it's a forgery?
Comments, people?
Dzuy M. Nguyen wrote:
Can someone help me figure out this /.bash_history from my
computer that someone cracked into and did some damage.
I'll probably re-install the box, but I'd like to see what they did
if you run updatedb via cron (or run it from the shell by hand
recently) it'll tell you if you have any of the evil files
on your computer:
locate pscan
locate wuftp
locate bnc2
locate .shit
locate anatomy
locate kod
locate '/b$'
if you find
Dzuy M. Nguyen wrote:
Can someone help me figure out this /.bash_history from my
computer that someone cracked into and did some damage.
I'll probably re-install the box, but I'd like to see what they did
before I destroy it. I've attached the /.bash_history.
Let's cut it down some..
cc
the ports of the computers physically
connected on this LAN? Should I be concerned with the security of the
whole office now?
- Original Message -
From: w trillich [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Tuesday, May 02, 2000 6:58 PM
Subject: Re: bash_history from Cracked
Dzuy M. Nguyen wrote:
This linux box was plugged into the same LAN as our company NT Network.
It wasn't setup to access the NT Network or be involved in it. It just
get's
it's TCP/IP signal from the LAN.
And what about the internet connection? Are all of your NT boxes
connected directly to
Joey Hess wrote:
Let's cut it down some..
cc anatomy.c -o anatomy
cc kod.c -o kofd
cp kofd kod
rm kofd
According to google, kod and kofd are related to the oracle database.
It's possible this is a cooincidence, or he was using these names to try
to appear innocous (weird choices
1 - 100 of 107 matches
Mail list logo
