LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Security (https://www.linuxquestions.org/questions/linux-security-4/)
-   -   Did he connect my pc to some server or something? (https://www.linuxquestions.org/questions/linux-security-4/did-he-connect-my-pc-to-some-server-or-something-4175609813/)

Abdulmalek97 07-13-2017 08:15 PM

Did he connect my pc to some server or something?
 
So basically this question is also a 100% newbie but it is more about security.

So I am following this ethical hacking course and things went wrong with installing Kali Linux and updating stuff, so the teacher offered to help me and he did. before he finished though, he wrote something that I believe began with "ad" and ended with conf ??!! not sure. he could see some view IPs and he changed an ip which started with 198.168 to one that starts with 200 and the local one 127.0.0.1 to one that starts with 255.255 and added one with 8.8.8 and so. What did he do here? did he hack me or connected my device to his? or to a server?

It might be a stupid question but i would like to know the answer. Thanks for you help already.

frankbell 07-13-2017 08:30 PM

It is almost impossible to reconstruct what your professor did, but it is possible to determine what the current situation is.

What is the output of

Code:

ip addr                or
ifconfig -a                and
traceroute 8.8.8.8

That information should help persons start answering your question. See man traceroute, man ip, or man ifconfig for more about those commands.

Be sure to surround the command output with "code" tags, which become available when you click the "Go Advanced" button beneath the "Quick Reply/Compost Post" window.

Timothy Miller 07-13-2017 09:16 PM

8.8.8.8 is Google DNS address, that one I know quite well.

frankbell 07-13-2017 09:20 PM

Quote:

8.8.8.8 is Google DNS address, that one I know quite well
True. It's almost never down, so it's good for a test.

I'm not necessarily a Google fan, but I will concede that, when Google builds something, it is usually works as promised. (It's the conditions that Google puts on that promise that sometimes give me pause.)

I'm not so interested in the final destination (8.8.8.8) as I am in what the route to it will reveal. That should give us a hint whether there are any side trips along the way.

Here's my traceroute to Google for comparison purposes.

Code:

$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max
  1  192.168.2.1  0.568ms  0.538ms  1.385ms
  2  10.5.48.1  8.936ms  7.680ms  15.973ms
  3  100.127.40.90  11.485ms  13.745ms  11.171ms
  4  172.22.51.66  9.522ms  8.002ms  8.979ms
  5  68.1.0.242  16.751ms  20.486ms  12.886ms
  6  98.182.1.74  14.674ms  13.101ms  14.013ms
  7  108.170.246.81  18.089ms  16.271ms  15.384ms
  8  216.239.49.197  29.396ms  15.514ms  38.011ms
  9  216.239.48.6  23.041ms  22.367ms  21.421ms
 10  209.85.251.61  21.872ms  36.849ms  25.166ms
 11  *  *  *
 12  8.8.8.8  22.113ms  22.294ms  26.889ms


Abdulmalek97 07-14-2017 01:52 AM

1 Attachment(s)
Quote:

Originally Posted by frankbell (Post 5734664)
It is almost impossible to reconstruct what your professor did, but it is possible to determine what the current situation is.

What is the output of

Code:

ip addr                or
ifconfig -a                and
traceroute 8.8.8.8

That information should help persons start answering your question. See man traceroute, man ip, or man ifconfig for more about those commands.

Be sure to surround the command output with "code" tags, which become available when you click the "Go Advanced" button beneath the "Quick Reply/Compost Post" window.

This is it:

Abdulmalek97 07-14-2017 01:54 AM

I am asking this and i am more curious because, in his videos on Udemy, he does not mention this but he did it to me. It might be harmless, just wanted to check from someone who has some experience.

Trihexagonal 07-14-2017 12:14 PM

Quote:

Originally Posted by Abdulmalek97 (Post 5734655)
he could see some view IPs and he changed an ip which started with 198.168 to one that starts with 200 and the local one 127.0.0.1 to one that starts with 255.255

127.0.0.1 is localhost, the hostname of your computer.

More likely than not the number you saw was 192.168.1.x, your address on the subnet, and 255.255.255.x is the netmask.

https://www.adminsub.net/ipv4-subnet.../255.255.255.0

It's an "ethical" hacking class. Your professor "probably" wasn't setting you up to be exploited, but safety first in all things computer related. ;)

Abdulmalek97 07-14-2017 12:23 PM

Quote:

Originally Posted by Trihexagonal (Post 5734908)
127.0.0.1 is localhost, the hostname of your computer.

More likely than not the number you saw was 192.168.1.x, your address on the subnet, and 255.255.255.x is the netmask.

https://www.adminsub.net/ipv4-subnet.../255.255.255.0

It's an "ethical" hacking class. Your professor "probably" wasn't setting you up to be exploited, but safety first in all things computer related. ;)


I also thought the same. But when I watched all the settings up videos and saw that he has not mentioned this, I got a bit skeptical. Still curious why he would do it to my laptop but not to others?

Trihexagonal 07-14-2017 12:30 PM

Quote:

Originally Posted by Abdulmalek97 (Post 5734916)
Still curious why he would do it to my laptop but not to others?

Quote:

Originally Posted by Abdulmalek97 (Post 5734655)
So I am following this ethical hacking course and things went wrong with installing Kali Linux and updating stuff, so the teacher offered to help me...

Did anyone else have the same problems you did and require his assistance?

You could always run netstat -an and see if you have any suspicious listening ports or connections. It just doesn't sound like he did anything nefarious.

wpeckham 07-14-2017 12:32 PM

Quote:

Originally Posted by Abdulmalek97 (Post 5734916)
I also thought the same. But when I watched all the settings up video and saw that he has not mentioned this, I got a bit skeptical. Still curious why he would do it to my laptop but not to others?

A video covering all of Linux networking, troubleshooting, resolution, and routing issues would be at least several days long. I suspect there were errors, and he corrected them to where you SHOULD have been had there been no errors.

It is unfortunate that he did not provide explanation as he went along, it was a perfect teaching/learning opportunity. If he was pressed for time and resources it is not unreasonable to jsut "fix the problem" without taking time to explain, just unfortunate.

Abdulmalek97 07-14-2017 12:47 PM

Quote:

Originally Posted by Trihexagonal (Post 5734922)
Did anyone else have the same problems you did and require his assistance?

You could always run netstat -an and see if you have any suspicious listening ports or connections. It just doesn't sound like he did anything nefarious.

I am sure some people did. I ran it but as a noob, i wouldn't even know how to read these information at the moment.

Abdulmalek97 07-14-2017 12:48 PM

Quote:

Originally Posted by wpeckham (Post 5734924)
A video covering all of Linux networking, troubleshooting, resolution, and routing issues would be at least several days long. I suspect there were errors, and he corrected them to where you SHOULD have been had there been no errors.

It is unfortunate that he did not provide explanation as he went along, it was a perfect teaching/learning opportunity. If he was pressed for time and resources it is not unreasonable to jsut "fix the problem" without taking time to explain, just unfortunate.

I agree

Trihexagonal 07-14-2017 01:57 PM

Quote:

Originally Posted by Abdulmalek97 (Post 5734930)
I ran it but as a noob, i wouldn't even know how to read these information at the moment.

Once you log off from the site let your computer set idle for a few minutes till all the connections time out. Then run:

Code:

netstat -an
Take note of what posts are listening, which will be designated by the *.* symbol. Also look at what, if any, connections are made to your computer, mark down the #IP and run it at someplace like network-tools.com to see what they resolve to. Things like Akamai are nothing to worry about.

You can reference what might be suspicious ports compared to those of know trojans or services like X-Windows (6000:6010}. There should be a /etc/services file in your distro, there is in BSD, to look up what services use which ports.

If you're running a firewall that carries out Stateful Packet Inspection it should drop any connections not initiated by your machine anyway, and you should be able to block any open ports at the firewall if it worries you.

Now that I've probably scared you worse than you were before... :p I really would be surprised if anything is out of order due to something he did, but I'm not infallible.

Abdulmalek97 07-14-2017 03:00 PM

Quote:

Originally Posted by Trihexagonal (Post 5734955)
Once you log off from the site let your computer set idle for a few minutes till all the connections time out. Then run:

Code:

netstat -an
Take note of what posts are listening, which will be designated by the *.* symbol. Also look at what, if any, connections are made to your computer, mark down the #IP and run it at someplace like network-tools.com to see what they resolve to. Things like Akamai are nothing to worry about.

You can reference what might be suspicious ports compared to those of know trojans or services like X-Windows (6000:6010}. There should be a /etc/services file in your distro, there is in BSD, to look up what services use which ports.

If you're running a firewall that carries out Stateful Packet Inspection it should drop any connections not initiated by your machine anyway, and you should be able to block any open ports at the firewall if it worries you.

Now that I've probably scared you worse than you were before... :p I really would be surprised if anything is out of order due to something he did, but I'm not infallible.

Haha. No worries. thanks. I will check that

Trihexagonal 07-14-2017 03:10 PM

Quote:

Originally Posted by Abdulmalek97 (Post 5734975)
Haha. No worries. thanks. I will check that

You're welcome. Be sure to let us know how it turns out and if you have any questions.


All times are GMT -5. The time now is 03:29 PM.