Comments for Sorressean's blog

Comment on DLLs:A brief overview by Brandon McGinty-Carroll

Brandon McGinty-Carroll — Fri, 13 Jan 2012 00:57:20 +0000

Exelent intro and overview. Concise, simple, well thought out, and well written.

Comment on a few updates. by Doc wright

Doc wright — Sun, 10 Jul 2011 07:17:21 +0000

I am in audio production. If i can help at all when you are ready to create your audio files for your game let me know. Also, How did you contact quentinC? everything I’ve tried bounces back.

Comment on Securing SSH by Charles

Charles — Tue, 05 Jul 2011 17:22:00 +0000

You should consider using 2 Factor authentication with your SSH connections.

http://code.google.com/p/google-authenticator/

I have written a small guide about it on my blog.

Comment on Securing SSH by Chris Brannon

Chris Brannon — Fri, 20 May 2011 15:27:47 +0000

Nice article.

Also, if you wish to require public key authentication, be sure
that ChallengeResponseAuthentication is disabled.
It is sometimes enabled by default.

When I set up a new sshd, I’m also conscientious about testing my config.
E.G., I try logging into the server from an account which does not have
my private key. This assures me that public key authentication is,
in fact, required by the server.

Comment on Linux permissions uncovered by James Scholes

James Scholes — Sun, 15 May 2011 10:11:56 +0000

The chgrp command takes the syntax chgrp group user.

Typo. chgrp group filename is the correct syntax.

Comment on Linux permissions uncovered by Sorressean

Sorressean — Sun, 15 May 2011 04:17:18 +0000

chmod 777 and 666 have their purposes, just sort of depends. sometimes you’ll want 666 (readable and writable by all), or 555 (readable and executable by all) more than 777, though.

Comment on Linux permissions uncovered by Storm

Storm — Sun, 15 May 2011 03:44:53 +0000

This is awesome. I have it bookmarked for a quick reference on permissions. The only thing I would have added is a warning to pretty much never use chmod 777 because it leaves a file wide open to anyone.

Comment on Securing SSH by Kerry Hoath

Kerry Hoath — Sat, 14 May 2011 00:07:10 +0000

2 small things, fail2ban is worth looking at for resisting brute force attacks however it does require iptables on the machine in question. Also the preferred way to copy an ssh key is to use ssh-copy-id but don’t worry too much I’ve been using ssh for 10 years and found out about this command 2 weeks ago.

Comment on Vinux: my thoughts on the project. by Sorressean

Sorressean — Mon, 02 May 2011 12:55:13 +0000

Chris:
If you were serious about this minimalist arch cd, I’d love to help out. Summer starts in about two weeks, if you want any help. I’ll speak to you more on IRC.

Comment on Vinux: my thoughts on the project. by Chris Brannon

Chris Brannon — Mon, 02 May 2011 12:18:57 +0000

If someone has the time and inclination,
why not create a minimalist live CD with gnome, orca, and all that jazz,
but based around ArchLinux, instead of Ubuntu?
Someone could take the current TalkingArch, such as it is, and build
this kind of environment around it.
The ArchLinux build scripts aren’t too hard to understand,
and the build process for TalkingArch is documented.
Start here:
http://the-brannons.com/tarchblog/building-made-simple.html
And continue with
http://the-brannons.com/README.building
So who wants to work with me?

And yes, I’m definitely a fan of the CLI. That’s a topic for another
day. Maybe I should go blog about it on my own blog…