Overall I'll hire the sysadmin who knows the most init systems still found in common linux and unix systems and is the most ready to adapt to whichever trend wins domination. Evolve or die.
641 karma · joined March 5, 2014
Overall I'll hire the sysadmin who knows the most init systems still found in common linux and unix systems and is the most ready to adapt to whichever trend wins domination. Evolve or die.
Months go by, and I start getting mail (physical and email) from "Global Capacity" telling me that my account for DSL service is overdue and my service will be suspended if I don't pay. At first I ignored it thinking it must me a scam because I never heard of the company.
I get 2 more in the following months, the ammount they say I owe them still increasing.
I call Century Link, why I've had service from for months at this point, to confirm my bill is paid in full. It was and my service was not at risk.
Finally I break down and contact them. They explain to me that they purchased MegaPath. So I go to MegaPath's website, which is still online[1]. There's nothing about being purchased to this day. After searching around I find they did indeed purchase Megapath[2] -- AFTER my service went down and I canceled my account!
Global Capacity are still threatening to cancel my service -- which I haven't had in about a year now. Every bill increases according to their monthly service fee. They also refuse to negotiate or admit that I canceled my service prior to their purchase of MegaPath. I don't know what to do at this point.
I have a feeling that Megapath was failing horribly and Global Capacity received unmaintained information from them. Either that or Global Capacity is a fradulent organization. Haven't decided which yet, but it may be a little of both.
[1] - http://www.megapath.com/ [2] - http://info.globalcapacity.com/global-capacity-acquires-mega...
When you want to make idealogcal changes to an existing codebase that does not mesh with the idealologies of the maintainer(s), forking is a great way to make your changes happen. Time will tell if your ideas were good ones. That and how well your maintain and promote your fork. :-)
In the case of OpenSSL vs LibreSSL, it appears the OpenBSD team made a great call and they are making it work really well. As for if anyone else agrees and adopts it, only time will tell.
While attending a security conference in Vancouver earlier this year, someone commented that they thought the OpenBSD team was childish for forking LibreSSL, and several people chimed in with agreement.
Of course this is all hear-say for you, and your experiences may vary. I've met more than a handful of people who did not like the fork. There are lots of people in the world, and they all have different opinions.
No matter how you feel about the forking or the openbsd team, there is something to be learned here. There are times when forking, deleting old code, and major clean-ups can be very useful strategies. Sunk cost bias can be an enemy of progress.
[1] - https://en.wikipedia.org/wiki/LibreSSL#Security_and_vulnerab...
How long until the money gets good enough for people to start introducing obfuscated vulnerabilities into code in order to further profit from it at a later time? With increasing financial incentive and an open market it might be an increasing risk with opportunistic or disgruntled developers.
Many organizations have yet to adopt devops and templated system deployment methodologies, so it's a legit concern.
<script ... integrity="sha384-...">
How will the browser confirm that the source HTML requesting script isn't modified by the CDN?Well known CDN services, such as CloudFlare, are known for modifying the HTML -- This is not uncommon.
If that is the case, why do so many people insist on comparing a framework, such as rails to node.js? Wouldn't the more relvant comparison be node.js vs ruby, or rails vs meteor.
So many people make such comparisons I feel like I'm the one who is crazy. Of course, I probably am, but that may have nothing to do with rails and node.js comparisons. :-)
SNI and SubjectAltName [https://en.wikipedia.org/wiki/SubjectAltName] mixed with the simplicity of issuing a new certificate using LetsEncrypt [https://letsencrypt.org/howitworks/] all but eliminate the need for wildcards.
When it comes to websites that try to force their app upon you when visiting their mobile website, my experience has almost always bee n the application is as bad as, if not worse than, the website's functionality. This gets to my point that if your developers are not capable of building a decent mobile friendly website then they are probably not any better at building an app.
Also I hinted at the fact that in many cases these apps appear to be designed to track users and invade users privacy. Why else do so many need access to contact lists and more when their functionality doesn't remotely require it.
If your developers are not capable of making your website mobible friendly in 2015, any app they develop is likely worse. This is especially true when your app demands access to everything on my phone even though it doesn't need any of it to function.
I'm still patiently waiting for the ability to push compressed disk images via API so I don't have to boot finix to do it. :-)
Even though the author clearly states he uses Docker?
How many times do you go to some technical project page and have no idea what the project actually does? Sometimes you get a vague description, sometimes you get a list of features, or worse you get a changelog for the front page.
If you want people who don't know anything about your tool to use it, first make sure they know what it is, then give them a reason to use it. Ask yourself: "What is X? Why would I use X?" If you can't answer that easily on your project's page, then people who have no idea what your project is may never know.
A little bit of both, honestly.
> It's very much the on-trend "what's the matter with kids these days" issue, carrying on the age-old tradition of condemning bare ankles, short skirts, dirty dancing, pre-marital cohabitation, etc.
Great point. Agreed.
B) See A. You say this like it's a bad thing.
C) The fact that this is true doesn't make it good or bad. One person's nightmare, is another's acceptable risk, is another's pleasure.
D) See C. As a side note: If the NSA spends countless dollars cataloging private citizens sexual interests rather than protecting United States security, then there are much much larger issues to worry about. (And frankly, there probably are)
Edited to fix typos and spelling issues.
(Edit: Assuming all parties involved are consenting adults.)
Also, using nightly images, not the vendor supplied ones.
Not sure how much of a difference that is, but it works for me. :-)
Of course these devices are Nexus 4,5,9 as well as OPO, so might be better supported.
This was my first question too. I checked the android app, and there was no obvious configuration option for a different server.
It's open source, so at least in theory it's possible to modify it to your needs.
Also side note: Was a little disappointed to not see this on f-droid's marketplace since it is open source and hosted on github. Need to get that changed. :-)
"Error 403
We're sorry, but we could not fulfill your request for /blog/machines-learn-to-play-tabla/ on this server.
You do not have permission to access this server. Before trying again, run anti-virus and anti-spyware software and remove any viruses and spyware from your computer.
Project Honey Pot listing for 192.42.116.16"
Not very search engine friendly.
Many of the vulnerabilities fixed are discovered by Mozilla's security team as well as community members, so while there may have been a vulnerability in the browser and it was fixed, it does not mean the vulnerability was known or used maliciously previous to being disclosed.
This is why you cannot judge the security of a product based upon the number of CVE's published. If the vendor in question has an open security program they will publicly disclose all security vulnerabilities they discovered internally. This is a common practice will most (all?) of the major browser vendors.
For example, look at the history of Google Chrome CVE's. You will notice huge spikes in the number of vulnerabilities. A little research, and you will find that was when the Chrome Security team started heavily fuzzing their code and fixing vulnerabilities before most of them were discovered by outside parties.
What you have to worry more about is vendors who don't publicly disclose security vulnerability information, so the only CVE's you see are the ones that independent parties published.