--- Log opened Fri Dec 18 00:00:08 2020
05:42 <@Dolemite> mr0ning, be0tches and h0 h0 h0ez!
06:01 <@Mirage> morning?   shit, I haven't been to bed yet.
06:02 <@Mirage> will be soon, though
06:03 <@Mirage> no work next week...not officially anyway, so of course everything's on a 'get it done asap before the break' deadline
06:07 <@Dolemite> I'm working M-W next week
06:07 <@Dolemite> But we're in the middle of a change freeze
06:07 <@Dolemite> So basically I'm relocating to the basement M-W next week during the day.   heh
06:08 <@Dolemite> I had to come back downstairs twice last night.   Storage admin rebooted the Isilon twice without warning.  MySQL clusters were not happy about that.
06:08 <@Dolemite> s/MySQL/MariaDB
06:09 <@Mirage> same difference
06:09 <@Dolemite> To us old farts, yes
06:10 <@Dolemite> Twitter and the White House have both denied reports that a Dutch security researcher was able to log into Donald Trump’s infamous Twitter account with the impossibly easy to guess password “MAGA2020!” But it turns out that really did happen, at least according to Dutch prosecutors.
06:10 <@Mirage> right now i'm having fun trying to figure out how to make a 'powershell' gnome-terminal profile that's shared or created for new users when they first log in.   So fucking annoying..
06:12 <@Dolemite> I've managed to resist learning much of anything related to PowerShell for 50 years.  I don't intend to change that.
06:13 <@Mirage> Well, since we;re moving to CentOS for our jump boxes vs Windows Server 2019, it's kind of a requirement to have powershell installed to be able to run VMware power-cli, power-nsx, etc for managing all the infrastructure.
06:14 <@Mirage> Setting up a powershell terminal for a single user is easy, but i can't for the life of me figure out how to properly set a default profile available to all users
06:57 <@Evilpig> wheee!  we get to patch all the F5s today to prevent another XSS exploit that's being actively leveraged
06:58 <@Evilpig> https://portswigger.net/daily-swig/amp/f5-warns-over-critical-xss-flaw-in-big-ip
06:58 < PigBot> F5 warns over ‘critical’ XSS flaw in BIG-IP | The Daily Swig (at portswigger.net) https://tinyurl.com/ya22dce3
07:19 -!- xray7 [~xray@c-71-236-3-132.hsd1.ga.comcast.net] has joined #se2600
07:21 -!- xray [~xray@c-73-43-3-64.hsd1.ga.comcast.net] has quit [Ping timeout: 240 seconds]
07:21 -!- xray7 is now known as xray
15:47 <@Mirage> our security ppl are fucking idiots. (no suprise I'm sure)  They were testing a new VPN tunnel to the management stack for a new customer and asked me to please turn on the jump host so that they could verify connectivity.   Told them it was on..then through the course of the conversation finally figured out that they were trying to rdp to it.
15:48 <@Mirage> Told them to just SSH to it.  They said only 3389/tcp was open on the tunnels.  I said, ok, i'll fire up another instance of ssh on 3389 for testing then.
15:49 <@Mirage> They then informed me that 'an ssh client' was not part of the standard build in the citrix vdi environment used to connect, but grudginly said they could submit a change to get putty installed.
15:50 <@Mirage> Told them while they were at it that VNC Viewer needed to be added as well.
15:52 <@Mirage> Their response was that VNC was not and would never be approved because it's an insecure protocol.   I said, yeah...that's why we'll be tunneling it through SSH.  At this point they told me that I couldn't make unilateral decisions like this w/o approval.  I told them I was just an indian and doing what I was directed to do by my management and that they should take it up with them...so next thing I know they start dragging project managers, managers, and di
16:26 <@Evilpig> oh gees
16:26 <@Evilpig> I use vnc in the house without tunneling and it's encrypted too
16:28 <@Evilpig> I think our security guys will give yours a run for the money in the shit for brains department though
16:30 <@Evilpig> dummy user decides that after patching last night his app isn't working and opens a ticket to security because the firewall is obviously failing now.  user puts source address <his server name> <ip address of our dns server>  and the destination address as <his other server name> <correct destination ip>
16:30 <@Evilpig> a competent person would verify those addresses before just running off and making firewall rules, but not this gem.  nope he opened up some random 4000 port from our dns server float to this whatever system
16:31 <@Evilpig> I point out the mistake to the brainiac and send screenshots showing all the addresses involved and he responds with "Im not familiar with the screenshots you sent? What is the issue going on?"
16:32 <@Evilpig> we then get an incident from the end user that sent them the wrong firewall ticket complaining that they fixed the rule and it still wasn't working.  I send that incident to the brainiac in security and reads the comments on the incidnet where one of my teammates spelled it out for him and he still didn't get it
16:33 <@Evilpig> I took that entire conversation and sent it to his boss that responded to me with a gif of a headdesk and a question of how it made it past the brainiac in the first place
17:31 -!- k3ymkr [~KeyMaker@ec2-52-6-16-39.compute-1.amazonaws.com] has quit [Remote host closed the connection]
17:31 -!- k3ymkr [~KeyMaker@ec2-52-6-16-39.compute-1.amazonaws.com] has joined #se2600
20:24 -!- xray [~xray@c-71-236-3-132.hsd1.ga.comcast.net] has quit [Quit: The Lounge - https://thelounge.chat]
20:25 -!- xray [~xray@c-71-236-3-132.hsd1.ga.comcast.net] has joined #se2600
--- Log closed Sat Dec 19 00:00:09 2020