4,741 karma · joined June 5, 2013
[ my public key: https://keybase.io/smcleod; my proof: https://keybase.io/smcleod/sigs/MzLBpke-na7sxHWYF1JaGxDaLN1yk8ArqkF87K7DQ_o ]
———
Words are my own or somebody else’s
- http://www.zdnet.com/article/security-flaws-affect-every-int...
* Edit:
From https://meltdownattack.com/
Which systems are affected by Meltdown?
"Desktop, Laptop, and Cloud computers may be affected by Meltdown. More technically, every Intel processor which implements out-of-order execution is potentially affected, which is effectively every processor since 1995 (except Intel Itanium and Intel Atom before 2013). We successfully tested Meltdown on Intel processor generations released as early as 2011. Currently, we have only verified Meltdown on Intel processors. At the moment, it is unclear whether ARM and AMD processors are also affected by Meltdown.
Which systems are affected by Spectre?
Almost every system is affected by Spectre: Desktops, Laptops, Cloud Servers, as well as Smartphones. More specifically, all modern processors capable of keeping many instructions in flight are potentially vulnerable. In particular, we have verified Spectre on Intel, AMD, and ARM processors."
I’m willing to be the guy/gal next door has those broken window alarm strips installed, one part of the strip is loose and when the cars RPM drops as the clutch is let out while in reverse it slightly vibrates the window causing the contact to short (or break) and thus the house alarm goes off.
Good fun :)
> Has there been an update released yet? I wouldn't know, I don't use OS X.
I think you might have misunderstood what I meant when when asking for citation, it's based on the statement you made in relation to citing sources for what something that could be opinion stated as fact.
https://libguides.mit.edu/citing
> Is it a bad way? No!
OK this is where I stop feeding the troll.
Citation needed.
> "It is best for users to know that their system is vulnerable, and how to fix that without waiting for a system update."
Stepping outside the 'tech' social bubble, most general users likely won't create a root account and password from something they see on TV or their local news site or at least not before a patch would have been released.
--
Further to previously provided examples:
https://www.cloudflare.com/disclosure/
https://access.redhat.com/security/team/contact
https://www.xenproject.org/security-policy.html
https://about.gitlab.com/disclosure/
https://help.github.com/articles/responsible-disclosure-of-s...
https://www.kernel.org/doc/html/v4.10/admin-guide/security-b...
https://www.drupal.org/drupal-security-team/general-informat...
https://www.cisco.com/c/en/us/about/security-center/security...
https://www.juniper.net/us/en/security/report-vulnerability/
If it’s not publicly known and is a security risk it is far more effective to directly contact the developers / companies security team so they can immediately work on actually protecting people by developing a patch. If they don’t respond quickly (subjective, I’d call it within 12 hours) or fail to issue a fix in a timely manor (subjective, I’d say 24 hours) then yes - go public, start by logging a bug report and link to that bug report or if you can’t - the bug number / reference.
2. Add a complex root passphrase and clean this up after the fix is released.
3. Reflect on how irresponsibly this serious security bug was ‘reported’, he didn’t just potentially miss out on $200,000, he put an enormous number of people at risk of local intrusions when instead if it was properly reported there’s a good chance Apple would have released a bug fix for this quicker thus reducing the potential impact and spread of misinformation.
https://en.m.wikipedia.org/wiki/Responsible_disclosure
https://support.apple.com/en-au/HT201220 (See ‘Security and privacy researchers’)
My only are the applications slow and buggy (unless I’m guessing you’re running Windows?) the file format is very hard to work with / from if you want to do anything with it outside the vendors application, data quickly becomes stale and it’s not easy to populate automatically using standard tooling let alone share the information generated there from in an accessible, digestible format.
I'm not having a go but I did also find it genuinely funny.
Anyway, fantastic work all - a fantastic distro that I believe in many ways sets an example for others (especially security wise). I look forward to all the hard work making its way into RHEL & CentOS in time to come.
Not only are 99% of phone calls a waste of time, you’re inefficient with no written log of the conversation (not even for security but also to improve workflow and prioritisation / memory recall), furthermore the impact of the context shifting from what I’m currently working on / deep in thought over to a jarring phone conversation at the time that suits the caller - is incredibly disruptive.
Out of interest - What does IBM’s brand mean to you? (Serious question)
By that, I think I mean - what does IBM make you think of and what emotions does it instil in you when considering the company and brand?
--
Infoxchange is a not-for-profit social enterprise that has delivered technology for social justice for over 25 years. With over 100 staff across Australia and New Zealand we tackle we tackle the biggest social challenges through the smart and creative use of technology.
We work with community, government and corporate partners to solve family violence, homelessness, mental health and issues facing ageing, disabled and Indigenous communities.
--
This role is responsible for process and people management of that team, as well as performing development activities on those products / codebases.
Delivering functionality enhancements, technical maintenance, and resolving defects on Infoxchange's Directory, Referral, Open Data, and Website products / infrastructure.
- Primary language used across modern products is Python.
- Open source tooling pretty much across the broad and very much promote public contributions and engagement.
- Highly automated environment with strong CI/CD capabilities.
- Lots of interesting tech across our applications and hosting (ElasticSearch / ELK Stack, GitLab, Puppet, Docker, Kubernetes, PostgreSQL and the list goes on...)
- We give and actively participate in lots of talks / meetups.
- Absolutely minimal bureaucracy and I'd say that everyone in the organisation truly cares about what we deliver and our impact.
- Ops team (my team!) works very closely with developers and there's a very social atmosphere.
--
Infoxchange | Senior Ops/Systems Engineer | Melbourne Australia | ONSITE | Full Time
We'll also shortly be seeking an experienced Ops Engineer to join the team I lead, so if you know of us via the work we do or the technologies we're involve or contribute to it's probably worth getting in contact if you're more in the ops / devops (with Systems / Ops focus) space.
--
Contact us here: https://www.infoxchange.org/au/contact or email recruitment (at) infoxchange.org