1,314 karma · joined March 1, 2011
Twitter: @jmeller Github: terracatta
When the iPod came out I remember the main competitor was the Creative Nomad Jukebox. It was bulky (it was the around the same size as a Sony discman), the screen was small, and it had like 11 weirdly shaped buttons, and I think had recharable AA batteries (that took like 12 hours to charge). It was awesome to have all those songs on there, but the thing was a chore to use.
The original iPod was Mac only but it was delightful to use, it fit in your pocket, had an innovative scrolling mechanic, and charged through the same wire as it used for data.
Of course marketing and harmony with iTunes helped a ton, but pound for pound the iPod was simply a better product even without those crutches.
Before notarization, when this bit was set, the user would receive a simple warning that the software was downloaded from the internet and they should proceed with caution.
All notarization does is add additional logic to this flow. If the notarization is "stapled" to the executable, then macOS can verify it offline, otherwise macOS will connect to Apple's servers to verify the notarization of an app/binary. This means that by notarizing an existing app, you do not need to re-distribute it.
This quarantine bit behavior is why upgrading to Catalina does not impact previously installed apps (regardless of their notarization status) as they do not have this bit set.
We have been a big part of the Osquery community for a while and we think it's an awesome project that can be used to get an insane level of visibility across your fleet. We also think in the context of rolling this out to end-users, companies need to really consider the privacy implications of the data Osquery is capable of collecting.
To that end, we soft-launched a product in May that helps fast growing tech companies use tools like Osquery to implement something called User Focused Security. User Focused Security involves treating employees like adults and understanding the context in which they work before rolling out a security strategy.
We want to be the best choice for organizations that want to get serious about the security of their laptops but don't want to lock-down devices, violate their user's privacy, or hurt their internal culture with opaque surveillance.
The three values that we use to build our software:
1. User Education over Enforcement
2. Trust through Transparency
3. Quality conclusions over Quantity of data
We use Osquery because it helps us fulfill that second value by giving end-users visibility into what is running on their device.
If your team uses Slack and want to see our approach you should check us out at https://kolide.com
Do you think that is an appropriate level of access to grant?
Parents don’t need to switch to Android, they have tools built into iOS that offer the features they need without essentially giving away the device to a third party company.
I think the prospect of MDM establishing itself as a necessary evil for consumer use-cases is such affront to their thoughts about individual data privacy rights that they would rather trash MDM than risk that possibility.
If you want to get a sense of how Apple thinks parental management of a device and enterprise management of a device in a corporate setting differ, all you need to do is compare the experiences and features. MDM is like a nuke compared to screentime and parental controls.
As a final note Apple refuses to even provide the management server portion of MDM, another clear signal that of their split feelings on the matter.
iPhones contain so much personal data on-device that Apple is absolutely responsible for protecting that data from illegitimate access. Using MDM which is clearly intended for enterprise management is an illegitimate use-case. Period.
The argument that their ability to use MDM APIs in the past and earn revenue due to a gap in Apple's vigilance dictates that they should be able to continue unimpeded is a logical fallacy.
Apple is under no obligation to offer unfettered API access to these companies just because they were filling a market need that Apple didn't want to pursue. You can tell if Apple wasn't under a market demand obligation to offer MDM to enterprises, they would cut that too.
One of the value props of the iPhone and the iOS ecosystem is that Apple exerts this level of control and editorializing on the platform. The result of which is easily seen when comparing the quantity of data mining apps on Android vs iOS.
I'm sure if I was one of these scorned developers, I would feel abused even victimized by Apple. Unfortunately that is a biased perspective. Apple is doing the right thing for consumers and end-users by blocking these apps.
The reporting on this was atrocious and seems to be a result of the recent competitive chatter about sandboxed computing platforms like iOS. Broader discussions around anti-competitive behavior on these platforms are needed, but this wasn't the poster-child.
To me, it seems very likely someone before 2019 laid eyes on these logs and either:
a) Decided not to report it (implies serious security culture issue)
b) Reported it and no action was taken (implies serious security process issue)
c) Didn't even acknowledge it was inappropriate (implies a serious security training failure)
If you've already become complicit towards regularly violating the privacy of your end-users, one can easily understand an employee devaluing the seriousness of clear-text passwords in a log.Are FB employees so regularly exposed to sensitive data that they have become desensitized to the seriousness of clear-text passwords in an internally accessible log?
I think this is a dangerous line of thinking. This crosses the line of being productively critical of a language or a framework into actually attacking people.
By promoting this line of thinking, you increase the tolerance of this kind of attack.
People arrive at their personal choice of language and framework as a function of their environment, their education, their first job, what's popular at the time, and myriad of other factors.
I am sure you have preferences for languages and frameworks, and I'm sure there are other people who don't agree with them. Do you want those people giving you reasoned arguments about why you should change your preferences or, do what you did, make allusions that you are so irredeemably stupid that you physically exhale shoddy code?
Kolide is an early-stage startup with a mission to build the world’s next generation endpoint security and infrastructure analytics platform. At it’s core, Kolide enables you to ask computers important questions, get back immediate answers, and take decisive action. Kolide does all this by leveraging the awesome power of Facebook’s osquery framework and extending it with built-in security and operations expertise. You'll have the opportunity to work on open-source software with the creators of osquery, led by a former FireEye executive.
Our Current Stack:
* Go
* Javascript
* Kubernetes
* C++
Roles we are hiring for: * Site Reliability Engineer
* Software Engineer: Backend, Frontend, and Host
* Security Engineer
Contact us at jobs@kolide.co | More info: https://kolide.com/careersMy assertion that in any capitalism driven society (no matter the quality of education) you will have a non-trival size of the population not capable of fulfilling job demand and achieving minimum viable salary for survival.
At the end of the day we have 3 options for these people:
1) Do nothing. This creates tax burden to combat crime as people get desperate to satisfy basic needs like food and shelter. It also is pretty crappy thing to do to our fellow man.
2) Subsidize them through programs like welfare. Helps but hurts middle class workers disproportionately and doesn't produce labor.
3) Create and enforce a livable minimum wage. Helps in the short-term (until goods/services prices are inflated adjust to this minimum) and produces labor that arguably has some value. Not perfect because it further decentivizes job creation and increases R&D for automation. Also, it is just a quick fix and needs to be constantly raised.
Minimum wage is clearly not a perfect solution but I'm not sure we have a better one yet within the framework of government regulated capitalism.
I'm not sure if this can be resolved until users are educated sufficiently on the long-term adverse effects of link shortening services (link rot, privacy concerns, slow/broken redirects, etc).
For change to happen the demand for direct links (generated explicitly by things like this blog posts, or implicitly by higher bounce rates due to long loading times) will need to be enough to outweigh the benefits to organizations that are building them.
Edit:
Even if there is evidence that shows this, why should _I_ be the one to give up my link shortener service when it will have no significant improvement to the overall problem which involves tens or hundreds of these services?