I put my mom on linux. You be surprise how many scammers will hang up as soon as they hear you run linux instead of windows/mac. I went through a phase talking to "windows support" because my evil sister used my moms phone number for something that ended up in there database. I ran through their script a few times typically stopping when they try and get me to install remote access software to see what their end goal was. When I started telling them I ran linux not windows they would hang up.
This is a very simple question to a very complex problem/issue. Simple answer it isn't possible. The current way the internet, law, and society works it is impossible to start a anonymous blog. You can create hurdles and do simple things that would stop the easy to find things. But, if someone or corporation really put any effort into finding you they could.
The internet was not design for people to be anonymous. Our law's weren't made to keep you anonymous. Our society doesn't allow for people to be anonymous.
Would not having E2EE platforms remove child abuse imagery and/or terrorism? The answer of course is no. I always get reminded of a story about terrorist using video games to communicate with each other and giggle a little bit.
Currently the government uses E2EE to safe guard themselves, then the American people should also have access to it to safe guard themselves. If the government allows us to purchase guns for our safety, why not encryption? You going to say encryption kills more people then guns?
Plus E2EE isn't some super secret thing the government only has access to. Any one can create a E2EE platform and the government would be hard press to stop it. You might not be able to commercialize it, but it won't stop it from existing.
I believe arguing over if something should be legal/illegal is a pointless distraction. E2EE exist now embrace it or move on, but don't think banning it or making it illegal will some how make it disappear.
I have work at a bank long enough to hear stories about people having mental breakdowns. Everything from just walking out of there office naked to people using the stairway as bathrooms to help deal with the stress and anxiety that some jobs at the bank can cause. At the first bank I worked at I never witness it myself, but when I got a new job at another one it started to become a normal.
So a friend of mine got hired by a bank that needed to hire 100 technical people in 30 days time. He told me how awesome of a job it was, because they had nothing to do so he spent his day doing whatever he wanted and getting paid mad money. Something happen and 2 people got fired so they needed them replace asap. He ask me if I wanted to throw my hat in the ring. I got such a gleaming referral from my friend they skip the interview process and hired me on the spot. In the week time of those 2 people getting fired though everything had changed.
We came to find out those 2 people got fired because the project was suppose to be 80% done by then, but instead it was more like 10%. They fired them 2 to show they meant business and they had the lowest performance score out of the entire 100 people so they were made a example. New policy was created no more headphones, meetings everyday, only work allowed on your computer screen, no smartphones out, and a old grumpy man was put at the back end of each isle to watch us. To make it worse all the cubicals were only shoulder height. So you had all the disadvantage of a open office with all the disadvantages of a cubical farm in a neat little package. The cubes were also smaller then normal with only enough space for your chair to slide back against the wall so you could slide out.
This is when stuff gets really strange you would think with all this distress and work needing to be done everyone would have there head down pounding out whatever they were suppose to be doing? That is the thing there was no work to be done. In my 6 month contract there I probably spent 3 hours actually doing work. In reality a 10 person team could have easily done what we had to do in a month time, but because of how the bank and management had structure everything it was impossible to do anything. There was also another strange thing people were expected to work 50 hours a week no matter what. When I started I put down 40 hours and got told by my manager, my recruiter, and a higher up I need to work more to help them catch up. The following week I work only 40 hours and the talks turn into threats so I started to work 47 hours a week and the threats went away. If you work 51+ hours a week it would give you the awesome option to work weekends as well.
So with all this stress, anxiety, and boredom a good number of people started to act really strange. A handful of people had stop taking showers leaving a noticeable smell in certain areas. Some people would squirrel food away leading to infestation of bugs and a underground market for trading and selling junk food. Some of the higher ups notice people were wearing the same cloths every day so after a talk those people started to wear jackets and such so the higher ups couldn't say anything to them. It became a normal thing for some to just sleep at there desk the entire day. Office supplies were constantly going missing even with the higher ups guarding them. Fights would break out randomly some just shouting a couple physical ones. Every other week a women would normally have a break down and cry in her cube because managers had started to use them as there own punching bags over emails/IMs. Lunches became more group therapy then a enjoyable outing. At some tipping point the main recruiting agency came in and had us all sign something basically pledging we would act professionally from that point forward and they were not held legally for our own actions and such.
To make the matter worse the recruiting agency was adding more anxiety and stress on the people. Most of the people there had work VISA and needed a job to stay in the country. The agency bully them into working 6 days a week. Someone accidentally sent out a email letting some of the people know they were no longer need on the project would be let go in 2 weeks. All the recruiters instantly contacted all 25 contractors that email went to saying that was a mistake and not true. They said they would be on the project for at least 6 more months and to ignore that email. 2 weeks later they were all let go.
I was told my contract was only going to be 3 months, I ended up 6 months there. When I hit the 3 month period I started to do whatever I wanted thinking I would get fired, but it never happen. I repeatedly reached out to my recruiter telling her to put in my 2 week notice, and it never happen. It finally hit a point where I told my manager my recruiter told me this was my last week. After my last day my recruiter contacted me 6 days later asking me why I wasn't at work. My friend that got me the job stayed on for another week, but ended up getting fired. A manager that leaned on him heavy for answering technical questions got scared he might replace her and told the higher ups he attacked her during a meeting. Security came and lead him out of the building.
I have a rpi2 I use as a low power server that keeps me connected to my irc server and runs tasks for me.
I have a rpi3 installed in my truck that acts as a media player. It also reads my OBDII so I know how my engine is running and other diagnosis information. I also use it to map wifi/bluetooth spots and other random data as I am driving.
First you leverage already existing blockchain technology to create simple program that allows you to access gpu, cpu, network, and storage of a pc it is installed on. Second you adverties it to people telling them they can earn cryptocash you have invented in exchange for resources used on there pc. Third any surplus of access you have sell to a third party or mine a more popular cryptocurrency.
Yep been using IRC for over 10 years now and still love it. Always seem like any gui base chat client required more resources then they should. Also the clients didn't allow for modifications I would want/need. Also at the time getting into desktop chat clients one of the popular ones to make profit turn their client into a massive botnet selling cpu power to business. This lead me to distrust gui clients early on.
I recently had a handful of friends that wanted to get away from IRC mainly because smart phone interaction is not the best. Since we switched to keybase I feel like we talk less. Also the desktop client doesn't close without using kill command which makes me open it less.
I use IRC just for chatting with friends and strangers on internet. Shout out to the #csharp channel on freenode some great people that regularly answer questions and help people out.
Isn't it great to have the choice wether some tool manages the system or one does it manually? Thanks GNU/Linux, thanks all the Linux distributions maintained by hundreds of volunteers!
I got the opposite out of this post; not only do RH/Cent use hellish network middlemen, but other distros have their own fresh hells. Is there really a choice that doesn't commandeer your configs?
Standard practice for me was to rip out every last shred of NetworkManager on every fresh build, but I didn't realize how many other utilities broke the resolver config as well.
What's wrong with Network Manager? I've yet to find a better tool for managing wired, wireless, vpn, and mobile broadband anywhere as well as NM. Sticking with the theme of the original post, NM combined with unbound and dnssec-triggerd is downright amazing. Your vpn connection passes down a nameserver and search zone? Bam, NM pushes that into unbound, and now queries for your vpn domain go to the vpn resolvers, and your other queries go out to whatever you set for your default resolver.
To be fair, in that particular config, resolv.conf never changes as it always points to loopback, with your preferred nameservers only existing in memory in unbound, and in network manager's config.
It's opaque and hard to debug. It may have utility on laptops, but on servers, it is absolutely counterproductive. I could not for the life of me figure out what it was doing w.r.t ipv6 prefix delegation and how it was dealing with dhclient6 internally. My leases would expire but not renew. Eventually, I had to rip it out and create simple configs by hand that work well.
I'll grant you that it's extremely different from static network configs, but it's far from opaque. If anything having all the logging under NM can make troubleshooting a pleasure `journalctl -f -u NetworkManager` is a godsend.
I'll also agree that the benefits on a server are next to non-existant, but at the same time it's just a default that's trivial to turn off, and I could probably count on one hand the number of times it's bitten me while building and deploying tens of thousands of hosts over the last 15 years.
It's a tool I've learned to love on my workstations, and rarely even notice on production systems.
You don't notice until it bites you. And trust me, I spent a lot of time debugging the ipv6 issues to no avail. It may be in general the whole ipv6 ecosystem is just not as mature, but the end result is that user experience suffers.
Disagree. I've "disabled" it in policy countless times, and been bitten in the ass by it re-enabling itself countless times. The only thing that works is deleting it entirely. After the umpteenth troubleshooting session, only to find out "oh, it's that thing again? That thing we keep trying to make go away?" I'm not going to spend one more minute trying to figure out how I could keep from hurting its feelings.
It sounds like you don't understand the tools you use, and have no interest in learning them. NetwokManager (just like any other daemon) cannot "re-enable" itself. It's possible if you were on an Debian derived host that package post-install scripts enable the service (as is the case with all services on Debian derived distros due to packaging policies. The right way forward here is to indeed remove the package if you aren't using NM. Or better yet, get a better grip on the packages you install in the first place, and just don't install NM to begin with.
If you're on a RH or Arch derived distro, policy is just the opposite, and if the service is ever magically enabled (aside from Anaconda enabling it after the package was selected at install time), it's a massive bug (I can't find any such bug report in Arch or Fedora).
No, it's just that, for the purpose of an internet forum comment, I don't wish to revisit years of regular and maddening problems across fleets of thousands of servers. Over the years they may be subject to different initial build and deployment regimes, to say nothing of different OS versions that may have been released over that time, and various Puppet manifests that may have been changed over that time.
When something is regularly found to be the problem, and has never made my life any easier, it gets yanked. Sometimes I may have had time to analyze further, other times it may have been an emergency. Regardless, it's been at least 1.5 years since I worked in that environment, and my memory has faded. In the real world, we don't have infinite time to analyze infinite failures.
Here's what I remember:
NetworkManager = problems.
No NetworkManager = no problems.
You may care to look down on people who don't always have the time to analyze every single occurrence of every single problem to the nth degree, and subsequently catalogue the exact cause and fix for reference when posting on forums in the future, and that's fine.
My opinion is, it sucks, and I don't want it.
If you like it, and enjoy its benefits, please do. I'm not denigrating you for your choice.
systemd's dependency logic about what is enabled or disabled is not straightforward. For example, I disable buetooth on general principle, and yet it gets enabled (as in activated) in some scenarios due to other stuff depending on it (i think something in gnome does). "systemctl is-enabled foo.service" is not a guarantee about anything. Something else can still start the service without the user's authorization.
It's not really the user's fault though. If you really want to make sure that something else doesn't start it, you need to mask the service. But then, you can't start it either. What you really need is "disabled unless I start it". I don't think there is a state like that.
I don't use these things. I run servers. It does nothing but break stuff, and it keeps butting in like that annoying acquaintance at parties. It's very difficult to make go away short of uninstalling every last vestige of it.
I'm on Debian stable and there's no systemd-resolved or NetworkManager running.
When I'm on a DHCP network dhclient runs and manages my resolv.conf asexpected.
We're still entirely in control in GNU/Linux, if you assert control. It turns out however that most people actually want the distros to do all the magic and for things to Just Work.
Choice is "do you want to <x> or <y>" not "if you don't want <x> figure out how to implement <y> on your own". That's simply known as "doing the work yourself" and is largely possible on even closed sourced systems assuming you have rights on the box.
There is nothing wrong with that but it shouldn't be conflated as choice and paraded as success of such.
The GP is referring to all the other Linux distributions who really give you <y> (or <z> or <Þ>), not to implementing <y> on your own.
There are distributions (e.g. Linux from Scratch) for when the option you want is the NULL option—i.e., doing things yourself. But there are N other managed options, not just one managed option and NULL.
Ah yes, the strawman disto which matches exactly what <user> needs and is the reason <problem> isn't actually an issue since they can just switch to strawman distro!
Unfortunately strawman distro is never real and the problems still exist after congratulating the ability to switch to it.
Well, you chose to install it, you can configure it not to do this. For the vast majority of people, myself included, NetworkManager should have control of DNS resolvers (at least, when I have WiFi on a system. I usually don't use NetworkManager on Ethernet-only systems, since there's systemd-networkd).
Absolutely. My laptop travels across a lot of networks, wifi and ethernet, with and without OpenVPN and Mobile IPSEC. I tether to my phone. I have some IPv6 networks to worry about. Firewalld is expected to do the right thing as well. I have loads of NM profiles, one of which has several RFC1918 addresses for covering most bases when starting out with routers and switches.
