Hallo, Dear Linux-Friends, I found something curious in my Home Dir. : A file named ?$2@ and I could by no means delete it execpt with the mc. ?$2@ and with echo: ^W$2@ German text below, I dont speak very good english, but understand German,French and Englisch. You could relply in those Languages. Thank you in Advance ---German text---- Ich fand folgende Datei bei mir in $HOME: ?$2@ Sie liess sich nicht auf der Konsole (egal mit welcher Maskierung) sondern nur mit dem mc loeschen! Nach dem Loeschen mit dem mc musste ich im xterm folgende "Ausgabe" feststellen: (Ich hatte vom xterm aus den mc gestartet und nach Beenden des mc kehrte ich wieder in den xterm zurueck.) ich@rose:~> rm %!#%! .!#.! /!#/! &!#&! /!#/! C!#C! H!#H! E&#E& G!#G! F$#F$ [@#[@ C!#C! H&#H& E!#E! F##F# q<#q< ZC#ZC C!#G% F!#F! I(#I( x?#x? R!#R! :!#:! /!#/! 8!#8! /!#/! &!#&! )*#)* x:#x: %!#%! (-#(- w:#w: %!#*# ]>#]> y8#y8 ?$2@ (Es sollte wohl so einiges an Variablen-Inhalt geloescht werden) Wahrscheinlich war diese "Ausgabe" die Kommandofolge, die der mc mit der "Datei"?$2@ gemacht hat? P.S. mit dem Entfernen der "Datei"?$2@ war ja auch das mit nur echo sichtbare: ^W$2@ verschwunden. Die beiden Dateien ?$2@ und ^W$2@ stehen somit in einem Zusammenhang. Mir ist trotz Studium der man bash nicht klar was hier ablaeuft: 1. regulares Verhalten vom mc (temporaere Datei ? nach crash) 2.Bug des mc 3. Crackerkonstrukt?? -- # MfG Michael Maldener + Das beste Linux ist die Pluralitaet aller Linuxica ;)
/ 2003-11-06 13:47:31 +0100 \ Michael Maldener:
Hallo, Dear Linux-Friends,
I found something curious in my Home Dir. : A file named ?$2@
and I could by no means delete it execpt with the mc.
?$2@ and with echo: ^W$2@
ich@rose:~> rm %!#%! .!#.! /!#/! &!#&! /!#/! C!#C! H!#H! E&#E& G!#G! F$#F$ [@#[@ C!#C! H&#H& E!#E! F##F# q<#q< ZC#ZC C!#G% F!#F! I(#I( x?#x? R!#R! :!#:! /!#/! 8!#8! /!#/! &!#&! )*#)* x:#x: %!#%! (-#(- w:#w: %!#*# ]>#]> y8#y8 ?$2@
very nice :-)
P.S. mit dem Entfernen der "Datei"?$2@ war ja auch das mit nur echo sichtbare: ^W$2@ verschwunden.
Die beiden Dateien ?$2@ und ^W$2@ stehen somit in einem Zusammenhang.
Mir ist trotz Studium der man bash nicht klar was hier ablaeuft: 1. regulares Verhalten vom mc (temporaere Datei ? nach crash) 2.Bug des mc 3. Crackerkonstrukt??
maybe some "utf" file name, or a byproduct of some accidentally paste of binary data containing > onto some shell promt... man ls: -q, --hide-control-chars print ? instead of non graphic characters --show-control-chars show non graphic characters as-is (default unless program is `ls' and output is a terminal) and so on. Lars Ellenberg
Hallo Lars, thank you for your mail... Am Donnerstag, 6. November 2003 14:32 schrieb Lars Ellenberg:
ich@rose:~> rm %!#%! .!#.! /!#/! &!#&! /!#/! C!#C! H!#H! E&#E& G!#G! F$#F$ [@#[@ C!#C! H&#H& E!#E! F##F# q<#q< ZC#ZC C!#G% F!#F! I(#I( x?#x? R!#R! :!#:! /!#/! 8!#8! /!#/! &!#&! )*#)* x:#x: %!#%! (-#(- w:#w: %!#*# ]>#]> y8#y8 ?$2@
very nice :-)
Please ... What do you mean by 'nice' ?
maybe some "utf" file name, or a byproduct of some accidentally
Do you mean unicode ??
paste of binary data containing > onto some shell promt...
Thank you ... -- # MfG Michael Maldener + Das beste Linux ist die Pluralitaet aller Linuxica ;)
In addition to Lars' suggestions, I've also found "ls -b" to be helpful with files like this. Files with meta-chars in them can be hard to delete. Either escape the troublesome chars with a "\" or surround the whole filename with single quotes. For example: rm \?\$2@ rm '?#2@' Of course, hidden chars (like control chars) will make those fail. You can always do: rm -i *2* putting any <normal> char between the stars and then give "y" to the one to go away and n to the others to keep. For files that start with a leading "-", be sure to make the pattern "./*something*". That doesn't answer your question about bug or crack, but hopefully the contents of the file will help you determine that. Good Luck! Kevin Michael Maldener wrote:
Hallo, Dear Linux-Friends,
I found something curious in my Home Dir. : A file named ?$2@
and I could by no means delete it execpt with the mc.
?$2@ and with echo: ^W$2@
-----Original Message----- From: Kevin Brannen <kevin_brannen@stercomm.com> To: suse-security@suse.com Date: Thu, 06 Nov 2003 09:43:51 -0600 Subject: Re: [suse-security] BUG or CRACKER
In addition to Lars' suggestions, I've also found "ls -b" to be helpful with files like this.
Files with meta-chars in them can be hard to delete. Either escape the troublesome chars with a "\" or surround the whole filename with single quotes. For example:
rm \?\$2@ rm '?#2@'
Of course, hidden chars (like control chars) will make those fail. You can always do:
rm -i *2*
putting any <normal> char between the stars and then give "y" to the one to go away and n to the others to keep. For files that start with a leading "-", be sure to make the pattern "./*something*".
That doesn't answer your question about bug or crack, but hopefully the contents of the file will help you determine that.
Good Luck!
Kevin
Michael Maldener wrote:
Hallo, Dear Linux-Friends,
I found something curious in my Home Dir. : A file named ?$2@
and I could by no means delete it execpt with the mc.
?$2@ and with echo: ^W$2@
I have even used rm -i * to remove some stuborn files. But you need to be VERY carefull. Ken Schneider
Hello Kevin, thank you for your mail... I was able to delete the 'file' with the mc. but I am still very curious if these 'files' ?$2@ and with echo: ^W$2@ have a high danger potential WHEN THEY ARE DELETED. I mean or think they are VARIABLES. I should have looked with echo $?$2@ before deleting them.
In addition to Lars' suggestions, I've also found "ls -b" to be helpful with files like this.
Next time I will think of it.
Files with meta-chars in them can be hard to delete. Either escape the troublesome chars with a "\" or surround the whole filename with single quotes. For example:
rm \?\$2@ rm '?#2@'
Of course, hidden chars (like control chars) will make those fail. You can always do:
rm -i *2*
putting any <normal> char between the stars and then give "y" to the one to go away and n to the others to keep. For files that start with a leading "-", be sure to make the pattern "./*something*".
That doesn't answer your question about bug or crack, but hopefully the contents of the file will help you determine that.
Good Luck!
Kevin
Michael Maldener wrote:
Hallo, Dear Linux-Friends,
I found something curious in my Home Dir. : A file named ?$2@
and I could by no means delete it execpt with the mc.
?$2@ and with echo: ^W$2@
-- # MfG Michael Maldener + Das beste Linux ist die Pluralitaet aller Linuxica ;)
participants (4)
-
Ken Schneider -
Kevin Brannen -
Lars Ellenberg -
MALDENER.de＠t-online.de