@KuroSaru said:
maybe ******* and zip are related. uuuudddduh how can that be? MAN if only there was a way to know how.
I get the relationship, I’m past that point or missing an element of that point. Without trying to give anything away, I have a *** (the non-cli kind) connection and get a blank screen.
@GH05TCD said:
Is the grey screen a fault? Or am I not doing something right?
It’s expected depending on how you’re connecting. Fixable, just google a solution (there are other posts in this thread that discuss this in more detail than they should, just fyi)
Hi,
I’ve got a hint, that would really help me - sometimes machine sees a difference between localhost and 127.0.0.1…
I’ve been struggling with this, even though I knew exactly what is wrong with the machine.
I’ve read almost all the comments, i have the secret i think i understand what i should do but still i can’t continue! If someone want to p.m so i can tell him what i’m doing without spoiling will be great!
sorta agree with the guy above, rooted as well, pretty straight forward but if you haven’t done something like this before it could get result in loads of googling, feel free to hmu anytime as well
My first server :D, two interesting days.
The comments are rights, just enumerate the services and understand how they works, then using the file.
I learned a lot.
on my first scan, I found two open ports and two filtered ones (one even corresponding to a known and useful service - or at least I thought so). Problem is, I can’t find those two services anymore, they don’t show up in my scan. I tried resetting the box several times, nothing changed. Did I allucinate?
I was able to find a username by decoding the password backup. I thought of using it in *** but I can’t figure out the password (I found the pwd file but all the entries are simpy ‘*’). It was stated several times that no bruteforce is needed here, so…What am I missing?