Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #687549 > unrolled thread
| Started by | Farley Flud <ff@linux.rocks> |
|---|---|
| First post | 2025-03-16 15:19 +0000 |
| Last post | 2025-03-17 19:28 +0000 |
| Articles | 20 on this page of 55 — 16 participants |
Back to article view | Back to comp.os.linux.advocacy
Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-16 15:19 +0000
Re: Please List Your Open Ports Physfitfreak <physfitfreak@gmail.com> - 2025-03-16 13:50 -0500
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-16 19:52 +0000
Re: Please List Your Open Ports Physfitfreak <physfitfreak@gmail.com> - 2025-03-16 17:38 -0500
Re: Please List Your Open Ports Farley Flud <fsquared@fsquared.linux> - 2025-03-17 10:37 +0000
Re: Please List Your Open Ports Physfitfreak <physfitfreak@gmail.com> - 2025-03-17 13:28 -0500
Re: Please List Your Open Ports Physfitfreak <physfitfreak@gmail.com> - 2025-03-17 13:34 -0500
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-17 19:09 +0000
Re: Please List Your Open Ports Physfitfreak <physfitfreak@gmail.com> - 2025-03-17 16:06 -0500
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-17 21:38 +0000
Re: Please List Your Open Ports Physfitfreak <physfitfreak@gmail.com> - 2025-03-17 16:55 -0500
Re: Please List Your Open Ports candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-03-27 20:00 +0000
Re: Please List Your Open Ports Joel <joelcrump@gmail.com> - 2025-03-27 16:13 -0400
Re: Please List Your Open Ports Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-03-30 13:49 +0000
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-30 17:16 +0000
Re: Please List Your Open Ports Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-03-30 21:50 +0000
Re: Please List Your Open Ports candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-03-31 17:50 +0000
Re: Please List Your Open Ports Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-04-06 08:33 +0000
Re: Please List Your Open Ports Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-04-06 09:40 -0400
Re: Please List Your Open Ports Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-03-16 19:54 +0100
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-16 19:48 +0000
Re: Please List Your Open Ports Marco Moock <mm@dorfdsl.de> - 2025-03-17 17:16 +0100
Re: Please List Your Open Ports Farley Flud <fsquared@fsquared.linux> - 2025-03-17 16:32 +0000
Re: Please List Your Open Ports Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-03-21 21:42 +0000
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-22 10:48 +0000
Re: Please List Your Open Ports Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-03-22 11:13 +0000
Re: Please List Your Open Ports rbowman <bowman@montana.com> - 2025-03-17 20:45 +0000
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-17 21:11 +0000
Re: Please List Your Open Ports Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-18 05:31 +0000
Re: Please List Your Open Ports Farley Flud <fsquared@fsquared.linux> - 2025-03-18 11:27 +0000
Re: Please List Your Open Ports vallor <vallor@cultnix.org> - 2025-03-18 23:31 +0000
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-19 15:10 +0000
Re: Please List Your Open Ports vallor <vallor@cultnix.org> - 2025-03-19 23:37 +0000
Re: Please List Your Open Ports Andy Gerald <andy@yohoo.com> - 2025-03-20 02:30 -0400
Re: Please List Your Open Ports vallor <vallor@cultnix.org> - 2025-03-20 17:08 +0000
Re: Please List Your Open Ports Andy Gerald <andy@yohoo.com> - 2025-03-20 13:28 -0400
Re: Please List Your Open Ports vallor <vallor@cultnix.org> - 2025-03-20 17:46 +0000
Re: Please List Your Open Ports Andy Gerald <andy@yohoo.com> - 2025-03-20 14:19 -0400
Re: Please List Your Open Ports vallor <vallor@cultnix.org> - 2025-03-20 19:23 +0000
Re: Please List Your Open Ports Andy Gerald <andy@yohoo.com> - 2025-03-21 07:12 -0400
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-21 19:11 +0000
Re: Please List Your Open Ports vallor <vallor@cultnix.org> - 2025-03-21 19:39 +0000
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-21 20:15 +0000
Re: Please List Your Open Ports vallor <vallor@cultnix.org> - 2025-03-21 21:13 +0000
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-21 21:29 +0000
Re: Please List Your Open Ports vallor <vallor@cultnix.org> - 2025-03-21 21:36 +0000
Re: Please List Your Open Ports Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-03-21 21:49 +0000
Re: Please List Your Open Ports Rudy Canoza <rc@jolly.invalid> - 2025-03-22 07:54 -0400
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-22 12:09 +0000
Re: Please List Your Open Ports CrudeSausage <crude@sausa.ge> - 2025-03-22 08:28 -0400
Re: Please List Your Open Ports L Thorpe <lt666@sixsixsix.net> - 2025-03-22 14:09 +0000
Re: Please List Your Open Ports Physfitfreak <physfitfreak@gmail.com> - 2025-03-22 12:02 -0500
Re: Please List Your Open Ports candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-03-27 23:00 +0000
Re: Please List Your Open Ports Farley Flud <ff@linux.rocks> - 2025-03-17 19:14 +0000
Re: Please List Your Open Ports vallor <vallor@cultnix.org> - 2025-03-17 19:28 +0000
Page 1 of 3 [1] 2 3 Next page →
| From | Farley Flud <ff@linux.rocks> |
|---|---|
| Date | 2025-03-16 15:19 +0000 |
| Subject | Please List Your Open Ports |
| Message-ID | <pan$98f5f$d61a8c9$9aa88326$ea218693@linux.rocks> |
I am curious about how many open ports the average distro exposes. List your open ports using the following command: netstat -lnptu Here are my open ports (I don's use a distro): Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 215/pdnsd udp 0 0 127.0.0.1:53 0.0.0.0:* 215/pdnsd That's all I need for my workstation. Note that "netstat" may not be available with that putrid abomination knows as systemd. Use whatever equivalent. -- Systemd: made by assholes for assholes.
[toc] | [next] | [standalone]
| From | Physfitfreak <physfitfreak@gmail.com> |
|---|---|
| Date | 2025-03-16 13:50 -0500 |
| Message-ID | <vr76h7$2bde5$1@dont-email.me> |
| In reply to | #687549 |
On 3/16/25 10:19 AM, Farley Flud wrote: > I am curious about how many open ports the average distro exposes. > > List your open ports using the following command: > > netstat -lnptu > > Here are my open ports (I don's use a distro): > > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 215/pdnsd > udp 0 0 127.0.0.1:53 0.0.0.0:* 215/pdnsd > > That's all I need for my workstation. > > Note that "netstat" may not be available with that putrid abomination > knows as systemd. > > Use whatever equivalent. > > I get 12 open ports. 6 of them have status of LISTEN. For example, one of the whose status isn't mentioned is this: udp6 0 0 :::34964 :::* Have no idea what these all mean.
[toc] | [prev] | [next] | [standalone]
| From | Farley Flud <ff@linux.rocks> |
|---|---|
| Date | 2025-03-16 19:52 +0000 |
| Message-ID | <pan$46871$67579cb1$5784d130$83cc267d@linux.rocks> |
| In reply to | #687554 |
On Sun, 16 Mar 2025 13:50:15 -0500, Physfitfreak wrote: > > I get 12 open ports. 6 of them have status of LISTEN. > > > Have no idea what these all mean. > It means that the average distro is exposing itself to potential security threats. For a standalone workstation there should be no open ports. -- Systemd: solving all the problems that you never knew you had.
[toc] | [prev] | [next] | [standalone]
| From | Physfitfreak <physfitfreak@gmail.com> |
|---|---|
| Date | 2025-03-16 17:38 -0500 |
| Message-ID | <vr7jt7$u90$2@solani.org> |
| In reply to | #687557 |
On 3/16/25 2:52 PM, Farley Flud wrote: > On Sun, 16 Mar 2025 13:50:15 -0500, Physfitfreak wrote: > >> >> I get 12 open ports. 6 of them have status of LISTEN. >> >> >> Have no idea what these all mean. >> > > It means that the average distro is exposing itself to potential > security threats. > > For a standalone workstation there should be no open ports. > > > > > I vaguely remember asking this question before. What do you mean by a "standalone" computer? I have 24x7 access to internet of course. Would that mean I'm not using a standalone computer? And since you posted this thread, I looked into closing the unneeded ports, and was not successful cause giving the command involved would not recognize the information about the port that I was giving it. Then I looked whether I could find if repeated attempts have been made to log into my computer, and were somehow led to installing fail2ban. But I don't understand well enough what it exactly does and how I'm supposed to use it. Yet.
[toc] | [prev] | [next] | [standalone]
| From | Farley Flud <fsquared@fsquared.linux> |
|---|---|
| Date | 2025-03-17 10:37 +0000 |
| Message-ID | <182d90d4ed38e644$26628$19313$802601b3@news.usenetexpress.com> |
| In reply to | #687568 |
On Sun, 16 Mar 2025 17:38:31 -0500, Physfitfreak wrote: > > I vaguely remember asking this question before. What do you mean by a > "standalone" computer? > A "standalone" workstation is one that stands alone, i.e. it is not part of a network. > > I have 24x7 access to internet of course. Would that mean I'm not using > a standalone computer? > Essentially no, unless the Internet access makes the machine a part of a network. > > And since you posted this thread, I looked into closing the unneeded > ports, and was not successful cause giving the command involved would > not recognize the information about the port that I was giving it. > I want to know how many open ports there are on the average distro machine that is not specifically being used as a server (for a good laugh). The Linux kernel has hundreds of configurable options for networking. I disable all options except the ones that are necessary to connect to the Internet. I want to know how the average distro is configured (for a good laugh). > > Then I looked whether I could find if repeated attempts have been made > to log into my computer, and were somehow led to installing fail2ban. > But I don't understand well enough what it exactly does and how I'm > supposed to use it. Yet. > You should check out tcpdump to examine what kind of traffic you are experiencing. -- Hail Linux! Hail FOSS! Hail Stallman!
[toc] | [prev] | [next] | [standalone]
| From | Physfitfreak <physfitfreak@gmail.com> |
|---|---|
| Date | 2025-03-17 13:28 -0500 |
| Message-ID | <vr9pji$lv2o$1@dont-email.me> |
| In reply to | #687581 |
On 3/17/25 5:37 AM, Farley Flud wrote: > You should check out tcpdump to examine what kind of traffic you > are experiencing. I will. Note that nsa, cia, and fbi are constantly part of this computer's "network". And I don't mind that, of course. In fact I prefer it that way. They're on my side. But I do _not_ wish psychos like "DFS" and now deceased "Relf" and "Jim Pennino" types of petty criminal "engineers" access my computer. This is my concern, this type of threats. Because they'd only mean harm.
[toc] | [prev] | [next] | [standalone]
| From | Physfitfreak <physfitfreak@gmail.com> |
|---|---|
| Date | 2025-03-17 13:34 -0500 |
| Message-ID | <vr9pvj$1u7s$1@solani.org> |
| In reply to | #687592 |
On 3/17/25 1:28 PM, Physfitfreak wrote:
> On 3/17/25 5:37 AM, Farley Flud wrote:
>> You should check out tcpdump to examine what kind of traffic you
>> are experiencing.
>
>
> I will.
>
> Note that nsa, cia, and fbi are constantly part of this computer's
> "network". And I don't mind that, of course.
>
> In fact I prefer it that way. They're on my side.
>
> But I do _not_ wish psychos like "DFS" and now deceased "Relf" and "Jim
> Pennino" types of petty criminal "engineers" access my computer. This is
> my concern, this type of threats. Because they'd only mean harm.
>
>
Running tcpdump gives me this error:
tcpdump: eno1: You don't have permission to capture on that device
[toc] | [prev] | [next] | [standalone]
| From | Farley Flud <ff@linux.rocks> |
|---|---|
| Date | 2025-03-17 19:09 +0000 |
| Message-ID | <pan$4e8$4d696b10$4b4e7f71$ac9f14e9@linux.rocks> |
| In reply to | #687594 |
On Mon, 17 Mar 2025 13:34:27 -0500, Physfitfreak wrote: > > Running tcpdump gives me this error: > > tcpdump: eno1: You don't have permission to capture on that device > You must execute tcpdump as the root user. On my machine I am always the root user, but the stupid distros have their own ridiculous security philosophy. I believe that their asinine command workaround is this: sudo tcpdump Also, read the tcpdump man page or search for tcpdump web pages. There is a LOT that the command can do. -- Systemd: solving all the problems that you never knew you had.
[toc] | [prev] | [next] | [standalone]
| From | Physfitfreak <physfitfreak@gmail.com> |
|---|---|
| Date | 2025-03-17 16:06 -0500 |
| Message-ID | <vra2sp$21kq$1@solani.org> |
| In reply to | #687595 |
On 3/17/25 2:09 PM, Farley Flud wrote: > On Mon, 17 Mar 2025 13:34:27 -0500, Physfitfreak wrote: > >> >> Running tcpdump gives me this error: >> >> tcpdump: eno1: You don't have permission to capture on that device >> > > You must execute tcpdump as the root user. > > On my machine I am always the root user, but the stupid distros have their > own ridiculous security philosophy. I believe that their asinine command > workaround is this: > > sudo tcpdump > > Also, read the tcpdump man page or search for tcpdump web pages. > There is a LOT that the command can do. > > > > > Ok, I ran it and had it write the result (a large file) to a file. Checking the file, I could not understand any of the output which were in chronological order. I spotted a few "Amazon" words, so I thought perhaps most of the file is about cookies activities, etc. So I ran the bleachbit to clear cookies up. Then I ran tcpdump again and wrote output in a file. The file looks the same having stuff like: (part of the entry for second 20 of 3:51 pm today) 15:51:20.751730 IP6 _gateway > hydrogen-OptiPlex-7050: ICMP6, neighbor solicitation, who has hydrogen-OptiPlex-7050, length 32 15:51:20.751816 IP6 hydrogen-OptiPlex-7050 > _gateway: ICMP6, neighbor advertisement, tgt is hydrogen-OptiPlex-7050, length 24 15:51:20.767810 IP6 _gateway > hydrogen-OptiPlex-7050: ICMP6, neighbor solicitation, who has hydrogen-OptiPlex-7050, length 32 15:51:20.767897 IP6 hydrogen-OptiPlex-7050 > _gateway: ICMP6, neighbor advertisement, tgt is hydrogen-OptiPlex-7050, length 24 15:51:20.799787 IP6 _gateway > hydrogen-OptiPlex-7050: ICMP6, neighbor solicitation, who has hydrogen-OptiPlex-7050, length 32 15:51:20.799872 IP6 hydrogen-OptiPlex-7050 > _gateway: ICMP6, neighbor advertisement, tgt is hydrogen-OptiPlex-7050, length 24 15:51:20.806917 IP6 hydrogen-OptiPlex-7050 > homeportal: ICMP6, neighbor solicitation, who has homeportal, length 32 15:51:20.806977 IP6 hydrogen-OptiPlex-7050 > _gateway: ICMP6, neighbor solicitation, who has _gateway, length 32 15:51:20.807765 IP6 homeportal > hydrogen-OptiPlex-7050: ICMP6, neighbor advertisement, tgt is homeportal, length 24 15:51:20.808234 IP6 _gateway > hydrogen-OptiPlex-7050: ICMP6, neighbor advertisement, tgt is _gateway, length 24 15:51:20.854022 e0:22:04:56:89:3b (oui Unknown) > Broadcast, ethertype Unknown (0x7373), length 121: 0x0000: 1211 0000 0043 1fb2 05dd f137 e122 3905 .....C.....7."9. 0x0010: ef58 d67c 1e40 a4ae bb60 6ad8 2f7d eecd .X.|.@...`j./}.. 0x0020: 43c3 ac98 e8a4 0000 0201 8003 06e0 2204 C.............". 0x0030: 5689 3b04 0104 0701 011b 0100 0806 e022 V.;............" 0x0040: 0456 893b 0901 020e 1800 0000 0000 0000 .V.;............ 0x0050: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0060: 0019 0889 caa5 4969 ebf2 04 ......Ii... If you can make sense of it you're welcome to comment :)
[toc] | [prev] | [next] | [standalone]
| From | Farley Flud <ff@linux.rocks> |
|---|---|
| Date | 2025-03-17 21:38 +0000 |
| Message-ID | <pan$5ecf8$98a81484$4ef24ebb$65e0792b@linux.rocks> |
| In reply to | #687603 |
On Mon, 17 Mar 2025 16:06:33 -0500, Physfitfreak wrote: > > If you can make sense of it you're welcome to comment :) > I'm very sorry, but any comments are not possible unless one understands basic IP/TCP concepts. You undeniably have the intelligence to grasp these concepts but I cannot provide any quick and easy insight. The only recourse is to study basic networking concepts via the many, many web sites that are devoted to this topic, or perhaps via a few books on same. -- Systemd: solving all the problems that you never knew you had.
[toc] | [prev] | [next] | [standalone]
| From | Physfitfreak <physfitfreak@gmail.com> |
|---|---|
| Date | 2025-03-17 16:55 -0500 |
| Message-ID | <vra5pa$23g7$1@solani.org> |
| In reply to | #687608 |
On 3/17/25 4:38 PM, Farley Flud wrote: > On Mon, 17 Mar 2025 16:06:33 -0500, Physfitfreak wrote: > >> >> If you can make sense of it you're welcome to comment :) >> > > I'm very sorry, but any comments are not possible unless one > understands basic IP/TCP concepts. > > You undeniably have the intelligence to grasp these concepts > but I cannot provide any quick and easy insight. > > The only recourse is to study basic networking concepts via > the many, many web sites that are devoted to this topic, or > perhaps via a few books on same. > > > > > Or using AI :) AI says this is normal activity. That's all I care about it.
[toc] | [prev] | [next] | [standalone]
| From | candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> |
|---|---|
| Date | 2025-03-27 20:00 +0000 |
| Message-ID | <slrnvubbbg.771v.candycanearter07@candydeb.host.invalid> |
| In reply to | #687595 |
Farley Flud <ff@linux.rocks> wrote at 19:09 this Monday (GMT): > On Mon, 17 Mar 2025 13:34:27 -0500, Physfitfreak wrote: > >> >> Running tcpdump gives me this error: >> >> tcpdump: eno1: You don't have permission to capture on that device >> > > You must execute tcpdump as the root user. > > On my machine I am always the root user, but the stupid distros have their > own ridiculous security philosophy. I believe that their asinine command > workaround is this: > > sudo tcpdump I think that's considered bad practice, but it's your machine.. > Also, read the tcpdump man page or search for tcpdump web pages. > There is a LOT that the command can do. Thanks, this program seems super cool! IDK if I'll use it for anything productive, but it'll be cool to see. -- user <candycane> is generated from /dev/urandom
[toc] | [prev] | [next] | [standalone]
| From | Joel <joelcrump@gmail.com> |
|---|---|
| Date | 2025-03-27 16:13 -0400 |
| Message-ID | <g9cbuj99k8idf60213sgbhmm0gubhehrkc@4ax.com> |
| In reply to | #688250 |
candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote: >Farley Flud <ff@linux.rocks> wrote at 19:09 this Monday (GMT): >> On Mon, 17 Mar 2025 13:34:27 -0500, Physfitfreak wrote: >> >>> Running tcpdump gives me this error: >>> >>> tcpdump: eno1: You don't have permission to capture on that device >> >> You must execute tcpdump as the root user. >> >> On my machine I am always the root user, but the stupid distros have their >> own ridiculous security philosophy. I believe that their asinine command >> workaround is this: >> >> sudo tcpdump > >I think that's considered bad practice, but it's your machine.. Right, that's a total self-pwn by Larry, running as root on top of how barebones his setup is, with Gentoo/LFS, bunch of idiocy. Distros are the way to go, if you have a brain. -- Joel W. Crump Amendment XIV Section 1. [...] No state shall make or enforce any law which shall abridge the privileges or immunities of citizens of the United States; nor shall any state deprive any person of life, liberty, or property, without due process of law; nor deny to any person within its jurisdiction the equal protection of the laws. Dobbs rewrites this, it is invalid precedent. States are liable for denying needed abortions, e.g. TX.
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-03-30 13:49 +0000 |
| Message-ID | <67e94bd0$0$423$426a74cc@news.free.fr> |
| In reply to | #688250 |
Le 27-03-2025, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> a écrit : > Farley Flud <ff@linux.rocks> wrote at 19:09 this Monday (GMT): >> sudo tcpdump > > I think that's considered bad practice, Of course it is. > but it's your machine.. As long as only his pet dog the terrorist is following his advices, it's not important. >> Also, read the tcpdump man page or search for tcpdump web pages. >> There is a LOT that the command can do. > > > Thanks, this program seems super cool! IDK if I'll use it for anything > productive, but it'll be cool to see. The good part with tcpdump is for automating tasks, but if you want to use it interactively, you should use wireshark instead. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | Farley Flud <ff@linux.rocks> |
|---|---|
| Date | 2025-03-30 17:16 +0000 |
| Message-ID | <pan$331de$e60ef1ec$867cd52e$28077b4b@linux.rocks> |
| In reply to | #688445 |
On 30 Mar 2025 13:49:04 GMT, Stéphane CARPENTIER wrote: >> >> I think that's considered bad practice, > > Of course it is. > No, it's not bad practice. My machine belongs only to me and running as root is the ONLY sensible option. I have been through this discussion with many others in the past and none of them could ever explain how running as root could lead to "exploits." Can you? Ha, ha, ha, ha! They, like YOU, are just parrots that mimic what they've been told. They have no understanding. They, like YOU, accept whatever their distro gives them. I have been running as root since the very beginning and I will continue to run as root until the very end -- and there have been and there will be no fucking consequences. You probably wish that you could run as root, but you don't know how to do it. Your distro makes the decisions and you just follow like a sheep. Ha, ha, ha, ha, ha, ha, ha, ha, ha! You are just another helpless distro lackey that cannot control his own machine. -- Systemd: solving all the problems that you never knew you had.
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-03-30 21:50 +0000 |
| Message-ID | <67e9bcb7$0$12922$426a74cc@news.free.fr> |
| In reply to | #688453 |
Le 30-03-2025, Farley Flud <ff@linux.rocks> a écrit : > On 30 Mar 2025 13:49:04 GMT, Stéphane CARPENTIER wrote: > >>> >>> I think that's considered bad practice, >> >> Of course it is. > > No, it's not bad practice. Of course it is. Your inability to understand what happens on your computer doesn't change the facts. > My machine belongs only to me and running as root is the > ONLY sensible option. In fact, no. Running as root some commands like "rm -rf /*" is what you describe and anyone can say that. Now, when you run tcpdump, your are using data coming from Internet. You don't control the data coming from Internet, you can believe/pretend whatever you want, it's a fact. So if someone sends data mean to breach tcpdump, running it as root just grant him the full power of your computer without any need to escalate privileges. That's why it's called bad practice. Now, you claim/believe what you want, I don't care. The fact remains: your computer belongs to anyone able to send you data as much as it belongs to you. The best protection for your computer is being managed by your clumsy hands which make it closer to a brick than to a computer. As long as the joke you are using as a computer remains useless, it's protected against any attack from the outside world. But be careful: the day you learn enough to make it run like a real computer, it will be used by others. Even if you can't see it. > I have been through this discussion with many others in the > past and none of them could ever explain how running as > root could lead to "exploits." Because you don't understand how a computer works. It's not running as root which leads to exploit. Running as what you want can lead to exploit if you don't control the inputs. And with tcpdump, you don't control the input. By design. Because, by design, tcpdump manages what others send to you as much as what you send to others. And you can't control others, so you can't control what others send to you. That's a simple fact. Your inability to see it is telling. So, there is no way you can control tcpdump inputs. So running tcpdump, by itself, can lead to exploit. And if tcpdump is running as root it has the full control of your computer. That's why it's bad practice: you just facilitate the way of the hacker. You can sanitize data as you want, you still don't control them. And I read enough of your messages to know that you certainly don't sanitize your inputs of tcpdump. I'm not saying you should, because if you did, you wouldn't be able to analyse it. But I'm pretty sure you can't use tcpdump for real: you are only able to launch it claiming you are a master of your computer. So you can't sanitize your data, you can't understand the outputs of tcpdump and nothing you can do would change that. So, the only fact that remains is: if someone was sending data designed to pawn tcpdump, you would grant him full control of your computer and you would never realize it. Good job. > Can you? Ha, ha, ha, ha! Of course, I can. Now, the real question is: can you understand my simple explanation? I seriously doubt it. > They, like YOU, are just parrots that mimic what they've > been told. They have no understanding. You are the one unable to understand the reason why it's bad practice. Not me. Don't switch sides. You are the one unable to understand why it's considered bad practice. > They, like YOU, accept whatever their distro gives them. You already proved you know nothing about distros, so you can't know how I use mine. You can't know what mine allows me to do neither. And there is no relation between a distro of choice and the way one use tcpdump. So this sentence is like you: garbage unrelated to any technical discussion. > I have been running as root since the very beginning and > I will continue to run as root until the very end -- and > there have been and there will be no fucking consequences. I know. I already answered that stupidity. You are stuck in the past, so, you can't understand that malware evolved since you first heard about them. At the beginning, the viruses were destroying your computer. Today, they are using it. Because destroying your computer could be fun but useless when using it can bring money. As you don't really use your computer, if someone was taking control of it you wouldn't realize it. You computer is either probably part of a botnet. It can be either mining bitcoins for others or trying to attack banks. Or both at the same time. For the bank part, if the cops are coming to your house, you'll be aware of it. You can't be able to to see it. Thirty years ago, when someone took control of your computer, you realized it the hard way. Now, it's using your computer and you don't realize it. Good job for giving the power of your computer to others. It's nothing to you and it's money for others. You should be proud of granting a way to others to get money thanks to your computer without you realizing it. > You probably wish that you could run as root, I don't wish it. I have no need for that. > but you don't know how to do it. I can do it if I want to: "sudo su -" and it's done. So, I just proved your sentence is a lie provided by an incompetent Linux user. Because anyone knows how to run as root. Even if you are unable to understand why I put a dash at the end of my command. It's just plain stupid for most of the cases, there is nothing to wish for. There is only basic knowledge of Linux, which you clearly don't have. > Your distro makes the decisions and you just follow like a sheep. Once again: you don't know what a distro is, you don't know how a distro works and you don't know how I use my distro. So, this sentence is just like you: a bag full of shit. > You are just another helpless distro lackey that cannot > control his own machine. Once again: I'm not the one complaining against freedesktop, systemd, python and wayland. Unlike you, I'm using my computer as I want. So, once again: don't switch sides. You are the Windows fanboy unable to use efficiently Linux. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> |
|---|---|
| Date | 2025-03-31 17:50 +0000 |
| Message-ID | <slrnvulkvs.9h4t.candycanearter07@candydeb.host.invalid> |
| In reply to | #688445 |
Stéphane CARPENTIER <sc@fiat-linux.fr> wrote at 13:49 this Sunday (GMT): > Le 27-03-2025, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> a écrit : >> Farley Flud <ff@linux.rocks> wrote at 19:09 this Monday (GMT): >>> sudo tcpdump >> >> I think that's considered bad practice, > > Of course it is. > >> but it's your machine.. > > As long as only his pet dog the terrorist is following his advices, it's > not important. > >>> Also, read the tcpdump man page or search for tcpdump web pages. >>> There is a LOT that the command can do. >> >> >> Thanks, this program seems super cool! IDK if I'll use it for anything >> productive, but it'll be cool to see. > > The good part with tcpdump is for automating tasks, but if you want to > use it interactively, you should use wireshark instead. Oh, thanks! Again, I /probably/ won't need it for anything though. -- user <candycane> is generated from /dev/urandom
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-04-06 08:33 +0000 |
| Message-ID | <67f23c62$0$11433$426a34cc@news.free.fr> |
| In reply to | #688515 |
Le 31-03-2025, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> a écrit : > Stéphane CARPENTIER <sc@fiat-linux.fr> wrote at 13:49 this Sunday (GMT): >> >> The good part with tcpdump is for automating tasks, but if you want to >> use it interactively, you should use wireshark instead. > > Oh, thanks! Again, I /probably/ won't need it for anything though. Try it once. You launch it and go away from your computer. Then when you come back, you stop it and see what happen on your computer. You can see interesting things. A long time ago, when I did that, I discovered that Firefox was sending information by default. I deactivated the option in FireFox, ran it again and saw that the deactivation was good. It's a good way to be sure programs don't do things you don't like without your knowledge. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | Chris Ahlstrom <OFeem1987@teleworm.us> |
|---|---|
| Date | 2025-04-06 09:40 -0400 |
| Message-ID | <vsu07u$13h35$1@dont-email.me> |
| In reply to | #688706 |
Stéphane CARPENTIER wrote this post while blinking in Morse code: > Le 31-03-2025, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> a écrit : >> Stéphane CARPENTIER <sc@fiat-linux.fr> wrote at 13:49 this Sunday (GMT): >>> >>> The good part with tcpdump is for automating tasks, but if you want to >>> use it interactively, you should use wireshark instead. >> >> Oh, thanks! Again, I /probably/ won't need it for anything though. > > Try it once. You launch it and go away from your computer. Then when you > come back, you stop it and see what happen on your computer. You can see > interesting things. A long time ago, when I did that, I discovered that > Firefox was sending information by default. I deactivated the option in > FireFox, ran it again and saw that the deactivation was good. > > It's a good way to be sure programs don't do things you don't like > without your knowledge. A cool GUI tool is etherape. Watch it explode when you load a newsy web site. -- "Don't discount flying pigs before you have good air defense." -- jvh@clinet.FI
[toc] | [prev] | [next] | [standalone]
| From | Marc Haber <mh+usenetspam1118@zugschl.us> |
|---|---|
| Date | 2025-03-16 19:54 +0100 |
| Message-ID | <vr76os$27n15$1@news1.tnib.de> |
| In reply to | #687549 |
Farley Flud <ff@linux.rocks> wrote: >Note that "netstat" may not be available with that putrid abomination >knows as systemd. Presence or non-presence of a netstat binary has absolutely nothing to do with the init system. -- ---------------------------------------------------------------------------- Marc Haber | " Questions are the | Mailadresse im Header Rhein-Neckar, DE | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402
[toc] | [prev] | [next] | [standalone]
Page 1 of 3 [1] 2 3 Next page →
Back to top | Article view | comp.os.linux.advocacy
csiph-web