From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] OT: Login incorrect
Date: Fri, 29 Jul 2005 11:28:15 +0000 (UTC) [thread overview]
Message-ID: <loom.20050729T131634-114@post.gmane.org> (raw)
I have a problem.
I have an embedded device that does not let me gain access.
ssh is block, but I can telnet into the port, only to
be denied access.
<snip>
telnet 192.168.32.49
Trying 192.168.32.49...
Connected to 192.168.32.49.
Escape character is '^]'.
VxWorks login:
<snip>
nothing I try works for an account name
and corresponding password. I'm not sure
if this version (is acually Vxworks ?) is
based on their BSD or Linux based RTOS....
So I need a brute force method to gain access.
It allows about 8 login attempts (60 sec) before resetting:
<snip>
VxWorks login:
Login timed out after 60 seconds!
Connection closed by foreign host.
<snip>
Any suggestions to automate this brute force effort?
Maybe a fancy protocol-profiler program to look at the
results of (ICMP) packets[it answers pings] to determine
the actual underlying OS would be a good first step?
Other ideas/methods to profile the (RT)OS are of interests to me.
James
--
gentoo-user@gentoo.org mailing list
reply other threads:[~2005-07-29 11:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20050729T131634-114@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox