You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!
If you have any problems with the registration process or your account login, please contact contact us.
Geek ChatAsk computer questions or just engage in general geek talk on here
This is the reason it's a good idea to have a typeable root password:
Quote:
<alpha>hmaugans@~$ su
Password:
Sorry
<alpha>hmaugans@~$ su
Password:
Sorry
<alpha>hmaugans@~$ su
Password:
Sorry
<alpha>hmaugans@~$ su
Password:
Sorry
<alpha>hmaugans@~$ su
Password:
Sorry
<alpha>hmaugans@~$ su
Password:
Sorry
<alpha>hmaugans@~$ su
Password:
Sorry
<alpha>hmaugans@~$ su
Password:
Sorry
<alpha>hmaugans@~$ su
Password:
Sorry
<alpha>hmaugans@~$ su
Password:
Sorry
<alpha>hmaugans@~$ su
Password:
<alpha>root@/home/hmaugans#
Sorry, I just glanced back up at my session, and laughed at myself. Had to post it for the geeks.
I personally like certificate based authentication, especially with all of the passwords I have to keep track of. I have already converted much of the web based apps to certificate authentication. very easy to do with apache and IIS.
I personally like certificate based authentication, especially with all of the passwords I have to keep track of. I have already converted much of the web based apps to certificate authentication. very easy to do with apache and IIS.
I used to have that setup, but now I'm logging in from so many different places it's useless.
that's where remote dektop comes in, I hit one central place from all others and can connect from there. That way I only have one vulnerable spot and I can work from there and if need be cut it remotely if it were to fall.
Here's what I did to configure both htaccess and an ssl cert now this is for vqadmin for qmail and the names have been changed to protect the guilty. In IIS you require a client cert and map it to a user. Then you can use user rights to allow/restrict access.
[CODE]<VirtualHost 192.168.1.100:443>
SSLEngine on
SSLCACertificateFile /usr/local/apache/conf/CA.crt
SSLCertificateFile /usr/local/apache/conf/server.crt
SSLCertificateKeyFile /usr/local/apache/conf/server.key
SSLOptions +FakeBasicAuth +StdEnvVars
ServerAdmin admin@domain.com
DocumentRoot /usr/local/apache/cgi-bin/vqadmin
ServerName server.domain.com
CustomLog logs/vqadmin combined
<Directory "/usr/local/apache/cgi-bin/vqadmin">
deny from all
Options ExecCGI
#AllowOverride AuthConfig
AllowOverride All
Order deny,allow
</Directory>
</VirtualHost>[/CODE]
I know I am smart enough to understand all of this. I just have not learned any of it. I am the geek forum lose
I wasn't born knowing this either. I've been messing with computers since the early 80's. It takes time and effort to get as good as some of the more seasoned proffesionals here. Keep working at it and you'll get it.
I actually just picked up 2 books on VOIP today. I realized I know NOTHING about it (very different from computers), so I'm diving in to learn it. Not for any purpose, but just to familiarize myself with it.
I actually just picked up 2 books on VOIP today. I realized I know NOTHING about it (very different from computers), so I'm diving in to learn it. Not for any purpose, but just to familiarize myself with it.
start playing with asterisk www.asterisk.org. it's a voip pbx, just by playing you'll get good experience with it. I built a voip offering for another company a few years back and asterisk helped.