They obviously can't address traffic directly to 192.168.1.0/24 over the Internet as that's a bogon address and the Internet routers will either reject it out of hand, or not know where to send it.
305 karma · joined May 4, 2019
They obviously can't address traffic directly to 192.168.1.0/24 over the Internet as that's a bogon address and the Internet routers will either reject it out of hand, or not know where to send it.
Strong top-down direction can work (e.g. Steve Jobs at Apple) but it can also cause ossification (e.g. Blackberry) where a company won't sacrifice an existing product to move forward.
Windows server has obviously lost the app server market, for a majority of companies. MS has adapted to that new reality by supporting Linux servers.
I'd say that is to their credit. Look at other companies who have been slower to adapt to the new cloud world (e.g. Oracle) and you can see the costs to their long term viability.
They're there to make money, simple as that (whether they should be or not, is a whole other discussion).
What tends to get in the way is internal politics and hubris, where a company gets ossified and scared of change.
There's plenty of examples of this (Nokia, Blackberry, Novell etc etc). A bold company will be willing to change even at the apparent cost of one of their own products.
MS have done a pretty effective job, under Satya Nadella, of realising that clinging to the past isn't effective and that they need to be willing to move with the times.
The argument, that I felt the article made, that this is some EEE strategy is (IMO) misplaced. I think MS has no intention of trying to extinguish Linux (if such a thing was even possible), they're adapting to the new reality.
The key to a stablecoin however, is trust. Users have to trust that their holdings are actually backed by real fiat currency as that's the promise of the stablecoin.
That trust can typically be bolstered by things like 3rd party audits, which is something Tether promised for many years and did not deliver.
With Tether the problems are that they have avoided scrutiny and audit, made statements on their website that subsequently turned out to be false and have a somewhat murky corporate structure. None of these, should , engender trust.
If you're using an unpatched version, anyone who can POST YAML to the Kubernetes API server can chew a fairly large amount of CPU/RAM. How badly this effects you, depends on a couple of factors.
1. Is your cluster exposed to the Internet? There's ~240,000 API servers on the Internet, so this isn't that uncommon.
2. Do you have `--anonymous-auth=true` on the API server? Again not that uncommon a config. If you're using a managed distribution, ask your provider...
3. Do unauthenticated users have access to an endpoint that allows for YAML to be posted? This is more likely in clusters at <= v1.13, but is possible theoretically at any version.
The underlying issue is in the Go YAML library, and has now been patched (if you're using it to process untrusted YAML, do upgrade to the latest version :) )
Interestingly the underlying issue is in the YAML spec, which doesn't mandate a limit on entity expansion...
It's not just Docker hub, there's services like the various Programming language package repos (npm, rubygems etc) and the Linux distro package repos.
I would have had Github in that category, but now it's owned by MS, presumably they don't have many of that kind of funding problems...
Security vulnerabilities in Web applications have been a major cause of big losses at a large number of these companies.
Despite that, the most authoritative, best funded, Web application security group is OWASP. A group with a full-time staff of < 10, and an annual budget of well under $10M.
It's interesting to me anyway, that the wider IT industry doesn't see value in trying to establish security practices and tooling which could be used to reduce some of these losses. Even if they don't like OWASP itself for any reason, that they don't look to establish something else to achieve the same goal.
One of the benefits is that it's open source, so you're free to contribute to improve it.
However it's generally the most used "standard" for web application security and some regulations will use OWASP projects as references for what things should be considered for security
I'd agree with the article that it gets misused (a lot) as some kind of checklist that, if you apply, you can have a "secure" application.
Ironically OWASP has several other great projects that are designed to provide methodologies to improve application security like ASVS https://www.owasp.org/index.php/Category:OWASP_Application_S... and at a more organizational level, OWASP SAMM https://owaspsamm.org/ .
Where I do feel some frustration with this article is where , to me, it feels like it's suggesting that "shift left security" (the idea that security activities should take place earlier in the development lifecycle) is any any way a new concept.
The idea of doing more application security work early in the development process has been around at least 20 years and probably more.
Instead of having new buzzwords for it, to try and make it more attractive, I'd be much more interested in a study of why after all this time it's still not uncommon to see a first security touchpoint for a project be a penetration test done 2 weeks before go-live.
To me, both are a manifestation of the idea that these two Operating Systems are moving in the direction of being safer for "ordinary users" at the expense of annoying more technical users who want to do less common things which can be dangerous if you're not careful (like running software as root)
Given that "ordinary users" outnumber technical ones, I guess that makes commercial sense...
As a result of that, I prefer working with Linux where possible as (generally) it lets you do what you want, even if that's really dumb/dangerous. If I say `kill -9 x` or I sudo to root and do `rm -rf .` by accident it's on me.
If you're using VM isolation, you need licenses for the containerized applications.
closest competitor for the Model X at the moment appears to be the Jaguar I-Pace.
For the model three there's things like the Hyundai Kona and Renault Zoe which are becoming competitive.
I don't think it's there yet, but if I was an investor looking at a 2-3 year timeline, you've got to expect increased competition as there's various models coming along from various companies. Not all of them will be successful, but it's a fair likeliness that some will be.
Tesla is likely coming to the end of the period where they have a relatively unique portfolio of products. We're starting to see the traditional car makers come up with competitive vehicles.
Whilst Tesla may ride this out fine, it's likely to have an impact on things like margins, going forward.
As long as they're still growing they can blame any losses on the costs of expansion. The hard part is becoming profitable once that growth period is over.
My feeling is that Uber, Lyft and WeWork will really struggle to turn big profits, there's just not enough differentiator to allow them to charge higher prices than other market participants.
with Uber/Lyft the endgame appears to have been self-driving vehicles, but it seems those are a long way off mass market adoption, so it's not likely they can sustain themselves while waiting for that to occur.
I'm not sure what WeWork thought the long term deal was...
The Leave camp, during the campaign, were very strong on the idea that leaving would have economic benefits, not penalties.
When combined with the UK press use of the EU as a scapegoat for many unpopular decisions over the last 40 years, it's not surprising to see the outcome we did.
Reality will only sink in, once we've left and the outcome becomes apparent. I really wish that weren't the case and that people would look at the people pushing brexit to see they are not likely to act in the interests of the majority of the population, but I don't think that's what's happened.
EDIT: to provide one example look at https://en.wikipedia.org/wiki/Results_of_the_2016_United_Kin... The North east of England voted Leave in almost every area...
However since then it has been treated as an article of the faith by both the major political parties in the United Kingdom that "brexit means brexit" (and a wide variety of other fairly meaningless slogans)
Now, reversing course would be seen by a large percentage of the population as a betrayal and would quite likely lead to a hard right victory in the next general election (although the vagaries of FPTP could make outcome rather random)
Looking at things like the "britain elects" twitter account which follows various polls, you can see the effect of various outcomes on likely voting https://twitter.com/britainelects/status/1176103416990437377... compared to https://twitter.com/britainelects/status/1176087917149728768... for example.
I'd prefer remain at this point, as it's obvious the British political establishment has made a total mess of this process, and will continue to do so. Also as the economic consequences of Brexit become clearer, it's obviously not in the countries interest to do it.
However, I have a strong feeling that remaining now will give endless fuel to hard right parties and their stories of how great Britain would be if it could only break free of the EU.
They will get a lot of support from people who feel betrayed by "the establishment", and they can continue their narrative without actually having to prove anything.
Whilst I can see that there's no such thing as a "clean break" brexit, I think from a political perspective, the consequences of carrying on with this deadlock will be worse in the long term.
My understanding of the Labour position is that they would negotiate a deal with the EU (likely including a custom's union) and then hold a second referendum, in which the government would stay neutral.
The government's originally stated aim of the prorogation, was that it was a standard mechanism prior to a queen's speech.
The court has taken the opinion that the real aim of this prorogation was instead to restrict parliamentary debate of the Brexit process and that this is unlawful.
Looking at historic prorogation lengths (https://researchbriefings.parliament.uk/ResearchBriefing/Sum...) we can see that "Between 1930 and 2017, the mean average was about 5 calendar days, a median average of about 4 calendar days.", so it's clear that this prorogation was considerably longer than usual.
Your suggestion then that there's nothing out of the ordinary, seems unlikely to hold and indeed the government's own lawyers didn't even try that line of argument during the case, as far as I'm aware.
To quote https://www.bbc.co.uk/news/uk-politics-49722087
'Lord Keen said previous prorogations of Parliament - including in 1930 and 1948 - had "clearly been employed" when governments wanted to "pursue a particular political objective", adding: "They are entitled to do so."'
so the government was arguing a) that the matter was not one for the courts and b) that even if it was, the government was entitled to use prorogation for political ends.
I'm actually mildly surprised that b) didn't hold. allowing a) would have set a very dangerous precedent.
For one example https://www.payscale.com/research/UK/Job=Software_Developer/...
However I'd suggest that many organizations are not that sophisticated and that many many organizations take CVSS score base scores as objective measures of vulnerability, and that that is dangerous.
Also the point about things like "difficulty to exploit", well that's often subjective and there's no way the analyst assigning the score has a good picture of the real-world likelihood in every case, so the idea that they can assign a universal number to that is incorrect.
If an organization wants to use CVSS internally and assign their scores for their environment, with a consistent set of scoring criteria, that could work (although I'd argue high/medium/low would work just as well)
Also even on the Internet, Shodan has about 5.2Milllion hosts with the Telnet port exposed...