andrey_chevron
asked on
read remote file without password
We have old Linux machine in remote office and I need to read one file in /user/leasing.txt . No passwords available- admin changed them before leaving :(
nmap output:
PORT STATE SERVICE VERSION
1080/tcp closed socks
2222/tcp open ssh OpenSSH 5.3 (protocol 2.0)
| ssh-hostkey:
| 1024 b4:35:5d:00:90:1c:2c:6f:cc :e2:0e:c3: 01:41:34:6 3 (DSA)
|_ 2048 83:0e:8b:dd:53:b2:ca:75:5c :5d:75:75: c5:5d:f8:2 5 (RSA)
2710/tcp closed sso-service
4662/tcp closed edonkey
6881/tcp closed bittorrent-tracker
6901/tcp closed jetstream
6969/tcp closed acmsoda
8181/tcp open http nginx 1.8.0
| http-methods: GET HEAD POST OPTIONS TRACE
| Potentially risky methods: TRACE
|_See http://nmap.org/nsedoc/scripts/http-methods.html
|_http-server-header: nginx/1.8.0
|_http-title: Site doesn't have a title (text/html; charset=UTF-8).
Device type: general purpose|WAP|storage-misc|l oad balancer|firewall
nmap output:
PORT STATE SERVICE VERSION
1080/tcp closed socks
2222/tcp open ssh OpenSSH 5.3 (protocol 2.0)
| ssh-hostkey:
| 1024 b4:35:5d:00:90:1c:2c:6f:cc
|_ 2048 83:0e:8b:dd:53:b2:ca:75:5c
2710/tcp closed sso-service
4662/tcp closed edonkey
6881/tcp closed bittorrent-tracker
6901/tcp closed jetstream
6969/tcp closed acmsoda
8181/tcp open http nginx 1.8.0
| http-methods: GET HEAD POST OPTIONS TRACE
| Potentially risky methods: TRACE
|_See http://nmap.org/nsedoc/scripts/http-methods.html
|_http-server-header: nginx/1.8.0
|_http-title: Site doesn't have a title (text/html; charset=UTF-8).
Device type: general purpose|WAP|storage-misc|l
If you're asking to gain access to a system that you don't have an account for then we cannot help you I'm afraid. Boot into single user mode is an option that is left as a last resort (and change root pwd).
ASKER
I don't have a physical access to the machine - so SUM is not an option.
No I don't have user name.
if you don't recognize nmap log - forget it .
No I don't have user name.
if you don't recognize nmap log - forget it .
>> if you don't recognize nmap log - forget it .
Nobody said we didn't understand nmap log, I'm just saying we cannot help you finding/exploiting weaknesses in nginx/1.8.0 or OpenSSH 5.3.
Nobody said we didn't understand nmap log, I'm just saying we cannot help you finding/exploiting weaknesses in nginx/1.8.0 or OpenSSH 5.3.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Best advice might be to get the new password(s) from the previous admin. It's very unethical to inhibit access in that way and potentially illegal. See perhaps the most famous similar example. Even if not classed under similar laws, a letter from a lawyer might be convincing.
What is it your showing us here?