 |
| Source: scrapperduncan |
I really don't believe but the support gave me the string... It's:
hipserv2_hitachigph
Now building the string to connect:
ssh admin_hipserv2_hitachigph_XXXX-XXXX-XXXX-XXXX@GCONNECT.local
G-Connect version 10.0.x
admin_hipserv2_hitachigph_XXX@gconnect.local's password:
G-Connect version 10.0.x
admin_hipserv2_hitachigph_XXX@gconnect.local's password:
-bash-3.2$
Wow!!! I'm in!! Connected!!
Now let's try to get root:
ssh admin_hipserv2_hitachigph_XXXX-XXXX-XXXX-XXXX@GCONNECT.local
G-Connect version 10.0.x
admin_hipserv2_hitachigph_XXX@gconnect.local's password:
-bash-3.2$G-Connect version 10.0.x
admin_hipserv2_hitachigph_XXX@gconnect.local's password:
-bash-3.2$ sudo -s
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Password:
audit_log_user_command(): Connection refused
bash-3.2#
ROOT ACCESSED !!!! Now the game begins !!!
OBS: The passwords are same registered in inicial G-CONNECT setup.
OBS2 : Don't mind about the message - audit_log_user_command(): Connection refused
Let's check the Firefly password:
bash-3.2# cat /etc/mt-daapd.conf | grep admin_pw
# admin_pw (required)
admin_pw = c03jkf4dj
Next Post... Back to oddities list... Let's handle the issue number one !!!!