Follow us on Twitter!
The measure of a mans life is not how well he dies, but how well he lives.
Thursday, April 24, 2014
Navigation
Home
HellBoundHackers Main:
HellBoundHackers Find:
HellBoundHackers Information:
Learn
Communicate
Submit
Shop
Challenges
HellBoundHackers Exploit:
HellBoundHackers Programming:
HellBoundHackers Think:
HellBoundHackers Track:
HellBoundHackers Patch:
HellBoundHackers Other:
HellBoundHackers Need Help?
Other
Members Online
Total Online: 32
Guests Online: 25
Members Online: 7

Registered Members: 82895
Newest Member: kevy90
Latest Articles
View Thread

HellBound Hackers | Challenges | Basic

Author

For those who have problems with Basic 6


Member

Your avatar

Posts:
Location:
Joined: 01.01.70
Rank:
Guest
Posted on 28-12-07 14:30
Hi guys, i'm really really tired of trying multiple answers to basic 6, i know my commands are right but it's just the syntax maybe or some punctuation error, can i pm somebody all my guesses in order he/she could tell me what am i doing wrong??

Thanks!

[EDIT] Oh i passed this challenge, and it's really frustrating to see that message every time i hit submit... so, without posting any spoiler, to all of you who have the same problem as i had, just a few tips:

-Don't forget the $.
-Put a SPACE after the $ symbol.
-Don't put ./ nor / before the directory name.
-Don't put " ".

I hope this will end with the problems of this mission.

SiPOX




Edited by on 28-12-07 14:40
Author

RE: For those who have problems with Basic 6


Member

Your avatar

Posts:
Location:
Joined: 01.01.70
Rank:
Guest
Posted on 16-01-08 04:40
Thank you very much! This helped a lot for me. I got pretty frustrated when I knew I had the right linux syntax. Turns out it was the space that I needed between $ and the commands!:happy:
Author

RE: For those who have problems with Basic 6


Member

Your avatar

Posts:
Location:
Joined: 01.01.70
Rank:
Guest
Posted on 21-01-08 16:37
*whew* so that that's it. This doesn't really seem realistic, though, does it? In my experiences with linux/unix, I've never had to put the $ in, because that's part of the bash. Is there ever a time when I have to do this?
Author

RE: parsing

mickimaus
Member



Posts: 7
Location: /etc/shadow
Joined: 03.08.06
Rank:
Guest
Posted on 17-03-08 20:44
don't know why I should use a $, just because of the comment in the text...
I would concat it with && or use something like ls *.php | xargs chmod ... && rm ... ....
but I know what pain it is to parse strings... sorry, but if this challange has not the goal to teach me how to bypass php forms I have no time to figure out what pattern the linux command has to be formatted to...

btw. does the $ stand for a parameter the bash/sh gets passed?
from what I read here it does not really matter?
Author

RE: For those who have problems with Basic 6

spyware
Member



Posts: 4192
Location:
Joined: 14.04.07
Rank:
God
Warn Level: 90
Posted on 17-03-08 20:48
I believe the dollar sign indicates a new line full of commands waiting to be executed. In most linux builds this dollar sign is there always, in this challenge you have to put it there.

The space however, is technically incorrect. At least, I think it is. I am merely a simple Windows user. I cannot be too sure about the exact technical command-line implementations in the various linux shells.



img507.imageshack.us/img507/3580/spynewsig3il1.png
"The chowner of property." - Zeph
[small]
Widespread intellectual and moral docility may be convenient for leaders in the short term,
but it is suicidal for nations in the long term.
- Carl Sagan
[center]�Since the grid is inescapable, what were the earlier lasers about? Does the corridor have a sense of humor?� - Ebert[/ce
Author

RE: the dollar

mickimaus
Member



Posts: 7
Location: /etc/shadow
Joined: 03.08.06
Rank:
Guest
Posted on 18-03-08 09:39
No, the space is technically correct. Most linux systems I came accross hab something like
user@hostname:/path/to$_
user@hostname:/path/to#_

where _ represents the space
and # represets root shell

if you write interactive scripts with "expect", you have even to expect the space in your expecting pattern. But on normal shell interaction, you don't have to write the space. Its already at the prompt to separete your command from the bash prompt.

anyone is welcome to correct me if I am wrong.