public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kevin Brandstatter <kjbrandstatter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} open-source: chat, tasks, resources, code
Date: Mon, 17 Dec 2012 18:52:09 -0800	[thread overview]
Message-ID: <50CFDA59.1050908@gmail.com> (raw)
In-Reply-To: <CAN0CFw3=KSw2U08dLq7y64PXrgw-6T_unM=Bks6OPLaYjbOm6A@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/17/2012 06:33 PM, Grant wrote:
>> What ive done on one of my servers is created a git user account
>> that cant login interactively, or with a password. (nologin),
>> whoever needs access gives me their private key and i add it to
>> the authorized_keys for the git account.
>> 
>> This is obvoiusly very basic and you could create users for each 
>> project etc, or use one of the many git server programs that
>> will allow to have more fine grained access control, Just depends
>> on your needs.
>> 
>> For chat, ive used campfire for the chicago marathon, its not
>> much more than a glorified irc system. IRC is perfectly fine if
>> your on a closed network. but i would keep it off the general
>> internet.
> 
> An IRC server shouldn't listen on an internet-facing port?  Are
> there security issues?
> 
> - Grant
> 
> 
>> resource and task management, i think eclipse and some ides have 
>> integrated solutions, outside of that not really sure
>> 
>> - -Kevin
irc servers are notorious for botnets and the like and yes, are often
a prime target for remote exploitation. they can be secured like the
major systems, but it can be a bit more of a challenge

- -Kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBAgAGBQJQz9pZAAoJENfP/Gsfo0VKdjQH/1Dc0qWISZc8xcMFKgBGlTlR
ao8UHcyHIoJapWESVOq/VglGBOXwiW2gWfSeO5LD+td+7hwe+5ZgkIewrPij9Dx5
yXxXDae3Obcd2L5ROZ9AncctM26vpqwBzTyFm+MXuaJfdFXECLaA1aMNptIJF2fr
iLSUntTlOooa7Falv+RCDg0ROXbV9VBckYPb3nKC38gUJvebw71uc/soGC4bzM7l
+cZRx/hXbcvnqXk8mXBl+Ox2t/UJfJuXXh3brK0lg8ov9Adho/3yoyYOPAYYPFAA
JZVy1P7j1JfHBBl72QSOcGbK1NC9+vmaysm4dXQJV9pTL/uRp4va5F1Q0iMIbi8=
=szla
-----END PGP SIGNATURE-----


  reply	other threads:[~2012-12-18  2:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17  7:26 [gentoo-user] {OT} open-source: chat, tasks, resources, code Grant
2012-12-17 16:13 ` Michael Orlitzky
2012-12-17 17:05   ` Michele Beltrame
2012-12-17 23:48     ` Michael Orlitzky
2012-12-18  0:56   ` Grant
2012-12-18  1:06     ` Michael Mol
2012-12-18  2:10       ` Kevin Brandstatter
2012-12-18  2:33         ` Grant
2012-12-18  2:52           ` Kevin Brandstatter [this message]
2012-12-18  1:11     ` Alan McKinnon
2012-12-18  2:04       ` Grant
2012-12-18 11:30         ` Marc Joliet
2012-12-18 11:46           ` Michael Mol
2012-12-18 12:50           ` Alan McKinnon
2012-12-18 14:57             ` Marc Joliet
2012-12-19 20:14               ` Grant
2012-12-19 20:29                 ` Michael Mol
2012-12-20 21:02                   ` Grant
2012-12-20 21:27                     ` Alan McKinnon
2012-12-20 21:28                     ` Michael Mol
2012-12-20 21:32                       ` Grant
2012-12-20 21:42                         ` Michael Mol
2012-12-18  1:12     ` Michael Orlitzky
2012-12-18  1:59       ` Grant
2012-12-18  2:21         ` Michael Orlitzky
2012-12-17 17:08 ` Kevin Brandstatter
2012-12-18  1:02   ` Grant
2012-12-18 11:21 ` Ciprian Dorin Craciun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50CFDA59.1050908@gmail.com \
    --to=kjbrandstatter@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox