farmersnotfighting

dog. https://theramswire.usatoday.com/2024/10/08/rams-jordan-whittington-wide-receiver-starter-2024/

https://www.therams.com/news/jordan-whittington-is-ascending-in-the-rams-wide-receiver-room good article. only bone i have to pick is when he said Jordan was recruited as a 5* RB out of high school. people always get that wrong. he was offered here first as a DB like sophomore year i think, declined, offered again junior year as a WR. accepted. came here and went straight to the WR room. then all those RB injuries happened and he volunteered to switch to RB with RoJo also switching from QB to RB. played freshman year as a RB. got hurt. went back to WR because RoJo wanted to stay as RB and Herman recruited Bijan so they didn't have that RB roster depletion anymore and he planned on being a WR anyway.

lol at everyone who said he didn't get separation. dude is and was always open.

https://www.pff.com/news/nfl-highest-graded-rookies-nfl-week-4 Highest PFF graded rookies through 4 weeks. J Whitt at 13. Also, Sweat at 5.

He should be used to having his touchdowns called back from his state championship game experience. McVay fucked up by not realizing Whittington gets angry about having his TD called back and scores the next play anyway.

Good little feature piece there. Damn. NFL production quality seems light years ahead of college. All the high definition slow-mo shit.

https://atozsports.com/college-football/texas-longhorns-news/salute-to-jordan-whittington-unbreakable-texas-longhorns-now-los-angeles-rams/

Officially made the 53 man team. https://athlonsports.com/college/longhorns-country/rookie-wr-jordan-whittington-makes-la-rams-53-man-roster ...and Stoops got cut. Eat shit ou.

https://ramblinfan.com/posts/2-nfl-experts-love-this-rams-coach-and-player-in-preseason-so-far-01j5t24p49ep

https://www.bleacherreport.com/articles/10132392-nfl-rookie-rankings-top-performers-after-2024-preseason-week-2 Top 10 rookie performers after 2 weeks. Worthy at 9, Whittington at 3. And he's on the list of highest graded rookies drafted on day 3.

Our boy getting love on Reddit

Your daily Jordan Whittington update:

Lots of good shots of our boy here. https://www.therams.com/photos/best-rams-gameday-cowboys-preseason-sofi-stadium-stetson-bennett-jordan-whittington#f7d03e96-3f9e-4dc2-a76a-d24e336cf67b 2 pics that tell you he's gonna be a leader there soon:

Mic'ed up. Seems pumped. Glad he's getting a chance to learn from Kupp and Stafford.

Highest PFF grade of any rookie WR last week. Probably should have thrown him the ball a couple of more times.

lol. neither did fireeye/mandiant when they got hacked. neither did RSA. neither did solarwinds. neither did FUCKING MICROSOFT. i'm not saying they're good. i'm saying they're not dog shit like you're suggesting. and again, at every org, security is understaffed, always screaming for changes and being ignored by management. every single company. that's not unique to lastpass. i do this for a living. i have seen a lot of organizations. fortune 10 and small orgs. including other security companies. i can count on one hand the number of orgs i've done engagements for where i never said "what the fuck are you doing here" and none of them were the security companies. you would be horrified to see how shitty some networks are only held up by gum and rubber bands, including major companies. the real world isn't a security+/cissp textbook.

lol i was talking chronologically through the attack. they were fine up until that point. they forced MFA on VPN usage. good for them. that puts them ahead of most orgs and is a huuuuge barrier to an attacker trying to gain initial access. having a low attack surface that's hardened, implementing MFA... forcing an attacker to pwn a dev's home network is very very good. oh and i was wrong about plex. it wasn't a 0day. apparently it was a known vuln. but still. identifying the target developer, finding his home network range, exploiting plex, that's a very time consuming attack. so kudos to the attacker there. the million dollar question still is how did they go from home network access to dev workstation access.

lazy with their monitoring and didn't notice someone walking out with everything. And lazy about separating prod and dev environments. as someone who breaks in to network for a living, i can assure you this is not unique to lastpass lol. as far as i know, lastpass breach was decently done. the dev was running a plex server at home. someone threw a 0day RCE at it from the outside and used that to pivot into his network. i dont think they ever disclosed how the attacker went from network access to actually owning the dev's box. but from there, they waited until he already logged in to the vpn (after he put in his MFA), and rode the connection in that way back to the lastpass network. so far so good. lastpass did everything right and the attack took a lot of resources to carry out. but where they fucked up was the dev having access to the prod data. i'm guessing they did the right thing and had all the data in multiple accounts (separate AWS account for prod, different one for dev, different one for staging). no access to each other. cool. but the dev probably had access to both (or all?) of the accounts, so the attackers could just ride in to the prod account as the developer. again, i haven't seen any details on this part of the breach, but i've seen (and done) this exact thing (well... similar -- SE to get code execution on developer company workstations while they work from home - not attacking personal devices. that's illegal) many times. you absolutely could physically write down a long password on paper for person use at home (as long as you can keep it secure). you are infinitely more likely to get your box randomly hacked than a fucking thief breaking in to your house, finding your password paper, and getting away with it. if they did that shit, you have way more problems to worry about than losing passwords. this is basically a discussion in threat modeling. who is mostly likely to attack you? how will they do it? is writing a password on paper perfect or great? no. is it less likely to be stolen than a file on your computer? yes... or probably. as long as you have a safe place for it that your wife/kids/dog can't get to it or damage it.

yeah you can use whatever service you want. lastpass had the market share since they were the first mainstream service so they got targeted. i can assure you 1pass and bitwarden will be compromised in the future if they aren't already. for any of these services, you're going to have to trust that they're doing the right thing and you wont know until it's too late. you can use a local wallet type of thing like keepass, but then you loose the synching capabilities between your computer and mobile device. and idk if they have browser addons or anything so it will make your process of getting your password out even longer. and your computer is more likely to be compromised and have your keepass file stolen that one of the larger companies focusing on keeping it safe. so now you're looking at how strong is your local master keepass file once someone takes it? and if that's the main question, then you don't really have a difference between local keepass and a cloud based one like 1P or bitwarden, or even lastpass. if you remember the lastpass breach, they stole the encrypted key vaults, not cleartext passwords inside. so you still need to crack the hash to your vault either way. lastpass uses aes-256 (good), so does 1password, so does bitwarden. keepass uses aes256 too, so now the only real difference is features in what you want in a password manager and who you trust more. and making damn sure you have a strong password to your vault no matter what since that's the master key to the kingdom.

pretty sure inchworm was an aggy. can someone photoshop the furk guy with an inchworm crawling out of his britches?

salting is literally to stop a rainbow attack lol. but nobody sits around with rainbow tables anymore since basically everything is salting by default now. invision community moved from md5 which is fucking awful (164,000,000,000 password guesses per second on a 4090) to blowfish (184,000,000 guesses/second) for the hashing algorithm. if you use a shit password like Summer2024! or Password1! or something that's on a common password list (check here: https://github.com/danielmiessler/SecLists/tree/master/Passwords/Leaked-Databases ) then consider your username/email address and password compromised. make sure you don't reuse that password for any other site. in general, use MFA where possible. and if you're too lazy to do that, make sure you have different passwords for every site that are randomly generated. no you aren't clever using "Password.Surly". if i see your email and "password.linkedin" or "password.gmail" or "password.facebook" in a breach, i'm damn sure gonna try "password.surly" if i'm targeting you. but use a password manager like lastpass or 1pass to generate and keep track of your passwords for different sites. they have browser addons and phone apps so you can auto fill shit too.

Classic.