63 is the total length of an FQDN, so assuming (for kindess) a "www" and a "com", that's 57. But we also have to include shorter domains, so it's 37^57 + 37^56 +... + 37 (ignoring that hyphens can't start or end a domain).
However, the latter numbers are going to add almost nothing to the original huge ^57, so doubling (.com and.net), let's say around $2*10^90.
All they have to do is hire Arthur Anderson to audit the accounts, and they won't just be bankrupt, they'll be turning a healthy profit...
That would only hold true if domain names could have an unlimited number of characters. I think that a domain has a limit of 64 characters, so given [a-z0-9-] as legit characters, we have a namespace of 37^64, ish, which is about 10^100 (since 64 * log(37) = 100).
Now, admittedly there are assumed to be only 10^80 particles in the universe...
That's actually good for us in my department: it means we can all see what each other is up to, but managers can't pencil in appointments under someone else's name, and people can't accidentally delete each other's stuff.
I admit, though, it would be nice to have a "let this calendar be editable by others" button.
Actually, I thought the Nazi's took the original clockwise swastika and turned it anticlockwise, to make it resemble two "s"s. (Clockwise means that if you attached rockets to the little sticky-out bits, it'd turn clockwise.)
Either way, I wouldn't make a swastika my company logo, clockwise or anti-clockwise - it'd cause trouble whatever.
The point is privilege escalation. If there's a hole in one of your services (as there are, from time to time), it won't hurt you too much if, say, an intruder is roaming around as an unprivileged user, such as www or nobody. If they can exploit a setuid binary to give themselves a backdoor, change accounts, basically do anything root can, then that's a hell of a lot worse.
Security comes in layers. I want as many layers as possible.
Yes, most OS X security vulns are pretty low-key, certainly from a desktop point of view. But it was a slight mistrust of Apple security that made me go for vanilla BSD for our main public servers, and leave our (rather nice) XServes inaccessible behind a strong firewall. Now I feel vindicated - potential privilege escalation on a public server gives me the shivers.
Silly bugger's gone and used 'C' twice - first for competitiveness, the second for complexity. And what's with the superfluous brackets anyway? Load of cobblers.
There are no known viruses *until you install Office X*.
Got infected by Walker-E the other day. A Word macro virus that was written in 1999 actually infected Word on OS X. And all documents that passed through it.
Now, to be fair, this isn't a virus that runs on OS X, it's a virus that runs under VBS emulation. However, that's not a distinction most users will make...
That's a little like all those early sound-cards claiming to be "CD-quality", when actually they meant "we have 16 bit converters". The fact that the converters sounded like they were made from soggy paper didn't seem to occur to anyone...
At the Watershed here in Bristol, we've just shown it. For free. On a nice big screen. Quality was pretty good. We're showing it twice a day for the rest of the weekend.
(Hehe, just watching the BBC report: the reporter used an Apple Mac to view it. Fake! Fake! You'll see me briefly if you go and watch the 6 o'clock bulletin online - report is 24 minutes ish in:) )
What, you mean you can't just type "strength of silkworm silk in pounds per square inch" into google calculator? Pah. I mean, it'll cope with nanoparsecs per fortnight...:)
OK, I've just downloaded 3 in Three, and it's brilliant. Just one question... how the hell do the elevator levels work? I get how the numbers at the bottom show the movement, but why do the damn elevators either side move as well?
Hmmm, how timely. I've just spent my sunny Saturday migrating from ASIP 6 to OS X server (mostly a file server). I found the admin tools fine, everything worked, etc, etc. A few annoying niggles, but I was happy.
Where I'm *not* happy is the total lack of configurability of the services. You can't, as far as I can tell, assign different sharepoints to different interfaces. Nor can you assign different *firewall* rules to different interfaces, for God's sake (not without using ipfw on the command line, anyway). If I'm wrong here, please, someone, put me out of my misery... but I spent enough time looking for the answers, and couldn't find any.
That said, the thing works. And after OS 9, it'll be a blessed relief. But I still don't feel as good friends with it as I do my 6 FreeBSD servers.
It's rather easier just to boot from the installer CD and select "change password" from the Installer menu. Change an admin's password, and away you go...
Slashdot Mirror
FYI, the eMac is slightly shorter front-to-back than a CRT iMac :)
It is, however, wider, higher, heavier, and a pain to move around. Good machines though, and the CRT is flat which makes it pleasant to work at.
Oliver.
Except for me, it tried to correct the spelling to "pornporn" (no space).
I can't believe MS screwed up *that* much. But then, nor can I stop laughing.
Sorry, slightly wrong calculation.
... + 37 (ignoring that hyphens can't start or end a domain).
.net), let's say around $2*10^90.
63 is the total length of an FQDN, so assuming (for kindess) a "www" and a "com", that's 57. But we also have to include shorter domains, so it's 37^57 + 37^56 +
However, the latter numbers are going to add almost nothing to the original huge ^57, so doubling (.com and
All they have to do is hire Arthur Anderson to audit the accounts, and they won't just be bankrupt, they'll be turning a healthy profit...
Anyway. Back to work.
That would only hold true if domain names could have an unlimited number of characters. I think that a domain has a limit of 64 characters, so given [a-z0-9-] as legit characters, we have a namespace of 37^64, ish, which is about 10^100 (since 64 * log(37) = 100).
Now, admittedly there are assumed to be only 10^80 particles in the universe...
That's actually good for us in my department: it means we can all see what each other is up to, but managers can't pencil in appointments under someone else's name, and people can't accidentally delete each other's stuff.
I admit, though, it would be nice to have a "let this calendar be editable by others" button.
Actually, I thought the Nazi's took the original clockwise swastika and turned it anticlockwise, to make it resemble two "s"s. (Clockwise means that if you attached rockets to the little sticky-out bits, it'd turn clockwise.)
Either way, I wouldn't make a swastika my company logo, clockwise or anti-clockwise - it'd cause trouble whatever.
According to the site, DynDNS lets you publish SPF records if you want to. Don't know if you have to pay extra, but DynDNS is pretty reasonable :)
The point is privilege escalation. If there's a hole in one of your services (as there are, from time to time), it won't hurt you too much if, say, an intruder is roaming around as an unprivileged user, such as www or nobody. If they can exploit a setuid binary to give themselves a backdoor, change accounts, basically do anything root can, then that's a hell of a lot worse.
Security comes in layers. I want as many layers as possible.
As loads of people point out, this *is* remotely exploitable. It's just a setuid binary that doesn't validate its input correctly.
Yes, most OS X security vulns are pretty low-key, certainly from a desktop point of view. But it was a slight mistrust of Apple security that made me go for vanilla BSD for our main public servers, and leave our (rather nice) XServes inaccessible behind a strong firewall. Now I feel vindicated - potential privilege escalation on a public server gives me the shivers.
/me tries to will some of my 'insightful' moderations over to you...
Silly bugger's gone and used 'C' twice - first for competitiveness, the second for complexity. And what's with the superfluous brackets anyway? Load of cobblers.
There are no known viruses *until you install Office X*.
Got infected by Walker-E the other day. A Word macro virus that was written in 1999 actually infected Word on OS X. And all documents that passed through it.
Now, to be fair, this isn't a virus that runs on OS X, it's a virus that runs under VBS emulation. However, that's not a distinction most users will make...
Fecking Microsoft.
That's a little like all those early sound-cards claiming to be "CD-quality", when actually they meant "we have 16 bit converters". The fact that the converters sounded like they were made from soggy paper didn't seem to occur to anyone...
I thought the whole point of poptop was that it used PPTP, which is inherently insecure.
L2TP replaces it, and MS seems to have got it right this time.
They said "effectively", and they're right.
It "effectively" does other things too, but that's the effect that most people are going to notice.
I think you'll find you're just very unpopular... you have to be in other people's address books to get the worm forwarded onto you :)
Either that, or all your friends actually have a clue.
(no offence intended)
At the Watershed here in Bristol, we've just shown it. For free. On a nice big screen. Quality was pretty good. We're showing it twice a day for the rest of the weekend.
:) )
(Hehe, just watching the BBC report: the reporter used an Apple Mac to view it. Fake! Fake! You'll see me briefly if you go and watch the 6 o'clock bulletin online - report is 24 minutes ish in
What, you mean you can't just type "strength of silkworm silk in pounds per square inch" into google calculator? Pah. I mean, it'll cope with nanoparsecs per fortnight... :)
Or there's always the good old Fire thread.
Happy afternoon-wasting...
Also, putting lemon in Earl Grey ruins what makes it Earl Grey, namely the bergamot. A bit like drinking wine with a vinaigrette dressing. Tsk, tsk.
I always find that (full-fat) milk enhances the flavour of a particular tea, with the exception of jasmine.
OK, I've just downloaded 3 in Three, and it's brilliant. Just one question... how the hell do the elevator levels work? I get how the numbers at the bottom show the movement, but why do the damn elevators either side move as well?
Thanks for any tips...
Oliver.
Sure that isn't US foreign policy you're quoting there? :)
</ducks>
Hmmm, how timely. I've just spent my sunny Saturday migrating from ASIP 6 to OS X server (mostly a file server). I found the admin tools fine, everything worked, etc, etc. A few annoying niggles, but I was happy.
Where I'm *not* happy is the total lack of configurability of the services. You can't, as far as I can tell, assign different sharepoints to different interfaces. Nor can you assign different *firewall* rules to different interfaces, for God's sake (not without using ipfw on the command line, anyway). If I'm wrong here, please, someone, put me out of my misery... but I spent enough time looking for the answers, and couldn't find any.
That said, the thing works. And after OS 9, it'll be a blessed relief. But I still don't feel as good friends with it as I do my 6 FreeBSD servers.
Just my 2p.
It's rather easier just to boot from the installer CD and select "change password" from the Installer menu. Change an admin's password, and away you go...