Q20: Are Social Security numbers reused after a person dies?
A: No. We do not reassign a Social Security number (SSN) after the number holder's death. Even though we have issued over 415 million SSNs so far, and we assign about 5 and one-half million new numbers a year, the current numbering system will provide us with enough new numbers for several generations into the future with no changes in the numbering system.
The article covered some math that had been performed to determine the true, actual weight of the data that makes up the Internet. Starting with the weight of a single electron (2 x 10^-30 pound), the author broke down the number of electrons required to charge a single capacitor (the charge equaling a âoe1â in binary) in a computerâ(TM)s memory (40,000), assuming a roughly 50 â" 50 split on 1â(TM)s and 0â(TM)s in a typical 50 kilobyte e-mail. The resulting sum can then be used to determine an electron count per message (8 billion), landing us at a weight for a single e-mail of two ten-thousandths of a quadrillionth of an ounce. Now extrapolate that math across the whole of all Internet traffic; all the e-mail, Web pages, music, videos, instant messages and everything else we all contribute to the Internet. Data-wise you arrive at a mind-blowing 40 Petabyte number. However, that 40 Petabytes only equates to a weight of 1.3 x 10^-8 pound. Thatâ(TM)s right ⦠in real-world terms, all that data equals the weight of the smallest possible grain of sand, one measuring only two-thousandths of an inch across.
The unintended consequence of this is that every user on a system is going to get a fixed ipv6 ip and ipv4 traffic would be gradually phased out. Why bother with the administrative burden of issuing an IP address via dhcp and tracking it, when, you could have an ipv6 theoretically assigned to a customer for the life of a device.
You _ARE_ kidding, right?
Maybe you should check out some information about ipv6 before you make more of a fool of yourself.
^Rstring # recall the last command with string in it
This can then be used again and again, ^R^R, to go back through each of those commands
This allows you to jump back 1, 2, 3, 4... or however many commands in history that include any specific string.
Pass up the command by hitting ^R too many times? ^S to the rescue! ^S then goes forward in your match history
Do not use ^S outside of ^R though, or it will freeze your terminals output(commands still run even though you do not get any output until the following is done) for which you will need to ^Q to unfreeze.
As for other history tricks that you did not get in to... All great!
My (obsd)firewall/proxy/smb is running strong on my 25DX. Of course I'd never add a software raid on that, but also would not ever run a software raid for any reason.
If you can not figure out vi, emacs, or any other cli text editor then why should we trust your programming?
Understanding the BASICS should be required.
Earlier someone compaired an IDE to a spell checker. An IDE does much more and is a grammer checker as well.
Do we teach english classes with grammer checkers? (substitute your own language if not english) no.
Do we teach spelling with spell checkers? I sure as hell hope not.
Then why should we teach programming with an IDE?
Hell, IDE's don't even pass lint most of the time. What does that show? And if you don't know what lint is then put away your IDE for a month(outside of work) and go back to the basics. Learn on your own and stop being lazy.
An opensource frontend (cluster if required) that acts as a gateway to your exchange backend.
This is exactly what my company does and it works very well. I have, infact, never recieved a single piece of spam. It can be configured to touch base with the exchange backend to insure a real account/group is on the recieving end and 550 anything else.
Do people actually do that? If you want a root shell it's sudo -s. But that is NOT the purpose of sudo. You want accountability on your server(s).
And as pointed out by another already, sudo !! or sudo !-2, sudo !-3, sudo !command... Understanding your environment should be one of the first things you learn.
"/var/named/chroot/var/zones/master/d/domain.tld" [New File] user/server:/path$ ls -l/var/named/chroot/var/zones/master/d/domain.tld ls:/var/named/chroot/var/zones/master/d/domain.tld: Permission denied user/server:/path$ sudo !! sudo ls -l/var/named/chroot/var/zones/master/d/domain.tld -rw-r----- 1 named wheel 7185 Aug 6 2005/var/named/chroot/var/zones/master/d/domain.tld user/server:/path$ ^.^2. sudo ls -l/var/named/chroot/var/zones/master/d/domain2.tld -rw-r----- 1 named wheel 1121 Aug 6 2005/var/named/chroot/var/zones/master/d/domain2.tld user/server:/path$ sudo -s root/server:/path# id -p login user uid root groups wheel kmem sys tty operator staff guest root/server:/path# ^D exit user/server:/path$ tail -n3/var/log/secure tail:/var/log/secure: Permission denied user/server:/path$ sudo !! sudo tail -n3/var/log/secure Apr 15 22:10:54 server sudo: user : TTY=ttyp1 ; PWD=/path ; USER=root ; COMMAND=ls -l/var/named/chroot/var/zones/master/d/domain.tld Apr 15 22:10:55 server sudo: user : TTY=ttyp1 ; PWD=/path ; USER=root ; COMMAND=ls -l/var/named/chroot/var/zones/master/d/domain2.tld Apr 15 22:10:57 server sudo: user : TTY=ttyp1 ; PWD=/path ; USER=root ; COMMAND=/usr/local/bin/bash
That's right, we don't have our user associated with our commands when in a root shell via sudo. There are patches and shells that will log this information, but they should not be needed. Correctly using the tools are as important as the tools themselves.
You will ALWAYS want to have individual logins for every administrator and TEACH your admin's howto use sudo correctly if they do not know already.
As for the original question: nobody should EVER login as root, EVER, PERIOD.
1) Cygwin
2) Dedicated Shell Server
Within this environment you will use fanout from Bill Stearns
A) If the remote systems are not set to ``UseLogin yes'' in sshd_config then the custom environment can be used with environment='whatever=whatever' in the remote ~/.ssh/authorized_keys. This, of course, would also require a key which may not be possible as well as ``PermitUserEnvironment yes'' set in sshd_config.
B) The env channel from the ssh client can set the environment on the remote system. This also will not work if ``PermitUserEnvironment no'' is set in sshd_config.
C) If ``PermitUserEnvironment yes'' is set then ~/.ssh/environment will also be evaluated upon login. This would not be advised as it appears as though multiple users aside from the admin's would be using the account(s).
Remember, A and B rely on C to work.
You will recieve the following if it is not setup correctly: Server refused to set environment variables
Anyways, fanout is the method of choice for issuing commands across multiple servers at the same time while providing the output of those commands to the controling terminal. Just setup a few variables and include them in the remote command(s).
Slashdot Mirror
Q20: Are Social Security numbers reused after a person dies?
A: No. We do not reassign a Social Security number (SSN) after the number holder's death. Even though we have issued over 415 million SSNs so far, and we assign about 5 and one-half million new numbers a year, the current numbering system will provide us with enough new numbers for several generations into the future with no changes in the numbering system.
http://blog.theplanet.com/2007/05/24/the-data-center-alive-and-well/
...
The article covered some math that had been performed to determine the true, actual weight of the data that makes up the Internet. Starting with the weight of a single electron (2 x 10^-30 pound), the author broke down the number of electrons required to charge a single capacitor (the charge equaling a âoe1â in binary) in a computerâ(TM)s memory (40,000), assuming a roughly 50 â" 50 split on 1â(TM)s and 0â(TM)s in a typical 50 kilobyte e-mail. The resulting sum can then be used to determine an electron count per message (8 billion), landing us at a weight for a single e-mail of two ten-thousandths of a quadrillionth of an ounce. Now extrapolate that math across the whole of all Internet traffic; all the e-mail, Web pages, music, videos, instant messages and everything else we all contribute to the Internet. Data-wise you arrive at a mind-blowing 40 Petabyte number. However, that 40 Petabytes only equates to a weight of 1.3 x 10^-8 pound. Thatâ(TM)s right ⦠in real-world terms, all that data equals the weight of the smallest possible grain of sand, one measuring only two-thousandths of an inch across.
The unintended consequence of this is that every user on a system is going to get a fixed ipv6 ip and ipv4 traffic would be gradually phased out. Why bother with the administrative burden of issuing an IP address via dhcp and tracking it, when, you could have an ipv6 theoretically assigned to a customer for the life of a device.
You _ARE_ kidding, right?
Maybe you should check out some information about ipv6 before you make more of a fool of yourself.
There is quite a bit of confusion, and it appears that people like you are the ones that are spreading it. How about just a little ipv6 delivery model to end customers?
^Rstring # recall the last command with string in it
This can then be used again and again, ^R^R , to go back through each of those commands
This allows you to jump back 1, 2, 3, 4... or however many commands in history that include any specific string.
Pass up the command by hitting ^R too many times?
^S to the rescue! ^S then goes forward in your match history
Do not use ^S outside of ^R though, or it will freeze your terminals output(commands still run even though you do not get any output until the following is done) for which you will need to ^Q to unfreeze.
As for other history tricks that you did not get in to... All great!
echo !-2:2
^replacethis^withthis
!?string?
echo !!:$:h
echo !!:$:e
echo !!:$:r
echo repeat this twice !#:1*
fc
shopt -s histverify
export HISTIGNORE="&:[ ]*:fg:bg:jobs:kill:exit:logout"
here is a simple cheat-sheet for some of the stuff.
I guess the cueCat is out of the bag... You know, I'm glad this is anonymous.
Wrong joke, sucka.
hansamurai was referring to the Wigner's friend thought experiment while MajikSheff was referring to the "SchrÃdinger's cat" thought experiment.
Quick Ref
QuickRef currently includes: C, C++, CSS, HTML, HTML DOM, Java, JavaScript, MySQL, Perl, PHP, Python, and Ruby
Still looking for underpowered...
My (obsd)firewall/proxy/smb is running strong on my 25DX. Of course I'd never add a software raid on that, but also would not ever run a software raid for any reason.
If you can not figure out vi, emacs, or any other cli text editor then why should we trust your programming?
Understanding the BASICS should be required.
Earlier someone compaired an IDE to a spell checker. An IDE does much more and is a grammer checker as well.
Do we teach english classes with grammer checkers? (substitute your own language if not english)
no.
Do we teach spelling with spell checkers?
I sure as hell hope not.
Then why should we teach programming with an IDE?
Hell, IDE's don't even pass lint most of the time. What does that show? And if you don't know what lint is then put away your IDE for a month(outside of work) and go back to the basics. Learn on your own and stop being lazy.
most of his facts are true, unlike the ones that the US government is telling you.
Huh?
I was going to suggest something similar.
An opensource frontend (cluster if required) that acts as a gateway to your exchange backend.
This is exactly what my company does and it works very well. I have, infact, never recieved a single piece of spam. It can be configured to touch base with the exchange backend to insure a real account/group is on the recieving end and 550 anything else.
NEVER!
Hell, I still have a few hours until my shift starts anyways. ABUSE MY BANDWIDTH!
Here are a few mirrors to use up. I'll probably bring them down after a few TB of transfer...
6 _hajjinet.mp4
0 6_hajjinet.mp4
New Jersey
http://www.def-con.org/~nocfed/downloads/notacon0
Texas
http://www2.def-con.org/~nocfed/downloads/notacon
One day I can look back on this...
/etc/motd
gaia$ cat
OpenBSD 3.9-current (gaia) #3: Fri Apr 21 12:38:12 CDT 2006
Don't fuck around or I'll kill you.
datacenter2, datacenter4, and datacenter5 all allowed to connect to gaia:22
if you need anything then don't ask because I don't give a fsck.
and one more thing... die
gaia$
sudo bash ???
/var/named/chroot/var/zones/master/d/domain.tld
/var/named/chroot/var/zones/master/d/domain.tld /var/named/chroot/var/zones/master/d/domain.tld: Permission denied /var/named/chroot/var/zones/master/d/domain.tld /var/named/chroot/var/zones/master/d/domain.tld /var/named/chroot/var/zones/master/d/domain2.tld /var/named/chroot/var/zones/master/d/domain2.tld /var/log/secure /var/log/secure: Permission denied /var/log/secure /var/named/chroot/var/zones/master/d/domain.tld /var/named/chroot/var/zones/master/d/domain2.tld
Do people actually do that? If you want a root shell it's sudo -s. But that is NOT the purpose of sudo. You want accountability on your server(s).
And as pointed out by another already, sudo !! or sudo !-2, sudo !-3, sudo !command... Understanding your environment should be one of the first things you learn.
user/server:/path$ vi
"/var/named/chroot/var/zones/master/d/domain.tld" [New File]
user/server:/path$ ls -l
ls:
user/server:/path$ sudo !!
sudo ls -l
-rw-r----- 1 named wheel 7185 Aug 6 2005
user/server:/path$ ^.^2.
sudo ls -l
-rw-r----- 1 named wheel 1121 Aug 6 2005
user/server:/path$ sudo -s
root/server:/path# id -p
login user
uid root
groups wheel kmem sys tty operator staff guest
root/server:/path# ^D
exit
user/server:/path$ tail -n3
tail:
user/server:/path$ sudo !!
sudo tail -n3
Apr 15 22:10:54 server sudo: user : TTY=ttyp1 ; PWD=/path ; USER=root ; COMMAND=ls -l
Apr 15 22:10:55 server sudo: user : TTY=ttyp1 ; PWD=/path ; USER=root ; COMMAND=ls -l
Apr 15 22:10:57 server sudo: user : TTY=ttyp1 ; PWD=/path ; USER=root ; COMMAND=/usr/local/bin/bash
That's right, we don't have our user associated with our commands when in a root shell via sudo. There are patches and shells that will log this information, but they should not be needed. Correctly using the tools are as important as the tools themselves.
You will ALWAYS want to have individual logins for every administrator and TEACH your admin's howto use sudo correctly if they do not know already.
As for the original question: nobody should EVER login as root, EVER, PERIOD.
They have two options for this:
1) Cygwin
2) Dedicated Shell Server
Within this environment you will use fanout from Bill Stearns
A) If the remote systems are not set to ``UseLogin yes'' in sshd_config then the custom environment can be used with environment='whatever=whatever' in the remote ~/.ssh/authorized_keys. This, of course, would also require a key which may not be possible as well as ``PermitUserEnvironment yes'' set in sshd_config.
B) The env channel from the ssh client can set the environment on the remote system. This also will not work if ``PermitUserEnvironment no'' is set in sshd_config.
C) If ``PermitUserEnvironment yes'' is set then ~/.ssh/environment will also be evaluated upon login. This would not be advised as it appears as though multiple users aside from the admin's would be using the account(s).
Remember, A and B rely on C to work.
You will recieve the following if it is not setup correctly:
Server refused to set environment variables
Anyways, fanout is the method of choice for issuing commands across multiple servers at the same time while providing the output of those commands to the controling terminal. Just setup a few variables and include them in the remote command(s).
more info
for those that seem to not be able to get the video from the main site
New York mirror
Italy mirror
http://www2.def-con.org/media/MATRIX_SVCD_JH.rar
and it will be removed in a couple of hours
more mirrors... heh, why only slash the main site and normal mirror?
homepage.mac.com/macnnadmins/.Pictures/unixad.jpg
www.osuweb.net/~ahaning/unixad.jpg
www2.def-con.org/images/unixad.jpg