<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><blockquote type="cite"><div>Mail scares me. I had to send my LEA ID in recently via USPS. I'm hoping <br></div><div>they got it.<br></div></blockquote><div><br></div><div>With how unreliable mail is, I still can't believe that we use it for anything official.<br></div><div><br></div><div>For instance, jury duty notices. Don't respond or never received it? Well, depending on the state and whether a judge is feeling crabby that day, you not responding to a notice you never got will result in a bench warrant issued for you. Imagine just going along your day and cop pulling you over and arresting you because you had a bench warrant for a notice you never received. And when that does happen, I highly doubt you'll be able to get any kind of restitution from the state or federal government over being arrested due to something being lost in the mail.<br></div><div><br></div><div><a href="https://www.msn.com/en-us/news/crime/man-says-he-didn-t-show-up-for-jury-duty-after-his-summons-arrived-over-two-months-late-metro-atlanta-mail-delays/ar-BB1oaPbX">https://www.msn.com/en-us/news/crime/man-says-he-didn-t-show-up-for-jury-duty-after-his-summons-arrived-over-two-months-late-metro-atlanta-mail-delays/ar-BB1oaPbX</a><br></div><div><br></div><div>On that note I've had the displeasure of going through jury duty and serving on a jury in Atlanta. There are so many cases and so many people called for jury duty that you're just treated like cattle.<br></div><div><br></div><div>On Thu, Jul 4, 2024, at 2:23 PM, George Toft via PLUG-discuss wrote:<br></div><blockquote type="cite" id="qt" style=""><div><scroll><br></div><div><br></div><div>Regards,<br></div><div><br></div><div>George Toft<br></div><div><br></div><div>On 7/4/2024 6:50 AM, <a href="mailto:techlists@phpcoderusa.com">techlists@phpcoderusa.com</a> wrote:<br></div><div>> Thank you so much George!!<br></div><div>><br></div><div>> Another Question. I was a police officer in the 80's and 90's. During <br></div><div>> my tenure the bank was on the hook for any criminal acts as long as <br></div><div>> the customer was not negligent. I only dealt with this on a couple <br></div><div>> occasional.<br></div><div>><br></div><div>> So If someone gets access to my online banking and I report it in a <br></div><div>> timely manner, or if someone washes one of my checks and I report it <br></div><div>> in a timely manner, is the bank on the hook or am I?<br></div><div><br></div><div>There are a ton of rules with more acronyms than the IT world has. I <br></div><div>would love to tell you what I understand, but I'd be talking out my ass.<br></div><div><br></div><div><br></div><div>> BTW I thought going old school was the most secure. I do not trust <br></div><div>> the Internet. My daily driver is a Linux Box and I do not use my <br></div><div>> cellular phone for anything except to talk and read some news. I am <br></div><div>> semiretired and have home officed for a long time.<br></div><div><br></div><div>Not sure there is any magic incantation that I can say that would put <br></div><div>you at ease, other than "Risk Analysis," "Government Regulation," "Audit <br></div><div>and Reviews," "Compliance," "Controls and Countermeasures," and "Fines." <br></div><div>We have to comply with a bazillion rules all designed to protect you, <br></div><div>the bank customer. Some regions are really strict and their governments <br></div><div>show they really care, like the EU - their rules are so restrictive. <br></div><div>Here's an example: You cannot log into a server that serves the EU if <br></div><div>Payment Card Information (PCI) is involved with the same user ID that <br></div><div>you used to log into your work station. This prevents lateral movement <br></div><div>from an insider attack should the attacker get an employee's credentials <br></div><div>or Kerberos TGT (Hey!!! It's now on-topic!!!) . This is just an example. <br></div><div>We have external inspectors and government auditors on site almost every <br></div><div>two weeks making us prove compliance with all the rules, and the bigger <br></div><div>we get, the more rules and more regulatory auditors we get to talk to. <br></div><div>We actually have two people on my team of 27 whose job used to be <br></div><div>project management, now is audit and compliance. All of this to protect you.<br></div><div><br></div><div>Let's not forget about the Security Operations Center monitoring <br></div><div>employee activities. Refer to the GTFOBins email from yesterday. I <br></div><div>documented a chained attack to get root based on that page, and the SOC <br></div><div>came knocking saying "George, we noticed suspicious activity on this <br></div><div>server and this date. Whatcha doin'?" Fortunately, I documented <br></div><div>everything and emailed it to my manager, so all I had to do was forward <br></div><div>that back to the SOC.<br></div><div><br></div><div>Mail scares me. I had to send my LEA ID in recently via USPS. I'm hoping <br></div><div>they got it.<br></div><div><br></div><div><br></div><div>> Any suggestions are appreciated.<br></div><div>><br></div><div>><br></div><div>><br></div><div>> On 2024-07-03 21:48, George Toft wrote:<br></div><div>>> Sorry, Kieth, I have bad news for you. You took a 30+ year leap <br></div><div>>> backwards in security.<br></div><div>>><br></div><div>>> I can tell you for certain, from my bank fraud analyst friend (just <br></div><div>>> got promoted to financial crimes investigator), checks are the second <br></div><div>>> most insecure way of transferring money, first being putting the <br></div><div>>> money in the envelope. They helped the USPS bust a fraud ring who <br></div><div>>> worked in the Post Office - fraudsters were pulling checks out of <br></div><div>>> envelopes inside the local Post Office. My friend pulled out all the <br></div><div>>> details for the Postmaster General.<br></div><div>>><br></div><div>>> ACH is free (for you) and secure and guaranteed by the originator as <br></div><div>>> they are on the hook to prove the identity of who initiated the <br></div><div>>> transaction and they have to pay. It's all very complicated, and I'm <br></div><div>>> not going into details here.<br></div><div>>><br></div><div>>> I use ACH all the time. My physical devices have multi-layer physical <br></div><div>>> protection. Logical access control is in-place. Both have <br></div><div>>> multi-factor authentication. Password resets require multi-factor <br></div><div>>> authentication.<br></div><div>>><br></div><div>>> And the DoD is worse - their systems have so many layers, it was <br></div><div>>> easier to just let my account get deleted from lack of use and <br></div><div>>> rebuilt it from scratch. I have notes that tell me screen-by-screen <br></div><div>>> what to put in each box and which ones to ignore. It's so secure, <br></div><div>>> legitimate users can't even get in... and this is just my health <br></div><div>>> insurance.<br></div><div>>><br></div><div>>> Where all of this can break down - getting on topic - is with the SSH <br></div><div>>> protocol and web proxies. When you connect to a website using HTTPS <br></div><div>>> using a web proxy, your web browser uses it's cert to set up the <br></div><div>>> connection, or so it thinks. What's really happening is the proxy is <br></div><div>>> responding to the request and decrypting the message, then it forms a <br></div><div>>> new request and sends it to the bank, which believes the proxy and <br></div><div>>> sends it back. Everything gets decrypted on the proxy, so whoever has <br></div><div>>> admin access to the proxy can see everything. Kinda like opening <br></div><div>>> envelopes in the mail room :) Disclaimer: This is what some <br></div><div>>> networking guys told me in a presentation about 10 years ago.<br></div><div>>><br></div><div>>> In summary, ACH is safe if you do it from home without a proxy. Of <br></div><div>>> course "safe" is relative, but it's safer than checks in the mail. <br></div><div>>> Drop into your bank and ask the branch manager, or call their <br></div><div>>> customer service and ask. They won't tell you checks are bad, but <br></div><div>>> they will steer you to ACH and tell you it's better. Break out the <br></div><div>>> Rosetta Stone and figure out what "better" means in corporate-speak. <br></div><div>>> Banks are in it to win it, and they don't offer something for free <br></div><div>>> unless they are saving money (cost avoidance) on the alternatives.<br></div><div>>><br></div><div>>> Regards,<br></div><div>>><br></div><div>>> George Toft<br></div><div>>><br></div><div>>> On 7/3/2024 6:21 AM, <a href="mailto:techlists@phpcoderusa.com">techlists@phpcoderusa.com</a> wrote:<br></div><div>>>> <scroll><br></div><div>>>><br></div><div>>>> On 2024-07-02 18:20, George Toft via PLUG-discuss wrote:<br></div><div>>>>> I work for a bank, and you would be amazed at how much security is <br></div><div>>>>> baked into the connecting your browser to their web servers. Makes <br></div><div>>>>> the NSA look like freshmen. And no, I'm not telling you who I work <br></div><div>>>>> for.<br></div><div>>>>><br></div><div>>>>> Regards,<br></div><div>>>>><br></div><div>>>>> George Toft<br></div><div>>>><br></div><div>>>> I'd like to hear more. The world is a hostile place. I recently <br></div><div>>>> went old school. I asked the bank to disarm my online banking. I <br></div><div>>>> now deal with paper statements and everything gets paid by check. <br></div><div>>>> Not as convenient as on-line banking, however I am hoping it makes <br></div><div>>>> my world a little bit more secure.<br></div><div>>>><br></div><div>>>> What are your thoughts?<br></div><div>>>><br></div><div>>>> Keith<br></div><div>>>><br></div><div>>>><br></div><div>>>><br></div><div>>>><br></div><div>>>><br></div><div>>>>><br></div><div>>>>> On 6/29/2024 5:19 PM, Keith Smith via PLUG-discuss wrote:<br></div><div>>>>>> Mike,<br></div><div>>>>>><br></div><div>>>>>> The world is a hostile place. The more precautions you take the <br></div><div>>>>>> better. I cover the camera on my cellular phone while not in <br></div><div>>>>>> use. I cover the camera that is built into my laptop while it is <br></div><div>>>>>> not in use. I think on-line banking is dangerous. At some point <br></div><div>>>>>> I want to turn off WIFI and go to wired only on my local net.<br></div><div>>>>>><br></div><div>>>>>> We lock our cars and houses for a reason.<br></div><div>>>>>><br></div><div>>>>>> I do not know as much security as I'd like, however it might be <br></div><div>>>>>> necessary at some point to to become more cyber.<br></div><div>>>>>><br></div><div>>>>>> About 24 years ago the members of the Tucson Free Unix Group <br></div><div>>>>>> (TFUG) helped me build a server that I ran out of my home. We <br></div><div>>>>>> left the email relay open and I got exploited. About 10 years ago <br></div><div>>>>>> I became root and I accidentally overwrote my home directory. <br></div><div>>>>>> yikes... both were painful. The first example is a reason we must <br></div><div>>>>>> be more aware of what we are doing. The 2nd is an example why we <br></div><div>>>>>> should use sudo as much as we can instead of becoming root.<br></div><div>>>>>><br></div><div>>>>>> Keith<br></div><div>>>>>><br></div><div>>>>>><br></div><div>>>>>><br></div><div>>>>>> On 2024-06-29 08:55, Michael via PLUG-discuss wrote:<br></div><div>>>>>>> I just realized, while 99% of the people on this list are honest <br></div><div>>>>>>> there<br></div><div>>>>>>> is the diabolical 1%. So I guess I enter my password for the rest of<br></div><div>>>>>>> my life. Or do you think that it really matters considering this is<br></div><div>>>>>>> only a mailing list?<br></div><div>>>>>>><br></div><div>>>>>>> On Sat, Jun 29, 2024, 10:22 AM Michael <<a href="mailto:bmike1@gmail.com">bmike1@gmail.com</a>> wrote:<br></div><div>>>>>>><br></div><div>>>>>>>> Thanks for saying this. I realized that I only needed to run apt as<br></div><div>>>>>>>> root. I didn't know how to make it so I could do that..... but<br></div><div>>>>>>>> chatgt did!<br></div><div>>>>>>>><br></div><div>>>>>>>> On Sat, Jun 29, 2024, 5:53 AM Eric Oyen via PLUG-discuss<br></div><div>>>>>>>> <<a href="mailto:plug-discuss@lists.phxlinux.org">plug-discuss@lists.phxlinux.org</a>> wrote:<br></div><div>>>>>>>><br></div><div>>>>>>>>> NO WORRIES FROM THIS END RUSTY.<br></div><div>>>>>>>>><br></div><div>>>>>>>>> As a general rule, I use sudo only for very specific tasks<br></div><div>>>>>>>>> (usually updating my development package tree on OS X) and no<br></div><div>>>>>>>>> where else will I run anything as root. I have seen what happens<br></div><div>>>>>>>>> to linux machines that run infected binaries as root and it can<br></div><div>>>>>>>>> get ugly pretty fast. In one case, I couldn’t take the machine<br></div><div>>>>>>>>> out of service because of other items I was involved with, so I<br></div><div>>>>>>>>> simply made part of the dir tree immutable after replacing a few<br></div><div>>>>>>>>> files in /etc. That would fill up the system logs with an error<br></div><div>>>>>>>>> message about a specific binary trying to replace a small number<br></div><div>>>>>>>>> of conf files. Once the offending binary was found, it made things<br></div><div>>>>>>>>> easier trying to disable it or get rid of it. However, after a<br></div><div>>>>>>>>> while, I simply pulled the drive and ran it through a Dod secure<br></div><div>>>>>>>>> erase and installed a newer linux bistro on it. I did use the same<br></div><div>>>>>>>>> trick with chattr to make /bin, /sbin and /etc immutable. That<br></div><div>>>>>>>>> last turned out to be handy as I caught someone trying to rootkit<br></div><div>>>>>>>>> my machine using a known exploit, only they couldn’t get it to<br></div><div>>>>>>>>> run because the binaries they wanted to replace couldn’t be<br></div><div>>>>>>>>> written to. :)Yes, this would be a bit excessive, but over the<br></div><div>>>>>>>>> long run, proved far less inconvenient than having to wipe and<br></div><div>>>>>>>>> reinstall an OS.<br></div><div>>>>>>>>><br></div><div>>>>>>>>> -Eric<br></div><div>>>>>>>>> From the central Offices of the Technomage Guild, security<br></div><div>>>>>>>>> Applications Dept.<br></div><div>>>>>>>>><br></div><div>>>>>>>>>> On Jun 28, 2024, at 6:43 PM, Rusty Carruth via PLUG-discuss<br></div><div>>>>>>>>> <<a href="mailto:plug-discuss@lists.phxlinux.org">plug-discuss@lists.phxlinux.org</a>> wrote:<br></div><div>>>>>>>>>><br></div><div>>>>>>>>>> (Deep breath. Calm...)<br></div><div>>>>>>>>>><br></div><div>>>>>>>>>> I can't figure out how to respond rationally to the below, so<br></div><div>>>>>>>>> all I'm going to say is - before you call troll, you might want<br></div><div>>>>>>>>> to research the author, and read a bit more carefully what they<br></div><div>>>>>>>>> wrote. I don't believe I recommended any of the crazy things you<br></div><div>>>>>>>>> suggest. And I certainly didn't intend to imply any of that.<br></div><div>>>>>>>>>><br></div><div>>>>>>>>>> On the other hand, it may not have been clear, so I'll just say<br></div><div>>>>>>>>> "Sorry that what I wrote wasn't clear, but english isn't my first<br></div><div>>>>>>>>> language. Unfortunately its the only one I know".<br></div><div>>>>>>>>>><br></div><div>>>>>>>>>> And on that note, I'll shut up.<br></div><div>>>>>>>>>><br></div><div>>>>>>>>>> On 6/26/24 15:05, Ryan Petris wrote:<br></div><div>>>>>>>>>>> I feel like you're trolling so I'm not going to spend very much<br></div><div>>>>>>>>> time on this.<br></div><div>>>>>>>>>>><br></div><div>>>>>>>>>>> It's been a generally good security practice for at least the<br></div><div>>>>>>>>> last 25+ years to not regularly run as a privileged user,<br></div><div>>>>>>>>> requiring some sort of escalation to do administrative-type tasks.<br></div><div>>>>>>>>> By using passwordless sudo, you're taking away that escalation.<br></div><div>>>>>>>>> Why not just run as root? Then you don't need sudo at all. In<br></div><div>>>>>>>>> fact, why even have a password at all? Why encrypt? Why don't you<br></div><div>>>>>>>>> just put all your data on a publicly accessible FTP server and<br></div><div>>>>>>>>> just grab stuff when you need it? The NSA has all your data anyway<br></div><div>>>>>>>>> and you don't have anything to hide so why not just leave it out<br></div><div>>>>>>>>> there for the world to see?<br></div><div>>>>>>>>>>><br></div><div>>>>>>>>>>> As for something malicious needing to be written to use sudo,<br></div><div>>>>>>>>> why wouldn't it? sudo is ubiquitous on unix systems; if it didn't<br></div><div>>>>>>>>> at least try then that seams like a pretty dumb malicious script<br></div><div>>>>>>>>> to me.<br></div><div>>>>>>>>>>><br></div><div>>>>>>>>>>> You also don't necessarily need to open/run something for it to<br></div><div>>>>>>>>> run. IIRC there was a recent image vulnerability in Gnome's<br></div><div>>>>>>>>> tracker-miner application which indexes files in your home<br></div><div>>>>>>>>> directory. And before you say that wouldn't happen in KDE, it too<br></div><div>>>>>>>>> has a similar program, I believe called Baloo.<br></div><div>>>>>>>>>>><br></div><div>>>>>>>>>>> There also exists the recent doas program and the systemd<br></div><div>>>>>>>>> replacement run0 to do the same.<br></div><div>>>>>>>>>>><br></div><div>>>>>>>>>>> On Wed, Jun 26, 2024, at 12:23 PM, Rusty Carruth via<br></div><div>>>>>>>>> PLUG-discuss wrote:<br></div><div>>>>>>>>>>>> Actually, I'd like to start a bit of a discussion on this.<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> First, I know that for some reason RedHat seems to think that<br></div><div>>>>>>>>> sudo is<br></div><div>>>>>>>>>>>> bad/insecure.<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> I'd like to know the logic there, as I think the argument FOR<br></div><div>>>>>>>>> using sudo<br></div><div>>>>>>>>>>>> is MUCH stronger than any argument I've heard (which,<br></div><div>>>>>>>>> admittedly, is<br></div><div>>>>>>>>>>>> pretty close to zero) AGAINST it. Here's my thinking:<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> Allowing users to become root via sudo gives you:<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> - VERY fine control over what programs a user can use as root<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> - The ability to remove admin privs (ability to run as root)<br></div><div>>>>>>>>> from an<br></div><div>>>>>>>>>>>> individual WITHOUT having to change root password everywhere.<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> Now, remember, RH is supposedly 'corporate friendly'. As a<br></div><div>>>>>>>>> corporation,<br></div><div>>>>>>>>>>>> that 2nd feature is well worth the price of admission, PLUS I<br></div><div>>>>>>>>> can only<br></div><div>>>>>>>>>>>> allow certain admins to run certain programs? Very nice.<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> So, for example, at my last place I allowed the 'tester' user<br></div><div>>>>>>>>> to run<br></div><div>>>>>>>>>>>> fdisk as root, because they needed to partition the disk under<br></div><div>>>>>>>>> test. In<br></div><div>>>>>>>>>>>> my case, and since the network that we ran on was totally<br></div><div>>>>>>>>> isolated from<br></div><div>>>>>>>>>>>> the corporate network, I let fdisk be run without needing a<br></div><div>>>>>>>>> password.<br></div><div>>>>>>>>>>>> Oh, and if they messed up and fdisk'ed the boot partition, it<br></div><div>>>>>>>>> was no big<br></div><div>>>>>>>>>>>> deal - I could recreate the machine from scratch (minus<br></div><div>>>>>>>>> whatever data<br></div><div>>>>>>>>>>>> hadn't been copied off yet - which would only be their most<br></div><div>>>>>>>>> recent run),<br></div><div>>>>>>>>>>>> in 10 minutes (which was about 2 minutes of my time, and 8<br></div><div>>>>>>>>> minutes of<br></div><div>>>>>>>>>>>> scripted 'dd' ;-) However, if the test user wanted to become<br></div><div>>>>>>>>> root using<br></div><div>>>>>>>>>>>> su, they had to enter the test user password.<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> So, back to the original question - setting sudo to not<br></div><div>>>>>>>>> require a<br></div><div>>>>>>>>>>>> password. We should have asked, what program do you want to<br></div><div>>>>>>>>> run as root<br></div><div>>>>>>>>>>>> without requiring a password? How secure is your system? What<br></div><div>>>>>>>>> else do<br></div><div>>>>>>>>>>>> you use it for? Who has access? etc, etc, etc.<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> There's one other minor objection I have to the 'zero defense'<br></div><div>>>>>>>>> statement<br></div><div>>>>>>>>>>>> below - the malicious thing you downloaded (and, I assume ran)<br></div><div>>>>>>>>> has to be<br></div><div>>>>>>>>>>>> written to USE sudo in its attempt to break in, I believe, or<br></div><div>>>>>>>>> it<br></div><div>>>>>>>>>>>> wouldn't matter HOW open your sudo was. (simply saying 'su -<br></div><div>>>>>>>>> myscript'<br></div><div>>>>>>>>>>>> won't do it).<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> And, if you're truly paranoid about stuff you download, you<br></div><div>>>>>>>>> should:<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> 1 - NEVER download something you don't have an excellent<br></div><div>>>>>>>>> reason to<br></div><div>>>>>>>>>>>> believe is 'safe', and ALWAYS make sure you actually<br></div><div>>>>>>>>> downloaded it from<br></div><div>>>>>>>>>>>> where you thought you did.<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> 2 - For the TRULY paranoid, have a machine you use to download<br></div><div>>>>>>>>> and test<br></div><div>>>>>>>>>>>> software on, which you can totally disconnect from your<br></div><div>>>>>>>>> network (not<br></div><div>>>>>>>>>>>> JUST the internet), and which has NO confidential info, and<br></div><div>>>>>>>>> which you<br></div><div>>>>>>>>>>>> can erase and rebuild without caring. Run the downloaded<br></div><div>>>>>>>>> stuff there,<br></div><div>>>>>>>>>>>> for a long time, until you're pretty sure it won't bite you.<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> 3 - For the REALLY REALLY paranoid, don't download anything<br></div><div>>>>>>>>> from<br></div><div>>>>>>>>>>>> anywhere, disconnect from the internet permanently, get<br></div><div>>>>>>>>> high-tech locks<br></div><div>>>>>>>>>>>> for your doors, and wrap your house in a faraday cage!<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> And probably don't leave the house....<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> The point of number 3 is that there is always a risk, even<br></div><div>>>>>>>>> with<br></div><div>>>>>>>>>>>> 'well-known' software, and as someone else said - they're<br></div><div>>>>>>>>> watching you<br></div><div>>>>>>>>>>>> anyway. The question is how 'safe' do you want to be? And how<br></div><div>>>>>>>>> paranoid<br></div><div>>>>>>>>>>>> are you, really?<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> Wow, talk about rabbit hole! ;-)<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> 'Let the flames begin!' :-)<br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>>>> On 6/25/24 18:50, Ryan Petris via PLUG-discuss wrote:<br></div><div>>>>>>>>>>>>>> wanted sudo not to require a password.<br></div><div>>>>>>>>>>>>> Please reconsider this... This is VERY BAD security practice.<br></div><div>>>>>>>>> There's basically zero defense if you happen to download/run<br></div><div>>>>>>>>> something malicious.<br></div><div>>>>>>>>>>>>><br></div><div>>>>>>>>>>>>> On Tue, Jun 25, 2024, at 6:01 PM, Michael via PLUG-discuss<br></div><div>>>>>>>>> wrote:<br></div><div>>>>>>>>>>>>>> then I remember that a PLUG member mentioned ChatGPT being<br></div><div>>>>>>>>> good at troubleshooting so I figured I'd give it a go. I sprint<br></div><div>>>>>>>>> about half an hour asking it the wrong question but after that it<br></div><div>>>>>>>>> took 2 minutes. I wanted sudo not to require a password. it is<br></div><div>>>>>>>>> wonderful! now I don't have to bug you guys. so it looks like this<br></div><div>>>>>>>>> is the end of the user group unless you want to talk about OT<br></div><div>>>>>>>>> stuff.<br></div><div>>>>>>>>>>>>>><br></div><div>>>>>>>>>>>>>> -- :-)~MIKE~(-:<br></div><div>>>>>>>>>>>>>> ---------------------------------------------------<br></div><div>>>>>>>>>>>>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br></div><div>>>>>>>>>>>>>> To subscribe, unsubscribe, or to change your mail settings:<br></div><div>>>>>>>>>>>>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></div><div>>>>>>>>>>>>>><br></div><div>>>>>>>>>>>>> ---------------------------------------------------<br></div><div>>>>>>>>>>>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br></div><div>>>>>>>>>>>>> To subscribe, unsubscribe, or to change your mail settings:<br></div><div>>>>>>>>>>>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></div><div>>>>>>>>>>>> ---------------------------------------------------<br></div><div>>>>>>>>>>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br></div><div>>>>>>>>>>>> To subscribe, unsubscribe, or to change your mail settings:<br></div><div>>>>>>>>>>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></div><div>>>>>>>>>>>><br></div><div>>>>>>>>>> ---------------------------------------------------<br></div><div>>>>>>>>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br></div><div>>>>>>>>>> To subscribe, unsubscribe, or to change your mail settings:<br></div><div>>>>>>>>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></div><div>>>>>>>>><br></div><div>>>>>>>>> ---------------------------------------------------<br></div><div>>>>>>>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br></div><div>>>>>>>>> To subscribe, unsubscribe, or to change your mail settings:<br></div><div>>>>>>>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></div><div>>>>>>> ---------------------------------------------------<br></div><div>>>>>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br></div><div>>>>>>> To subscribe, unsubscribe, or to change your mail settings:<br></div><div>>>>>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></div><div>>>>>> ---------------------------------------------------<br></div><div>>>>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br></div><div>>>>>> To subscribe, unsubscribe, or to change your mail settings:<br></div><div>>>>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></div><div>>>>> ---------------------------------------------------<br></div><div>>>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br></div><div>>>>> To subscribe, unsubscribe, or to change your mail settings:<br></div><div>>>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></div><div>---------------------------------------------------<br></div><div>PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br></div><div>To subscribe, unsubscribe, or to change your mail settings:<br></div><div><a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></div><div><br></div></blockquote><div><br></div></body></html>