IRC Logs for #crux-devel Sunday, 2017-07-30

*** dlcusa has joined #crux-devel00:16
*** onodera has quit IRC00:21
*** deep-book-gk_ has joined #crux-devel00:41
*** deep-book-gk_ has left #crux-devel ()00:43
*** _________mavric6 has quit IRC02:37
*** _________mavric6 has joined #crux-devel02:38
*** isidore has joined #crux-devel03:12
*** isidore has quit IRC03:59
*** Workster has quit IRC06:59
*** xyhuogsfpvaswxsm has joined #crux-devel06:59
*** Workster has joined #crux-devel06:59
*** nthwyatt has joined #crux-devel11:50
*** darfo has quit IRC11:50
*** onodera has joined #crux-devel12:12
frinnstanyone else have problems with ssh on crux.nu? i've changed the remotes and tried a push but it first timed out13:03
frinnstah, now it went through13:03
frinnstunless its just me i can ask charlie about it13:04
frinnstiirc he did mention that they had some logic on port 22 to deal with brute force13:04
frinnstalso, is this a gitolite feature? commit 6546a12330c9c04eafc0d7eba820d9785d7303b6 (HEAD -> 3.3, origin/3.3)13:07
frinnstno, not a gitolite feature but this i guess: +-rwxr-xr-x     root/root       usr/lib/git-core/git-rebase--helper13:09
jaegerI had thought that the SSH trouble was because of the BB software but maybe it's somewhere else on the network in the DC. With that said, that's the point of the dropbear instance on 222214:12
*** chinarulezzz has quit IRC14:19
frinnstI'll ask charlie about that. sure we can iron it out17:47
teK_I have had troubles with SSH too but not in the last two days19:12
*** chinarulezzz has joined #crux-devel19:13
*** dacuwlxqbrwifxre has joined #crux-devel22:53
*** Workster has quit IRC22:53
*** Workster has joined #crux-devel22:53

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!