今現在 java json ライブラリを含めないで 少なくとも 6つの scala向け json ライブラリがあります。
file_to_disk = './tmp/large_disk.vdi' | |
Vagrant::Config.run do |config| | |
config.vm.box = 'base' | |
config.vm.customize ['createhd', '--filename', file_to_disk, '--size', 500 * 1024] | |
config.vm.customize ['storageattach', :id, '--storagectl', 'SATA Controller', '--port', 1, '--device', 0, '--type', 'hdd', '--medium', file_to_disk] | |
end |
GitHub RCE by Environment variable injection Bug Bounty writeup | |
Disclaimer: I'll keep this really short but I hope you'll get the key points. | |
GitHub blogged a while ago about some internal tool called gerve: | |
https://github.com/blog/530-how-we-made-github-fast | |
Upon git+sshing to github.com gerve basically looks up your permission | |
on the repo you want to interact with. Then it bounces you further in | |
another forced SSH session to the back end where the repo actually is. |
This Gist summarizes all malware collected in my Kippo SSH Honeypot from June 2013 to present.
Last updated: March 1, 2016
↓ ↓ ↓ Scroll down for the list ↓ ↓ ↓
I was tired of Chrome eating all my laptop resources so I decided to put some limit to it with cgroup.
As I was using Ubuntu 12.04 with support for cgroup, I installed the package cgroup-bin
and add the following group to the file /etc/cgconfig.conf
:
group browsers {
cpu {
# Set the relative share of CPU resources equal to 25%
cpu.shares = "256";
}
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
As I've discovered, managing LXC containers is fairly straightforward, but when building out a system for provisioning out user maintained instances of NodeBB, it was imperative that unprivileged LXC containers were used, so that in the event of shell breakout from NodeBB followed by privilege escalation of the saas
user, the root
user in the LXC container would only be an unprivileged user on the host machine.
During the course of development, I ran into numerous blockers when it came to managing LXC containers in unexpected circumstances. Namely:
- Using LXC in a subshell is not directly supported. This usually happens under one of the following two circumstances:
- After switching users via
su
or executinglxc-*
commands as another user viasudo
- Executing
lxc-*
commands via a program, application, or script. In my case, a Node.js application.
- After switching users via
これは Aizu Advent Calendar 2016 の 9日目の記事(遅刻)です.
http://www.adventar.org/calendars/1530
8日目: オフィスにいる人間をSlackに通知するやつ作った - 人権真骨頂
10日目: @mic_psm
. | |
.. | |
........ | |
@ | |
* | |
*.* | |
*.*.* | |
🎠|