Yup. All of them.
Yup. All of them.
I will not note the unexpired Ohio driver's license is questionable; who cares if it is expired?
Theoretically, a resident of--say Indiana--who recently moved there from Ohio could potentially vote in both states using an expired or voided Ohio drivers license.
As a sports fan who chooses not to get screwed over by the cable or satellite TV companies, I don't have access to the ESPN app. Paying a couple bucks a month extra to Amazon for live sports would be well worth it to me vs paying for a cable subscription.
Also, use a script or ad blocker to prevent those stupid like buttons from running their scripts in the background.
I see you never made it past line 1 of the comment...
For what it's worth they are spying on you anyway, even if you don't have an account. Every time you see a like button--whether you click it or not, you are being facebooked. Every time someone tags you in a picture (even though you don't have an account,) you are being facebooked.
At the end of the day you are better off having an account (even if you don't use it) so you can control your exposure. Also, use a script or ad blocker to prevent those stupid like buttons from running their script in the background.
Obviously there is no guarantee--there never is in these days of NSA-intercepted shipments, government-sponsored code changes, etc... There are plenty of steps you can take to minimize the risk of this happening though.
1. Use either Open Source software as your firewall platform (pfSense, m0n0wall, your own creation with pf or iptables, etc...), a firewall appliance based on open-source software that update frequently when vulnerabilities are disclosed (Mikrotik, Ubiquiti, etc...) or use enterprise-grade (even if it's used) hardware (Palo Alto, Cisco ASA, Fortinet, etc...) as long as you have access to software updates. Home and SOHO products aren't going to give you the kind of fine-grained controls you need to do this right. You minimally need VLAN support so you can have multiple WLANs to segregate your IoT devices.
2. Follow the vendor/developers best practices when configuring the above firewall. Don't expose any firewall management services to the internet or your IoT network. If your firewall supports any consumer-oriented crap like upnp, TURN IT OFF! Obviously, don't expose any real computers to the IoT network.
3. Subscribe to your vendors/developers mailing list. This way you can stay on top of any vulnerabilities as they are discovered, as workarounds are discovered, and as patches are released. Pretty much all the major vendors in item #1 have been on the front page of Slashdot within the last 2 years for some sort of vulnerability. It happens. Know about it when it does.
4. Patch your shit. Update your firewall often. Read the release notes so you know what you are fixing, then apply the patch.
Yes. I use a firewall. I suggest everyone else do the same with their IoT devices.
A trucker with a CB can send critical information 40 or 50 miles on the 11m band on a good day. Legally they are limited to 5w output. Even with a yagi, this is going to be tough.
HAMs (Skilled QRPers) on the other hand regularly communicate to other continents with 5w of power. Your typical 100-150W HF rig is going to be able to communicate anywhere in the world--or worst case, anywhere in the continental US. Some HAMs are also trained in emergency communications and/or formal traffic handling (to verify the accuracy of messages.) HAMs can use modes like SSTV (Slow Scan TV) to send an image of a piece of damaged infrastructure or a damaged building so engineers or rescuers can come in properly prepared. APRS mode is designed to update a real-time map of mobile and stationary transmitters using GPS. Information like this can also be critical in a disaster information. Rescuers won't have to guess where to look to find an injured person, etc... HAM radio is much more than Morse Code (CW) and people talking to each other like on CBs.
Just because you can't think of a reason doesn't mean they don't exist.
Here's a list of people you forgot:
People who regularly trailer cars or heavy equipment for whatever reason
People with non-European sized campers - see below
People with large boats - see below
When it comes to boats and campers, you are not taking wind resistance in to consideration. Many campers in the US are much taller than the tow vehicle causing massive amounts of wind resistance. This is a consideration along with weight. Same with any large boat. If it's sticking way above the roof of the towing vehicle, it probably shouldn't be towed by your sub-compact or little crossover.
Any trailer with brakes should be pulled by a full-size truck or SUV, especially if it's towed on a regular basis. Your little car may say it has a certain towing capacity, but that is assuming optimal conditions and new parts. If you are towing on a regular basis, you *will* put more strain on the drive train, suspension, and brakes than someone who doesn't. Most cars, minivans, and hatchbacks these days seem to be built as cheaply as possible so the extra wear and tear does make a difference. Vehicles that are purpose-built for this kind of work are generally heavy-duty enough to handle it.
It makes little to no financial sense, and is wasteful, to own a dedicated towing vehicle if towing is something you do even a handful to times a year. Most families can't afford more than 2 vehicles, so if towing is something needed and both adults are working, the tow vehicle needs to double as a commuter.
The only heavy haulage work involves moving concrete, sand, or building supplies, and if that's your gig then you need a light commercial vehicle.
At least in the US, full-size trucks are the light commercial vehicle of choice and are often driven to job sites by their owners. You can't really expect a construction worker--think of an independent contractor who for sure isn't making tons of money--to own a separate work vehicle.
A simple TCP port scan doesn't need root. You are just attempting to open a connection to a port on a given host or hosts. This is the same behavior every network-enabled application is using to establish a connection with a remote host. It's also exactly what ShieldsUp does.
Fancier nmap scans (SYN scan for example) do need root.
I suppose the authors of nmap didn't think their tool through correctly because it allows joe-random-employee at $office to portscan the ever loving shit out of every device behind the firewall.
Feel free to block the scanner. That's the appropriate response if you don't like having a port scan done. While you are at it, you should probably sit there and watch your firewall logs and block all of Shodan's bots, and all the malware-infected pcs hanging out there on the internet doing port scans. If you consider a port scan a threat to your office's or your company's security, you are relying on security by obscurity and are doing it wrong.
Oh, and SpinRite does work. I used to work at a university back in the days when floppies were the most common way for students to carry homework around. Every semester at finals time, we would have a few dozen students come in to the student support area in tears because their final/thesis/whatever was on a bad floppy and it was their only copy. I had about a 50% success rate with SpinRite. Better than nothing. I have also used SpinRite to get a drive back in good enough shape to pull an image before throwing it out. I've probably done this a dozen times over the years. I won't say it fixes the drive (or floppy disk), because it doesn't, and GRC doesn't claim it does. Generally the act of reading all the data just triggers the drive's internal ECC and it fixes itself by recovering from a spare sector.
Assuming the hinges don't crack, the laptop doesn't get dropped, the power connector doesn't break, the RAM doesn't fail, there aren't any capacitors waiting to blow, and there aren't any hidden cold joints in a BGA socket somewhere, I guess you will have to find a new distro 7 years from now.
Most laptops don't come close to lasting 10 years. Desktops are a bit better, but most of them have been 64-bit since 2006 or so. I don't think it's worth wasting a free software project's time and money to support such a fringe case. I'm sure there will be a demand for 32-bit distros in 2023. You will probably be able to use Gentoo, CentOS, Debian, one of the BSDs, or else some enterprising people will create a niche distribution to fill that gap in the market. You will be fine.
No reason to stop. If it does what you need, go ahead. I'm sure source-based distros like Gentoo will still be fine. Distros that focus on long term support like CentOS and Debian will probably still provide a 32-bit distro as well.
I would also like to point out that your 10-year-old laptop is having trouble now. Add another 7 years to that and you will be compounding those problems dramatically. I don't see any (desktop or laptop) computers around from 1999 that are terribly useful today. Some parts from a 15+ year old PC are hard to find nowadays (unless you have a huge stash or like risking your money on feebay.) Think IDE hard drives and DDR1 or SDRAM.
That is the plan as described by TFA.
Well, in 2018, the 2006 MacBook will be 12 years old. 18.04 is an LTS release and will have 5 years of support and security updates. By the time there are no more security patches, the machine will be 17 years old and software exploits will be the least of the user's concerns if it is still his/her main machine.
Kill Ugly Radio - Frank Zappa