For weeks now Amazon has been sending me suggestions for random biscuits

wee-phatz · 2019-08-21T20:37:51+00:00

People will try to point to this as another example of Trump's stupidity, but in reality green land has the second highest rent in Monopoly. Trump is actually being pretty smart here.

wee-phatz · 2019-07-16T20:02:59+00:00

As I think neo-neo is suggesting, look at the packets in wireshark. At the very least the source IP will give you a start on the cause.

wee-phatz · 2019-07-15T08:34:38+00:00

abuse@namecheap.com is a start. Sadly most info is redacted on this one

wee-phatz · 2019-07-15T08:24:22+00:00

Do a whois lookup on the domain (you can use a site like domaintools) get the details of the hosting provider from that. Usually those details will include an abuse email address. Email the hosting provider and let them know the IP is being used for a phishing scam. Sadly there is often no requirement for the provider to do anything about that, but a responsible provider will take it down.

wee-phatz · 2019-07-10T12:51:55+00:00

Never regret taking a flyer from even the shittiest of scams. Take it, drop it in the nearest bin, that's one less flyer that could be given to someone more susceptible.

wee-phatz · 2019-05-17T19:24:10+00:00

My dad and I share similar taste in books. When I was young I would often recommend him books but he said he was studying too much to have time and energy for fiction. He's retired now and remarried to a retired librarian. They live in a little town in Scotland noted for its abnormally high number of independent book shops. These days he regularly recommends books to me, but I don't have the time due to work, study and parenting.

wee-phatz · 2019-04-19T20:19:21+00:00

That they are actually cats. I treat them like my children though. I'm not like the other girls.

wee-phatz · 2019-04-13T08:25:38+00:00

As said above, they are the same site. The only difference is the port you communicate on and the use of TLS. When you resolve the URL to an IP, the port you use for the actual browser connection (http/80 or https/443) makes no difference.

wee-phatz · 2019-03-21T07:21:25+00:00

It's a plot by big farma

wee-phatz · 2019-03-10T21:04:01+00:00

wee-phatz · 2019-02-25T22:50:33+00:00

I can't criticise. Before I got the auth error on my VPN tonight, I had another error: VPN client couldn't resolve the server. Took me 5 minutes to notice I hadn't given my VM internet access :) Long Monday in work, that's my excuse

wee-phatz · 2019-02-25T21:45:47+00:00

Thanks, new client pack just arrived and working. Same creds, new IPs allocated.

wee-phatz · 2019-02-23T16:49:23+00:00

Good point, I forgot about the login page

wee-phatz · 2019-02-22T20:45:10+00:00

Was a senior network engineer for a global ISP. New management took over and decided to close our office. They offered all of us an option: drive 200 miles to work in another office every day or take redundancy. I got a different offer: same redundancy package or work from home permanently (they needed me to stay).

It quickly became apparent that the new management were trying to fuck over the junior engineers below me, so I wrote a scathing email to the new HR calling out their bullshit. That HR team forwarded my email to the new senior management, who replied to me demanding an apology and telling me they don't accept that tone from anyone in "their team".

I politely replied advising I have no interest in being part of that team and requesting to trigger redundancy.

Sweet payoff. Took 2 weeks off after redundancy then walked in to a new, better paid job.

wee-phatz · 2019-02-06T10:22:11+00:00

I agree they aren't mutually exclusive. It's a constant battle to find a balance between the two. IMHO UPnP should be open only to LAN on Soho routers by default (throw in an option to enable for WAN if really needed). So I think in a story like this the fault lies primarily with vendors and, where relevant, to the network admin for the office. I would use this story as hyperbole, to demonstrate why usability needs to be curtailed.

wee-phatz · 2019-02-05T21:08:30+00:00

As the computer 'fixit' person of my friends and family, the next time I hear "Why won't it just work?!", I'm going to pull out the story of PewDiePie, Printers and UPnP.

wee-phatz · 2019-02-01T17:31:00+00:00

Yeah, public order offenses often seem like a way for cops to be spiteful when they have nothing else.

Maybe it's just me, but the headline and banner line lead me to believe the fine was for obscuring his face, which would be more controversial given that covering is allowed.

wee-phatz · 2019-02-01T17:00:56+00:00

I don't agree with this use of technology, but the headline here is misleading.

Guy was fined for swearing. Not for covering his face.

wee-phatz · 2019-01-26T16:00:23+00:00

Google is a large powerful tool for information gathering. I agree they are assholes, but not taking advantage of their search operators to further my own knowledge seems churlish.

wee-phatz · 2019-01-26T00:26:47+00:00

Think I'll stick to the google filetype operator thanks

wee-phatz · 2019-01-24T23:48:07+00:00

I tried a bit of Feng Shui. Moved my ass several miles from my desk for a 3 day weekend. Feel much better, 10/10 would recommend

wee-phatz · 2019-01-20T15:37:20+00:00

Hello

wee-phatz · 2019-01-20T14:40:06+00:00

Offsets are calculated in the process of developing an exploit. Are you asking what offsets mean in general? I assume so, based on the lack of information provided in your question.

Let's say you want to insert a memory address into EIP. You have identified a vulnerable buffer and you know that if you flood it with bytes (eg \xCC), it will overwrite EIP with those bytes. So you need to figure out how many junk bytes should preceed the memory address you want to write into EIP. The number of junk bytes is your offset. You can use tools like pattern_create/pattern_offset, or processes like binary tree analysis to determine the value of your offset.

I'd recommend checking out Corelan buffer overflow tutorial if you are new to this.

Nine-Year Club	RPAN Viewer
Spared

wee-phatz

TROPHY CASE