Re: revolting restaurant more like
When I visited (2015? It was some anniversary or other, and there was a ballot to get the opportunity to visit and dine there), it was being run by Searcy.
Had a nice lunch, as we were slowly rotated.
170 publicly visible posts • joined 5 Aug 2009
What value is anyone still getting out of Squid?
We found it very useful 25+ (time flies…) years ago, but the internet is different now. If I were forward proxying, well, I would be surprised if there were any gains these days from caching. If I were reverse proxying then there are better, more modern technologies.
Some of us- those who actually write or run applications- benefit from API stability, and (call me old fashioned) ABI stability.
That’s why the “enterprise” distributions are back-porting instead of continuously updating their kernel versions. Because everyone who isn’t just running a kernel for the sake of it wants to actually be doing something else with their computers.
Of course the resources to do that sustaining engineering effort are not trivial, it’s no great surprise some are pulling that work to behind closed doors. It’s just a shame that the options are being reduced just as commercially sponsored ones are disappearing from public access too.
Not to mention developer tools, libraries, operating system updates.
There’s a prevailing attitude (possibly because so much software *is* free at the point of access) that it must cost nothing to provide it.
Which is ironic when application developers are complaining about sharing any of their income with the app store providers.
I would expect to see any “third-party” app stores being obliged to pay royalties to the platform developers/owners, or else the app developers having to agree financial terms with same. Be careful what you wish for, etc.
It acquired its OpenGroup Unix certification in 2007, a mere 6 years after public launch, Mac OS X having little technology in common with Mac OS 9 and earlier.
(though a bit longer than 6 years if you were to include the NeXTStep origins, but I’d argue that would be misleading because a lot of work was done by Apple specifically to be capable of passing the certification. Even then, they never attempted to deny its BSD underpinnings either).
Clever people those IBMers. It's easy to spot in any hex output, and if you ever see "0xdeadbeef" in your pointers then you know you've got something wrong.
(Someone has it that it's a play on being 'dead meat' if you end up with a pointer into unallocated memory. But I hadn't heard that before.)
If we want to spit-ball possible risks, perhaps you aren’t trying to exfiltrate data, but infiltrate the physical location? What if you could flash a QR code that made the camera keep transmitting an old image, or just go off line for a bit, or something else carefully planned.
Don’t even need to have the camera on the Internet to ensure that regular software updates are applied, any of which could introduce new features, because your organisation security policy undoubtedly requires you to keep software up to date. Especially if they fix disclosed vulnerabilities.
I remember when one of my older phones would shutdown with a high percentage of charge left, and of course it turned out the battery was on the way out and could not meet the power demands.
I’m glad they started throttling, as shutting down is far more disruptive than going slow. Though the PMs involved should have thought about the “PR” and had it advise the user to get their battery replaced.
Err, Safari works fine for the user. If the experience was really sub-par Apple wouldn’t be selling us lots of iPhones. Just because it doesn’t implement every latest experimental feature does not make it bad.
If I wanted a choice of dodgy apps I’d buy a different brand of phone ;-)
A lot of dev teams, particularly those who use containerisation in production, will use Docker Desktop as a means to get the run-time Docker tools onto their developers’ machines, to stand up a local copy of their own software for development and debugging. Images for deployment would be built by CI systems (with Docker build, or kaniko, Buildah, etc)
But, as someone else said, it’s a hard task to sell software that is perceived as “free”. Docker Desktop will be a ground-up choice (development teams making their own lives easier) rather than a business-led choice (a technology that improves the bottom line), so if there’s little or no development tools budget - or it has already been allocated to IDEs - then Docker will be SOL.
(I personally wouldn’t begrudge paying for Docker Desktop for Mac if they’d integrate networking on macOS. Having to manually configure and run “tap” is a big annoyance)
Back in the day, we systems programmers built almost every third-party tool ourselves from source. Even the C compiler. But we sure as hell weren’t reading and comprehending all the source, not even checking for common sources of mistakes (printf without format args, popen calls, etc), and you’ve only got to recall Ritchie’s seminal paper Reflections on Trusting Trust to see the elephant in the (GCC) room.
Software is necessarily more complex these days because capabilities are higher and we demand more, and that will almost always involve many more third party dependencies, which in turn may have more. That cat is not going back into the bag, because it’s just not feasible, or wise - trivial string padding routines aside - for a development team to rewrite all those themselves (crypto, maths, graphics, UI, kernel, etc).
The solution isn’t to ditch the “uncontrolled” open source dependencies, either, and go back to commercial (commercial C++ libraries were all the rage in the 90s and early 00s), because we’ve seen with SolarWinds, Kaseya and many others that if you’re a high value target you *will* get attacked and compromised at some point for leverage into other networks. You need to have in place methods to prevent, mitigate or detect it when the time comes.
At the end of the day, it’s the “configuration vs. customisation” debate. It’s the same thing that gets you stuck on an old release, unable to upgrade because you’ve tweaked it up the wazoo and no one who knows how it works is still working for you (or, those that are, know better than to want to get involved).
ServiceNow, with their SaaS workflow, were already having that challenge with customers over 10 years ago, and as far as I know (I’m no longer working in that orbit) they’ve addressed it by being more restrictive in what you can change/how you can change their stuff.
My understanding, reading between the lines and knowing the APIs available, is that they’re both transmitting BLE messages and also registering to listen for them. You might know this as iBeacons.
You can listen for Beacons from your family in the background, the OS APIs make it easy and battery friendly.
You can’t transmit beacons in the background so easily, transmitting also requires more power.
The world of malware shows why, with many billions more of mobile devices, there’s a need to treat things differently to how we historically did so on personal computers.
(On iPhone, I can prevent an app from having Bluetooth access even if it asks for it. Likewise Location. My Android phone stopped getting updates, but even it had some controls that let a user turn features off. If the App doesn’t then function, well that’s down to differing opinions of the app developer and you, the user. Not much you can do about that, if you cannot write your own or pay someone to do so.)
ISTR NatWest’s forays into investment banking played a part in their downfall.
“ in 1997, NatWest Markets, the corporate and investment banking arm formed in 1992, revealed that a £50m loss had been discovered, revised to £90.5m after further investigations.”
Wikipedia also reminded me that they’d tried to do a merger with Legal & General, which went down like a lead balloon, and seems to have been the final straw.
All worked out well for RBS, in the end, eh? ;-).
Was officially 22%, though when it was still being drunk a few years later it’s hard to say. It was very nice, though.
Stuart Howe, then of Sharps, did brew his Turbo Yeast Abomination from Hell, https://brewingreality.blogspot.com/2010/01/3-turbo-yeast-abomination-from-hell.html, I did get to try some but I don’t remember what it’s final gravity was.
A lot of TLS web sites are hosted on shared services these days: think anything on AWS S3, for example.
There’s separate work going on to prevent them being enumeratable (i.e. to prevent the domain names being disclosed via the certificate when you connect to them)
This will lead to some suggesting the answer is to “man in the middle” every TLS connection, I’m sure.
Isn’t PiHole just a DNS resolver that you configure, via DHCP or statically, as your device’s DNS server? It may then make those onward requests, for domains it deems “good”, over DoH but by that point it’s looking up only what it wants to anyway. Essentially it’s doing what some paternalistic ISPs servers are doing, only under your control.
DoH is about your privacy, stopping a middleman from snooping on what domains you are resolving under the guise of “it’s just metadata”) Also, about stopping those paternalistic ISPs from further meddling with your DNS lookups.
Clearly the board exist to oversee the operation of the foundation and are not product managers of every single (or any, unless they happen to be) Apache Project (as you note, there a lot. More, if you include those in incubation).
Projects are managed by Project Management Committees (clever play on words, there), take it up with them - or join them!
I’ve always been curious - maybe I missed previous discussions - but I’ve personally never met anyone whose employer/ organisation was a customer. I have even worked for companies who have “one of everything” and they didn’t use it.
Any readers able to tell us anything about it?
If you have the server private key then you can decrypt the captured TLS sessions (including at a later date, e.g. if you steal that key), *unless* they use a cipher scheme that implements perfect forward secrecy.
Then you can’t.
But you certainly can’t break TLS just by sniffing the packets as an independent observer, unless you can “break” the maths behind DH.
https://security.stackexchange.com/a/42350 has a pretty good explainer
Yup, and I’ve seen comments elsewhere on this debacle to the effect that one should be able to consent to what Facebook was doing (“if they pay me enough”, said someone)
But IMHO there’s no way they can obtain legitimate *informed* consent from an average user. With the installed root cert and a VPN Facebook were in a position to read *everything* between the phone and any other TLS protected service that wasn’t using certificate pinning (and probably break those that were), riding roughshod over security best practices, laws, and user agreements.
Indeed, they may well be getting a less favourable transaction fee now. Unfortunately we’ll end up paying it in “booking fees”.
(In my case it was my Amex card number that got stolen, but it only came to light after the subsequent BA incident. I haven’t flown with BA in years but it seems someone started testing the numbers they had to see which were still working... it’s good to get alerts on card transactions!)
I think it isn’t truly appreciated just how easy it is for an authorised piece of software to upload an object - with an “everyone can read it” ACL - and completely undo any attempts to keep the bucket secure.
(Yes, you could craft a policy that blocked anything with open access from being created, but you couldn’t block everything already there.)
I've never lost out as a result of fraudulent transactions on any credit card and there have been a few over the years (I don't think I've ever had my debit card ripped off: I don't use it anywhere but ATMs.)
It's just the inconvenience of having to get cards replaced, but Amex were quick (reported Saturday, arrived Tuesday) on the last occurrence - which was probably the miscreants testing cards stolen via Ticketmaster but after the BA hack and publicity.
Co-inky-dinkly, my Amex card just got abused last night. At least twice, before I was able to make the call and get it blocked.
Nothing massive, just a couple of online services taking a preauth - possibly an abuser “testing” the numbers. Now I’ve not flown BA for a while: I probably have used that card number with them in the past, though it would be a different expiry and CID.
But there’s a few other orgs that held that card’s details, at least three of which are “big enough” to have been storing numbers themselves instead of a third party system. I hope none of them have been hit, for that would be very messy indeed.