Re: 202 days Uptime in OpenBSD 3.6
Alexander Bochmann wrote:
...on Thu, Jan 11, 2007 at 08:42:35AM +0100, Marc Balmer wrote:
hmm, why are people so proud of their uptimes when it only show they
don't care for their systems?
Bah, uptimes (is it that time of the year again?)...
Last login: Sun Jan 7 19:22:19 2007 from xxx
OpenBSD 2.3 (LOCAL) #0: Wed Jul 31 12:51:38 CEST 2002
Welcome to OpenBSD: The proactively secure Unix-like operating system.
{104} ls -al /etc/localtime
lrwxr-xr-x 1 root wheel 33 Jun 12 1998 /etc/localtime -
/usr/share/zoneinfo/Europe/Berlin
That's an Internet-connected system, running mail, web, DNS.
It gets increasingly difficult to talk current software into
compiling on that platform, though.
Alex.
you must have a really reliable hard drive and power supply to last that
long without going down.
Re: 202 days Uptime in OpenBSD 3.6
Marc Balmer wrote: hmm, why are people so proud of their uptimes when it only show they don't care for their systems? I forgot to power it (a Sun IPC) down when I left the company: [draco:~]$ uname -a; uptime OpenBSD draco..com 2.6 GENERIC#287 sparc 11:55AM up 1538 days, 58 mins, 1 user, load averages: 0.22, 0.13, 0.09 Regards, Greg P.S. A current employee provided the uptime -- I didn't use a remote hole. ;) \|/ ___ \|/[EMAIL PROTECTED]+- 2048R/38BD6CAB -+ @~./'O o`\.~@| 02BD EF81 91B3 1B33 64C2 | /__( \___/ )__\ | 3247 6722 7006 38BD 6CAB | `\__`U_/' +--+
Re: 202 days Uptime in OpenBSD 3.6
Marc Balmer wrote:
hmm, why are people so proud of their uptimes when it only show they
don't care for their systems?
Below is a patch which adds an -i flag to 'uptime' converting an uptime
period to a size in inches:
evilkittens:w {160} ./uptime
11:13AM up 24 days, 16:42, 1 user, load averages: 0.14, 0.15, 0.13
evilkittens:w {161} ./uptime -i
11:13AM up 3 inches, 1 user, load averages: 0.14, 0.15, 0.13
evilkittens:w {162}
As you see, I better let my system run a bit longer :(
--- /usr/src/usr.bin/w/w.c Tue Jul 19 23:19:08 2005
+++ w.c Wed Jan 17 11:16:15 2007
@@ -92,6 +92,7 @@
intheader = 1; /* true if -h flag: don't print heading */
intnflag = 1; /* true if -n flag: don't convert addrs */
intsortidle; /* sort bu idle time */
+intinches = 0; /* compute len of uptime in inches */
char *sel_user; /* login of particular user selected */
char domain[MAXHOSTNAMELEN];
@@ -137,7 +138,7 @@
p = hiflM:N:asuw;
} else if (!strcmp(p, uptime)) {
wcmd = 0;
- p = ;
+ p = i;
} else
errx(1,
this program should be invoked only as \w\ or \uptime\);
@@ -149,7 +150,10 @@
header = 0;
break;
case 'i':
- sortidle = 1;
+ if (wcmd == 1)
+ sortidle = 1;
+ else
+ inches = 1;
break;
case 'M':
header = 0;
@@ -402,29 +406,36 @@
size = sizeof(boottime);
if (sysctl(mib, 2, boottime, size, NULL, 0) != -1) {
uptime = now - boottime.tv_sec;
- if (uptime 59) {
- uptime += 30;
- days = uptime / SECSPERDAY;
- uptime %= SECSPERDAY;
- hrs = uptime / SECSPERHOUR;
- uptime %= SECSPERHOUR;
- mins = uptime / SECSPERMIN;
+ if (inches == 1) {
+ inches = uptime / (60*60*24*7);
(void)printf( up);
- if (days 0)
- (void)printf( %d day%s,, days,
- days 1 ? s : );
- if (hrs 0 mins 0)
- (void)printf( %2d:%02d,, hrs, mins);
- else {
- if (hrs 0)
- (void)printf( %d hr%s,,
- hrs, hrs 1 ? s : );
- if (mins 0 || (days == 0 hrs == 0))
- (void)printf( %d min%s,,
- mins, mins != 1 ? s : );
- }
- } else
- printf( %d secs,, uptime);
+ (void)printf( %d inch%s,, inches, inches 1 ? es: );
+ }
+ else {
+ if (uptime 59) {
+ uptime += 30;
+ days = uptime / SECSPERDAY;
+ uptime %= SECSPERDAY;
+ hrs = uptime / SECSPERHOUR;
+ uptime %= SECSPERHOUR;
+ mins = uptime / SECSPERMIN;
+ (void)printf( up);
+ if (days 0)
+ (void)printf( %d day%s,, days,
+ days 1 ? s : );
+ if (hrs 0 mins 0)
+ (void)printf( %2d:%02d,, hrs, mins);
+ else {
+ if (hrs 0)
+ (void)printf( %d hr%s,,
+ hrs, hrs 1 ? s : );
+ if (mins 0 || (days == 0 hrs == 0))
+ (void)printf( %d min%s,,
+ mins, mins != 1 ? s : );
+ }
+ } else
+ printf( %d secs,, uptime);
+ }
}
/* Print number of users logged in to system */
Re: 202 days Uptime in OpenBSD 3.6
Don't forget about vulns in tcp/ip stack in summer 2005 2007/1/16, Olivier Meyer [EMAIL PROTECTED]: What really matters is the security of the applications you are running(httpd, sshd, sendmail,...). If you keep those up to date, the kernel really does not matter. If you look at http://openbsd.org/security.html, most of the openbsd bugs really are in openssh, the c library, or are a local privilege escalation attack that cannot be exploited remotely.
Re: 202 days Uptime in OpenBSD 3.6
...on Mon, Jan 15, 2007 at 11:20:27AM -0700, Darren Spruell wrote: On 1/15/07, Alexander Bochmann [EMAIL PROTECTED] wrote: Last login: Sun Jan 7 19:22:19 2007 from xxx OpenBSD 2.3 (LOCAL) #0: Wed Jul 31 12:51:38 CEST 2002 Do you sleep well at night exposing that system to the Internet? Yes. The setup is obscure enough to require a very targeted attack, and I'm still waiting for someone to come along and do that. Also, the services on the machine used to run on a SunOS 4 sun3 before this one was set up - so it's kind of a tradition to use an outdated system ;) One would question the amount of effort to ensure patch application Shure. But it's fun. Well, some strange kind of fun, at least. Also I can brag about it now and then. Alex.
Re: 202 days Uptime in OpenBSD 3.6
...on Thu, Jan 11, 2007 at 08:42:35AM +0100, Marc Balmer wrote:
hmm, why are people so proud of their uptimes when it only show they
don't care for their systems?
Bah, uptimes (is it that time of the year again?)...
Last login: Sun Jan 7 19:22:19 2007 from xxx
OpenBSD 2.3 (LOCAL) #0: Wed Jul 31 12:51:38 CEST 2002
Welcome to OpenBSD: The proactively secure Unix-like operating system.
{104} ls -al /etc/localtime
lrwxr-xr-x 1 root wheel 33 Jun 12 1998 /etc/localtime -
/usr/share/zoneinfo/Europe/Berlin
That's an Internet-connected system, running mail, web, DNS.
It gets increasingly difficult to talk current software into
compiling on that platform, though.
Alex.
Re: 202 days Uptime in OpenBSD 3.6
On 1/15/07, Alexander Bochmann [EMAIL PROTECTED] wrote:
...on Thu, Jan 11, 2007 at 08:42:35AM +0100, Marc Balmer wrote:
hmm, why are people so proud of their uptimes when it only show they
don't care for their systems?
Bah, uptimes (is it that time of the year again?)...
Last login: Sun Jan 7 19:22:19 2007 from xxx
OpenBSD 2.3 (LOCAL) #0: Wed Jul 31 12:51:38 CEST 2002
Welcome to OpenBSD: The proactively secure Unix-like operating system.
{104} ls -al /etc/localtime
lrwxr-xr-x 1 root wheel 33 Jun 12 1998 /etc/localtime -
/usr/share/zoneinfo/Europe/Berlin
That's an Internet-connected system, running mail, web, DNS.
Do you sleep well at night exposing that system to the Internet? One
would question the amount of effort to ensure patch application (if at
all possible) on a system so far out of date...
DS
Re: 202 days Uptime in OpenBSD 3.6
On Mon, Jan 15, 2007 at 11:20:27AM -0700, Darren Spruell wrote:
On 1/15/07, Alexander Bochmann [EMAIL PROTECTED] wrote:
...on Thu, Jan 11, 2007 at 08:42:35AM +0100, Marc Balmer wrote:
hmm, why are people so proud of their uptimes when it only show they
don't care for their systems?
Bah, uptimes (is it that time of the year again?)...
Last login: Sun Jan 7 19:22:19 2007 from xxx
OpenBSD 2.3 (LOCAL) #0: Wed Jul 31 12:51:38 CEST 2002
Welcome to OpenBSD: The proactively secure Unix-like operating system.
{104} ls -al /etc/localtime
lrwxr-xr-x 1 root wheel 33 Jun 12 1998 /etc/localtime -
/usr/share/zoneinfo/Europe/Berlin
That's an Internet-connected system, running mail, web, DNS.
Do you sleep well at night exposing that system to the Internet? One
would question the amount of effort to ensure patch application (if at
all possible) on a system so far out of date...
If you are careful, and know what you do, and know what software to run,
you can get away with a very small number of patches.
Still, I do try to upgrade at least once a year.
Joachim
Re: 202 days Uptime in OpenBSD 3.6
Joachim Schipper wrote:
On Mon, Jan 15, 2007 at 11:20:27AM -0700, Darren Spruell wrote:
On 1/15/07, Alexander Bochmann [EMAIL PROTECTED] wrote:
...on Thu, Jan 11, 2007 at 08:42:35AM +0100, Marc Balmer wrote:
hmm, why are people so proud of their uptimes when it only show they
don't care for their systems?
Bah, uptimes (is it that time of the year again?)...
Last login: Sun Jan 7 19:22:19 2007 from xxx
OpenBSD 2.3 (LOCAL) #0: Wed Jul 31 12:51:38 CEST 2002
Welcome to OpenBSD: The proactively secure Unix-like operating system.
{104} ls -al /etc/localtime
lrwxr-xr-x 1 root wheel 33 Jun 12 1998 /etc/localtime -
/usr/share/zoneinfo/Europe/Berlin
That's an Internet-connected system, running mail, web, DNS.
Do you sleep well at night exposing that system to the Internet? One
would question the amount of effort to ensure patch application (if at
all possible) on a system so far out of date...
If you are careful, and know what you do, and know what software to run,
you can get away with a very small number of patches.
Still, I do try to upgrade at least once a year.
Joachim
and behind a good firewall, even old systems like RH6 with a million
holes are never going to get exploited as long as you take proper care.
in a high volume, public facing infrastructure. there are too many
cpanel and IIS servers around to hack, trying to bust into an OBSD box
would mean you have to be a real hacker, like U4EA or DFENS or Radikahl
or Sidewinder or Tkiller or Datarape or One's looking for a car
with the doors unlocked, engine running, keys in the ignition, owner
nowhere in sight.
Can you show me some 3.6 exploits Alexander? It's hard to doubt someone
cares about their system when they hang out on the list. Perhaps
really, they actually know what they are doing eh?
Where would I get an exploit for 3.6?, which exploit would I choose?
Remote? How many hundreds of those are lying about for ready download?
Can you or anyone else we know on the list give a nice howto on this?
Just how easy is it compared to the old days when you could run nuke.c
on IRC chats and literally shut down someone's Mac Plus on them
mid-sentence? Now that was fun. Wasn't even a web back then, just
BITNET, majordomo, FTPlists, BB's, archie, WAIS, even encrypted chat
/dcc_chat /dcc_send (where'd that go?)
I have a 3.6 system right here, unpatched behind a firewall, and one not
behind a firewall. -i'd like to see some skills from the
fear-uncertainty-doubt 5th column since everyone's so absolutely sure
you'll get hacked if you turn on a computer at all and try to make it do
anything useful whatsoever.
uptime 412 days on #drgori he's running an ancient os because informix
hasn't altogether disappeared from the base of code run by our v1 app
made what, 6 years ago? boy if that one customer who needs it would
just scram. -practical need vs. non-useful-perfectionism. the ugly
flower never gets picked. I hate informix, but #drgori never goes
down, does it's job, and even though people try, -they just can't get
through the defenses in front of him.
Just curious Alexander. Just curious.
booya. biff y
-krb
Re: 202 days Uptime in OpenBSD 3.6
What really matters is the security of the applications you are
running(httpd, sshd, sendmail,...). If you keep those up to date, the
kernel really does not matter. If you look at
http://openbsd.org/security.html, most of the openbsd bugs really
are in openssh, the c library, or are a local privilege escalation
attack that cannot be exploited remotely.
On 1/15/07, Karl R. Balsmeier [EMAIL PROTECTED] wrote:
Joachim Schipper wrote:
On Mon, Jan 15, 2007 at 11:20:27AM -0700, Darren Spruell wrote:
On 1/15/07, Alexander Bochmann [EMAIL PROTECTED] wrote:
...on Thu, Jan 11, 2007 at 08:42:35AM +0100, Marc Balmer wrote:
hmm, why are people so proud of their uptimes when it only show they
don't care for their systems?
Bah, uptimes (is it that time of the year again?)...
Last login: Sun Jan 7 19:22:19 2007 from xxx
OpenBSD 2.3 (LOCAL) #0: Wed Jul 31 12:51:38 CEST 2002
Welcome to OpenBSD: The proactively secure Unix-like operating system.
{104} ls -al /etc/localtime
lrwxr-xr-x 1 root wheel 33 Jun 12 1998 /etc/localtime -
/usr/share/zoneinfo/Europe/Berlin
That's an Internet-connected system, running mail, web, DNS.
Do you sleep well at night exposing that system to the Internet? One
would question the amount of effort to ensure patch application (if at
all possible) on a system so far out of date...
If you are careful, and know what you do, and know what software to run,
you can get away with a very small number of patches.
Still, I do try to upgrade at least once a year.
Joachim
and behind a good firewall, even old systems like RH6 with a million
holes are never going to get exploited as long as you take proper care.
in a high volume, public facing infrastructure. there are too many
cpanel and IIS servers around to hack, trying to bust into an OBSD box
would mean you have to be a real hacker, like U4EA or DFENS or Radikahl
or Sidewinder or Tkiller or Datarape or One's looking for a car
with the doors unlocked, engine running, keys in the ignition, owner
nowhere in sight.
Can you show me some 3.6 exploits Alexander? It's hard to doubt someone
cares about their system when they hang out on the list. Perhaps
really, they actually know what they are doing eh?
Where would I get an exploit for 3.6?, which exploit would I choose?
Remote? How many hundreds of those are lying about for ready download?
Can you or anyone else we know on the list give a nice howto on this?
Just how easy is it compared to the old days when you could run nuke.c
on IRC chats and literally shut down someone's Mac Plus on them
mid-sentence? Now that was fun. Wasn't even a web back then, just
BITNET, majordomo, FTPlists, BB's, archie, WAIS, even encrypted chat
/dcc_chat /dcc_send (where'd that go?)
I have a 3.6 system right here, unpatched behind a firewall, and one not
behind a firewall. -i'd like to see some skills from the
fear-uncertainty-doubt 5th column since everyone's so absolutely sure
you'll get hacked if you turn on a computer at all and try to make it do
anything useful whatsoever.
uptime 412 days on #drgori he's running an ancient os because informix
hasn't altogether disappeared from the base of code run by our v1 app
made what, 6 years ago? boy if that one customer who needs it would
just scram. -practical need vs. non-useful-perfectionism. the ugly
flower never gets picked. I hate informix, but #drgori never goes
down, does it's job, and even though people try, -they just can't get
through the defenses in front of him.
Just curious Alexander. Just curious.
booya. biff y
-krb
--
--
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
Re: 202 days Uptime in OpenBSD 3.6
On Thu, 11 Jan 2007 07:57:44 +0100, Rico Secada wrote: On Wed, 10 Jan 2007 18:47:38 -0800 Greg Thomas [EMAIL PROTECTED] wrote: On 1/10/07, Francisco Valladolid [EMAIL PROTECTED] wrote: I have 202 days using OpenBSD 3.6 as router/firewall/ PPPOE. I want to share this screenshot. http://farm1.static.flickr.com/147/353353577_e8e875083d_o.jpg Wow, I am impressed, your dick is wy bigger than mine because I have become a eunuch for the kingdom of heaven's sake. (Matthew 19:12) My uptime is permanently stuck at zero now. Greg We all know that a long uptime means neglect, but that doesn't mean we should reply in a dumb way like that! Why the hell do you always feel you have to make people wanna go away!? Actually the thing you seem to have missed is that the OP's boot time was when the version used was already out of support. 3.6 became unsupported on the release of 3.8 on November 1 2005. That's a lot more than 202 days ago. And yes, Greg was not dumb. His riposte was particularly apposite in the way it referenced the original post. Sadly humour rarely crosses language barriers and so I know only one joke which can be literally translated from French to English and still be funny and AFAIK it doesn't work in German or Spanish or Italian. Maybe you just didn't get the satire in Greg's reply... Trust me - to an EFL person with any kind of clue (including the biblical reference) it was, at the very least, humourous. Chill out a bit, ok? In the beginning was The Word and The Word was Content-type: text/plain The Word of Rod.
Re: 202 days Uptime in OpenBSD 3.6
:D :D
Always buy the OpenBSD CD's please see it.
http://www.flickr.com/photos/sigueme/141498221/
http://www.flickr.com/photos/sigueme/286455116/
-the current -release (4.0) not arrived to my office yet, ... I don't know.
This machine is using 3.6 in a customers office, maybe he no need pay me for
updating your small router, but I have access to this machine.
;-)
On 1/11/07, Marc Balmer [EMAIL PROTECTED] wrote:
* Francisco Valladolid wrote:
I have 202 days using OpenBSD 3.6 as router/firewall/ PPPOE.
we bring out a new release every ~180 days, with fixes and new features.
If your uptime is longer than this, it is an indication that you did not
buy any new cd-roms from us, which you really should if you want to
support us... and 3.6 is quite old style these days, a much shorter
uptime, but with 4.0 would be so much better ;)
hmm, why are people so proud of their uptimes when it only show they
don't care for their systems?
--
---
Therefore, if anyone is in Christ, he is a new creation; the old has gone,
the new has come! - 2 Corinthians 5:17 (NIV)
---
Francisco Valladolid Hdez.
[EMAIL PROTECTED]
{Open}{Net}BSD user.
202 days Uptime in OpenBSD 3.6
I have 202 days using OpenBSD 3.6 as router/firewall/ PPPOE. I want to share this screenshot. http://farm1.static.flickr.com/147/353353577_e8e875083d_o.jpg Regards, -- --- Therefore, if anyone is in Christ, he is a new creation; the old has gone, the new has come! - 2 Corinthians 5:17 (NIV) --- Francisco Valladolid Hdez. [EMAIL PROTECTED] http://blog.bsdguy.net - http://www.flickr.com/photos/sigueme/
Re: 202 days Uptime in OpenBSD 3.6
On 1/10/07, Francisco Valladolid [EMAIL PROTECTED] wrote: I have 202 days using OpenBSD 3.6 as router/firewall/ PPPOE. I want to share this screenshot. http://farm1.static.flickr.com/147/353353577_e8e875083d_o.jpg Wow, I am impressed, your dick is wy bigger than mine because I have become a eunuch for the kingdom of heaven's sake. (Matthew 19:12) My uptime is permanently stuck at zero now. Greg
Re: 202 days Uptime in OpenBSD 3.6
On Wed, 10 Jan 2007 18:47:38 -0800 Greg Thomas [EMAIL PROTECTED] wrote: On 1/10/07, Francisco Valladolid [EMAIL PROTECTED] wrote: I have 202 days using OpenBSD 3.6 as router/firewall/ PPPOE. I want to share this screenshot. http://farm1.static.flickr.com/147/353353577_e8e875083d_o.jpg Wow, I am impressed, your dick is wy bigger than mine because I have become a eunuch for the kingdom of heaven's sake. (Matthew 19:12) My uptime is permanently stuck at zero now. Greg We all know that a long uptime means neglect, but that doesn't mean we should reply in a dumb way like that! Why the hell do you always feel you have to make people wanna go away!?
Re: 202 days Uptime in OpenBSD 3.6
* Francisco Valladolid wrote: I have 202 days using OpenBSD 3.6 as router/firewall/ PPPOE. we bring out a new release every ~180 days, with fixes and new features. If your uptime is longer than this, it is an indication that you did not buy any new cd-roms from us, which you really should if you want to support us... and 3.6 is quite old style these days, a much shorter uptime, but with 4.0 would be so much better ;) hmm, why are people so proud of their uptimes when it only show they don't care for their systems?
