frozenice
I recently had to import a CSV with some million rows into MariaDB. Neither HeidiSQL nor DBeaver could do it (tried various settings). IntelliJ worked like a charm.
An Announcement from Gitlab CEO Sid Sijbrandij
July 1 TeamCity Cloud Outage Postmortem
time.Second * time.Second
The type of this is `time.Duration` (or int64 internally), not `time.Second` (which is a const with a value).I agree, though, that this is not quite sound, because it can be misused, as shown above with `time.Sleep(delaySecs * time.Second)`.
In Kotlin you can do `1.seconds + 1.minutes` but not `1.seconds * 1.minutes` (compilation error), which I quite like. Here is a playground link: https://pl.kotl.in/YZLu97AY8
Authentication, not authorization. ;)
That's the first time I hear about RFID/NFC MITM, neat.
Visa card vulnerability can bypass contactless limits
There are only two hard problems in computer science: cache invalidation, naming things and off-by-one errors.
Fake fingerprints can imitate real ones in biometric systems
Troy Hunt is already looking for the data ;) https://twitter.com/troyhunt/status/1038368815778648064
[de] 1.8M cleartext passwords leaked from knuddels.de
Kelsey's tutorial is a bit outdated (Oct 2 2017 with k8s v1.8, v1.11 just got released). Here is a link to the official kubeadm guide for Creating a single master cluster with kubeadm:
https://kubernetes.io/docs/setup/independent/create-cluster-...
It basically is just running
kubeadm init
on a server / VM (after installing docker and kubeadm, of course). Add a pod network add-on (Calico seems to work well, 2 commands to install), remove the mentioned taint and optionally join more worker nodes (also a single kubeadm command). Every step is in the guide, just copy & paste. ;)Note: This is no production-ready cluster (it has a single master), also you should have some basic understanding of k8s, which the OP provides. I also highly recommend to dig around kubernetes.io/docs - good material there.
I started with kubeadm some days before the release of k8s v1.11, which made some stuff I wrote obsolete, oh well... :) I really like the new kubeadm phase stuff, though.
There is also an official guide for Creating Highly Available Clusters with kubeadm (it's updated for v1.11) which I just went through:
https://kubernetes.io/docs/setup/independent/high-availabili...
I opted for the "stacked masters" approach (run HA etcd right on the k8s master nodes), wrote some ansible tasks to automate to boring stuff like copying configs/certs etc., and am currently (re-)exploring add-ons and advanced functionality (helm, network policies, ingress controller, ceph via helm, ...).
Let's see how far I get this time!
Development on Torus at CoreOS Stopped as of Feb 2017
There was this eSettings.exe which let you change some BIOS Settings from Windows, including the password. Of course it first asked for the old password and showed a prompt, denying the request if it was wrong.
I fired up good old OllyDbg and traced the prompt in the ASM code. I changed only one bit IIRC (jne to je, or similar), saved the .exe and tried my luck.
It let me through the prompt and I entered the new password. Amazingly the BIOS gladly accepted it!
I didn't bother to find out what functions it exactly called to set the new password to write a small tool, because I already had one. ;)
I wonder if this still works... If not with an Acer, maybe with some other make?
The lower layers in the modern computing infrastructure are written in languages threatened by exploitation of memory management errors. Recently deployed exploit mitigations such as control-flow integrity (CFI) can prevent traditional return-oriented programming (ROP) exploits but are much less effective against newer techniques such as Counterfeit Object-Oriented Programming (COOP) that execute a chain of C++ virtual methods. Since these methods are valid control-flow targets, COOP attacks are hard to distinguish from benign computations. Code randomization is likewise ineffective against COOP. Until now, however, COOP attacks have been limited to vulnerable C++ applications which makes it unclear whether COOP is as general and portable a threat as ROP. This paper demonstrates the first COOP-style exploit for Objective-C, the predominant programming language on Apple’s OS X and iOS platforms. We also retrofit the Objective-C runtime with the first practical and efficient defense against our novel attack. Our defense is able to protect complex, real-world software such as iTunes without recompilation. Our performance experiments show that the overhead of our defense is low in practice.
Subversive-C: Abusing and Protecting Dynamic Message Dispatch [pdf]
I found SXCluster and posted it here https://news.ycombinator.com/item?id=11812566 - not directly geared towards containers, but very easy to setup (no need for etcd and the like).
I wanted to go with Flocker (although it is a bit complex) seeing it has some nice features, but it only supports rather complex block device backends (https://docs.clusterhq.com/en/latest/flocker-features/storag...) and I'm not on AWS / GCE. I have free space lying around on some servers' disks (not extra devices or partitions, mind you) and there was no easy way to make this space accessible as / to a cluster.
This blew me away! Setup was a breeze, just add an apt repo, install a deb + maybe 6 deps and answer some prompts, done. The docs are easy to read and not cluttered, see http://www.skylable.com/manuals/sx/manualch3.html (use sxsetup --advanced to change the port, if needed).
They have support for mounting a volume from the storage cluster as a normal directory via FUSE (http://www.sxfs.io/#install).
Did I mention it's free and has Users and basic ACLs for volumes?
A basic web GUI is also available (as an alternative to the enterprise version) here: https://github.com/skylable/sxconsole-lite (runs via docker, just answer some prompts)
But wait there's more! Some other goodies include an S3 compatible API (https://www.skylable.com/products/libres3/) and Dropbox like apps (http://www.sxdrive.io/) - which I haven't tested, yet.
Bonus: One founder of Skylable is the author of ClamAV.
So my curent plan is to just create a volume or several, mount them on each docker host via sxfs (FUSE) and bind them into the containers, where needed. I'm curious if anyone has other suggestions on how to make use of spare space on servers for multi-host data volumes.