seletskiy

11 ms·

61.
Show HN: Hierarchical error reporting made right in Go-lang(github.com)
1 points by seletskiy 10y ago|0 comments
62.
Pastejacking prevention using urxvt, tmux and vim(github.com)
3 points by seletskiy 10y ago|0 comments
63.
Show HN: Tests.sh – func/unit testing command line tools and daemons(github.com)
3 points by seletskiy 10y ago|0 comments
64.
by seletskiy 10y ago
Recently, I've wrote simple tool for storing secrets like passwords in public Git repos using AES cypher: https://github.com/seletskiy/carcosa/
65.
Show HN: Tests.sh – func/unit testing command line tools and daemons(github.com)
2 points by seletskiy 10y ago|0 comments
66.
by seletskiy 11y ago
And how it's better, than sed/awk? xo: function shh() { ssh $(cat servers.yml | xo "/. ?($1):\s server:\s+([^:\n]+):?(\d+)?. ?user:\s+([^\n]+). /\$4@\$2 -p \$3?:22/mis") } sed: function s
67.
by seletskiy 11y ago
Beautiful colored unicode output. But why on the Earth it's implemented in bash/awk? It's completely unmaintanable and unfrendly for contributors. Just look, how GitHub syntax colouring gives up on 46 line of prettyping scrip
68.
by seletskiy 11y ago
Thanks for valuable note about README, it's certanly needed to be explained. But, I hope, I describe point about LDAP and stuff in replies to other discussion members comments.
69.
by seletskiy 11y ago
I'll call it oversimplification. It very error-prone and very difficult to automate. Of course, you can always tell your ops engineer to run something like `xargs -n1 -I{} ssh {} echo ... \| chpasswd < hosts.list` manually, but we a
70.
by seletskiy 11y ago
Often, the only way to know what's wrong with server/software is to login through IPMI and see it while it's still alive. Reboot will lost that information. Don't see exactly how enabling root password login at physical&
71.
by seletskiy 11y ago
shadowd is not against SSH keys in any way. It can serve them as well. The main point is always having password access for cruicial services, so any given ops engineer can login from almost everywhere. In real life there can be different si
72.
by seletskiy 11y ago
I guess, you didn't address any single issue I mentioned. I don't see, why it's far more effective, secure and stable to have proposed stack as the single source of truth. Given the example, that we do not have LDAP stack alr
73.
by seletskiy 11y ago
Nope. Attacker can figure out "some" password (e.g. will find collision for specific salt+hash), that will be valid only for the server it already has access too, so it's not the big deal. All other nodes will have different
74.
by seletskiy 11y ago
I prefer well written, well working, well documented and packaged software that solve problems, not tcl scripts or any other shell scripts that is very difficult to maintain. shadowd/shadowc is exactly the tool that generates X differe
75.
by seletskiy 11y ago
It depends. You can have many development servers/nodes, which are infrastructurally "inside" the company and is not accessible from outside. They should be managed somehow, security requirements can be considerably less than
76.
by seletskiy 11y ago
Calling passwd on each host (imagine hundred of them for tens of users) and manually setting same password is not the way to go. The idea is to have same password will be setted up on numerous amount of nodes without storing or transferring
77.
by seletskiy 11y ago
LDAP is a remote login provider, works through PAM-module and is nowhere near "lightweight" as it supposed to be. Also, it stores only one hash for original password, not many. If you do not have cached version of auth info on the
78.
by seletskiy 11y ago
Actually, I feel myself so stupid right now. >_<
79.
Show HN: Zero-configiration systemd containers(github.com)
28 points by seletskiy 11y ago|5 comments
80.
Show HN: Zero-configiration systemd containers(github.com)
2 points by seletskiy 11y ago|0 comments
81.
by seletskiy 11y ago
Looks like I was not clear enough. goimports works perfectly, but only on buffer save event (or by manual trigger). Take an example, start from scratch: package main func main() { fmt| } Cursor is at |, and when I type .,
82.
by seletskiy 11y ago
I'm using vim-go, I just implemented autoimport functionality on top of it.
83.
by seletskiy 11y ago
Yeah, only on save. It's deal breaker for me, I want to see completions immediately, not by entering `fmt.`, saving file, backspacing, re-entering `.`.
84.
by seletskiy 11y ago
It's really nice, but lack specific feature of auto-importing packages while typing. Like, if you type `fmt.` and package is not imported yet, you'll not see any completions. So, I've implemented it a while ago in separate co
85.
by seletskiy 11y ago
Check it out: https://github.com/seletskiy/dotfiles/blob/master/.zsh/alias... Far more easier to press CTRL-T than type `fuck` every time.
86.
Show HN: Finally, just insert text in shell vim with Shift-Insert(github.com)
3 points by seletskiy 12y ago|0 comments
87.
by seletskiy 12y ago
...or use very simple lib like this one [1] to access to deep-nested structs using one call. [1] https://github.com/zazab/zhash
88.
Show HN: Code review in editor for Atlassian Stash(github.com)
4 points by seletskiy 12y ago|0 comments
89.
by seletskiy 12y ago
Not the same, but I'm building tool for using editor (vim, ...) as backend for reviewing pull requests for Stash (git hosting product from Atlassian): https://github.com/seletskiy/ash
90.
by seletskiy 12y ago
Just copying is not enough sometimes. If you want to clone some production images to your dev/test environment you need to change some params in production image to make it work. For example, if you have nginx in production environment

More ›