The other thing added is something we call protected admin. This is a mode that administrators run in by default. If someone is configured as an admin, their basic execution happens as a standard user. When they try to do something that requires the administrator privilege, the system prompts them to see if they want to elevate to admin to complete the task, and if they consent, just that task is elevated (this is more secure that SUPERUSR ON in Unix that elevates the entire session). When the task completes, the high privileged process is torn down. The system can also be configured to require a password on elevation.
Is it just me, or is this exactly what sudo has been doing for over 25 years? Good Unix admins don't run sessions as root. They run regular user accounts and execute their admin commands using sudo to elevate just that process. In fact, at least Fedora is set up to automatically prompt for root credentials when a regular user tries to run a command that requires root privileges..
Congratulations on the fine innovation you call "protected admin," guys!
What makes anonymous comments any less relevent than anonymous sources, the latter having actually toppled a presidency once upon a time.
I would say the most significant difference is the accomplished newspaper reporter that says, "A top-ranking governmental figure said,..."
In the days before King Bush, a journalist was protected from having to reveal their sources. They could vouch for their authenticity without compromising their anonymity. So, instead of having some anonymously sourced comment from who-knows-what crackpot, you had some sort of chain of trust, as short as it was. If you trusted the reporting journalist's credability, you could believe the anonymous source.
except its really self-abuse. Anyone else notice both Hexus articles were submitted by Steve Kerrison? That's steve.kerrison@HEXUS.net (or steve@stevekerrison.com) from the Hexus staff
... guess its one way to drum up advertising revenue.
You're absolutely right, the US Dvorak layout is biased towards English. The US Standard and UK Standard keyboard layouts are also biased towards English.
... or were you talking about the French Dvorak layout, which I assume to be biased towards French?
Keyboards are inherently language specific. They're used to input languages. A language neutral keyboard would very likely result in a different layout from US Dvorak.
However, I would hope your "objective test" takes into account a language's popularity, and, France^H^H^H^Hench isn't very popular anymore.
If BPL turns out to be evil, will that conflict with googles basic principle?
As is evident in several preceding posts, in many people's eyes, BPL has already shown itself to be evil. Personally, I am very disappointed that Google is investing in this technology. If I had stock, I'd be voicing my displeasure with their financial acumen by dumping it.
I actually got someone on that once. We were in a code review, and he was discussing his use of a semaphore in one module. I calmly asked, "Have you considered using a hamaphore instead?"
"What's a hamaphore?"
"Pounding nails."
(long pause)
(snicker)
It seems to me that the easier it is to implement in hardware, the more implementations will fit in a single FPGA/ASIC, the smaller/cheaper/faster a hardware-based brute-force attack would be...
Recommendation: stick with AES. We don't need YAWEA (Yet Another Weak Encryption Algorithm)...
Prospective web page when searching for Louis Vuitton:
Address: http://fr.google.com?q=louis%20vuitton
Web Images Groupes Annuaire Actualités
GOOGLE [ louis vuitton ] Rechercher
In order to comply with the court order of Magestrate (insert idiot's name here), Google has prohibited searches of the above trademark. Please use general categories instead of brand names for any item you may be searching for. We apologize for the confusion created while this legal situation is being resolved.
-----
Prospective letter to head of Louis Vuitton sales department:
Dear Sir,
Enclosed is a check refunding your current and pending advertisement contracts with all Google subsidiaries. In compliance with court order, you are hereby informed that the trademarks "Louis Vuitton," "Vuitton" and "LV" have been entered as banned words on all Google search engines. As ordered, any advertisement contracts using these trademarks have been cancelled and their fees refunded. Consumers searching for these trademarks will be informed of the lawsuit initiating this action and encouraged to perform general category searches for the product they are interested in.
Regards,
(Google Corporate Officer)
Encl: Check
-----
Leaked internal Google memo:
Screw them if they want to interfere with our business. We don't need their advertising Francs!
Slashdot could implement something like this, it would make article comments meaningful again.
They could even selectively add or omit it based on the comment's moderation. Include the nofollow tag by default, but if a comment with a link in it is moderated highly, remove the tag so search engines can use it. Sounds like the best of both worlds..
I have a suggestion for the next/code release: add a feature to the code that will scan the comments after they are submitted and [searches]search for grammatical errors. When an error is found, the incorrect word would be then shown in red in brackets, and a correct word would be put outside of the brackets with a link to the dictionary.
(Sorry, can't change font color, so pretend the bold word above is red..)
Are all women insatiable like this or did I just happen to hit the motherload?
Is she approaching 40?
Did she attend a private church-funded school?
Those are the best reasons I've been able to come up with to explain my situation.
Knock her up. That put an end to it for me.. All they want to do for the first trimester is sleep.
Thus far, the only solution I've found is to use some kind of SQL access plug-in for FileMaker. This way, I get to keep the FileMaker interface but ditch its lousy relational model. Unfortunately, I'd still have to pay for FileMaker, and the SQL plug-in requires tons of extra coding to pass the data from FileMaker to SQL and back again.
I think you're on the right track with this. Yes, it will take time and effort to build the FileMaker to SQL bridge. However, once that's in place, you've got your raw SQL access for the other apps you mentioned. Plus, you can start turning out reports directly from SQL, and create apps to enter data directly to SQL as needed. If you make them prettier/faster/easier than the "native" FileMaker interfaces, people will start using them instead. Before you know it, you've weaned everyone!
Short-term, you may or may not need the new FileMaker licenses (can you stick with the current version?), you will need the SQL plugin licenses, and you'll have to spend some time coding the SQL/FileMaker bridge.
Long-term, you've gained the raw DB access you need, provided an alternate means of both data entry and access, and released your data from proprietary lockin.
1) Put together your project plan and budget,
2) Compute the project's ROI,
3) Run it all by the comptroller,
4) ???
5) Profit!
Bullshit. Put an erase head after the read head. Write once, play once. That has been the case for decades. To claim it wasn't possible before, is a poor excuse to undo a decades-old accepted practice.
... and who's going to ge the first one of us to open that end-user product up and cut the leads going to the erase head?
There's a reason you don't find any products that use that type of read-once technology, besides the fact that nobody would pay extra for the erase head: there's always a way around it!
I don't think you are right with this. You're taking the word "process" too strict. I have not seen that it sasys in the patent that it needs to be a daemon.
How about something as mundane as traceroute (a setuid binary)?
For example:
I'm logged in as an unprivileged user.
I run "traceroute www.uspto.gov"
My shell makes a system call to the kernel to launch the traceroute executable.
The kernel (a previously running, privileged process if there ever was one) creates the traceroute process space and runs it as a privileged user.
It sounds to me like the setuid mechanism itself is prior art. As mentioned elsewhere, that's circa 1988 or so...
Slashdot Mirror
The other thing added is something we call protected admin. This is a mode that administrators run in by default. If someone is configured as an admin, their basic execution happens as a standard user. When they try to do something that requires the administrator privilege, the system prompts them to see if they want to elevate to admin to complete the task, and if they consent, just that task is elevated (this is more secure that SUPERUSR ON in Unix that elevates the entire session). When the task completes, the high privileged process is torn down. The system can also be configured to require a password on elevation.
Is it just me, or is this exactly what sudo has been doing for over 25 years? Good Unix admins don't run sessions as root. They run regular user accounts and execute their admin commands using sudo to elevate just that process. In fact, at least Fedora is set up to automatically prompt for root credentials when a regular user tries to run a command that requires root privileges..
Congratulations on the fine innovation you call "protected admin," guys!
Methinks you're just being pointlessly anal retentive for mod points' sake.
Anal-retentive is properly spelled with a hyphen.
Nobody laughs when I tell them that (I do get an occasional groan), but it never gets old to me!
Institute a cap on the total number of stories a given submitter can get accepted
Too easy to get around. Slashdot accounts are free.. You'd just end up with TripMaster1, TripMaster2 and TripMaster3.
What makes anonymous comments any less relevent than anonymous sources, the latter having actually toppled a presidency once upon a time.
..."
I would say the most significant difference is the accomplished newspaper reporter that says, "A top-ranking governmental figure said,
In the days before King Bush, a journalist was protected from having to reveal their sources. They could vouch for their authenticity without compromising their anonymity. So, instead of having some anonymously sourced comment from who-knows-what crackpot, you had some sort of chain of trust, as short as it was. If you trusted the reporting journalist's credability, you could believe the anonymous source.
Our neighbors to the North are looking ever more attractive...
You don't watch the news, do you?
Ahh.. where's my mod points when I need 'em!
Thanks for the belly laugh.. made my neighbors peer over the cube walls at me. 8-)
Happy "Abuse Hexus Day" everyone!
except its really self-abuse. Anyone else notice both Hexus articles were submitted by Steve Kerrison? That's steve.kerrison@HEXUS.net (or steve@stevekerrison.com) from the Hexus staff
... guess its one way to drum up advertising revenue.
case "the 20's":
s/the Boogyman/Soylent Green/g;
break;
The Dvorak layout is biased towards English.
Duh!
You're absolutely right, the US Dvorak layout is biased towards English. The US Standard and UK Standard keyboard layouts are also biased towards English.
... or were you talking about the French Dvorak layout, which I assume to be biased towards French?
Keyboards are inherently language specific. They're used to input languages. A language neutral keyboard would very likely result in a different layout from US Dvorak.
However, I would hope your "objective test" takes into account a language's popularity, and, France^H^H^H^Hench isn't very popular anymore.
If BPL turns out to be evil, will that conflict with googles basic principle?
As is evident in several preceding posts, in many people's eyes, BPL has already shown itself to be evil. Personally, I am very disappointed that Google is investing in this technology. If I had stock, I'd be voicing my displeasure with their financial acumen by dumping it.
One of them's a meta-for.
Booo!
That anything like a hamaphore?
I actually got someone on that once. We were in a code review, and he was discussing his use of a semaphore in one module. I calmly asked, "Have you considered using a hamaphore instead?"
"What's a hamaphore?"
"Pounding nails."
(long pause)
(snicker)
... and that they've put an awful lot of effort into making it efficient in hardware requiring a minimal number of gates.
Which in my view equates to "easier to brute-force." Am I missing something?
It seems to me that the easier it is to implement in hardware, the more implementations will fit in a single FPGA/ASIC, the smaller/cheaper/faster a hardware-based brute-force attack would be...
Recommendation: stick with AES. We don't need YAWEA (Yet Another Weak Encryption Algorithm)...
Prospective web page when searching for Louis Vuitton:
Address: http://fr.google.com?q=louis%20vuitton
Web Images Groupes Annuaire Actualités
GOOGLE [ louis vuitton ] Rechercher
In order to comply with the court order of Magestrate (insert idiot's name here), Google has prohibited searches of the above trademark. Please use general categories instead of brand names for any item you may be searching for. We apologize for the confusion created while this legal situation is being resolved.
-----
Prospective letter to head of Louis Vuitton sales department:
Dear Sir,
Enclosed is a check refunding your current and pending advertisement contracts with all Google subsidiaries. In compliance with court order, you are hereby informed that the trademarks "Louis Vuitton," "Vuitton" and "LV" have been entered as banned words on all Google search engines. As ordered, any advertisement contracts using these trademarks have been cancelled and their fees refunded. Consumers searching for these trademarks will be informed of the lawsuit initiating this action and encouraged to perform general category searches for the product they are interested in.
Regards,
(Google Corporate Officer)
Encl: Check
-----
Leaked internal Google memo:
Screw them if they want to interfere with our business. We don't need their advertising Francs!
Better yet, use atmopheric braking. The only rockets you'd really need are maneuvering thrusters..
Slashdot could implement something like this, it would make article comments meaningful again.
They could even selectively add or omit it based on the comment's moderation. Include the nofollow tag by default, but if a comment with a link in it is moderated highly, remove the tag so search engines can use it. Sounds like the best of both worlds..
For example:
/code release: add a feature to the code that will scan the comments after they are submitted and [searches] search for grammatical errors. When an error is found, the incorrect word would be then shown in red in brackets, and a correct word would be put outside of the brackets with a link to the dictionary.
I have a suggestion for the next
(Sorry, can't change font color, so pretend the bold word above is red..)
Are all women insatiable like this or did I just happen to hit the motherload?
Is she approaching 40?
Did she attend a private church-funded school?
Those are the best reasons I've been able to come up with to explain my situation.
Knock her up. That put an end to it for me.. All they want to do for the first trimester is sleep.
C'mon, Chuck! If you've going to post a URL to a high-bandwidth site, at least post it as a link...
LOL!
That's the first thing that popped into my head too when I saw the title. Of course, it helps that my TiVo captured it just last week...
Inside Akimbo one can find a 733 MHz Celeron, 64 MB of SDRAM, 80 GB hard drive and Windows CE.
Sounds an awful lot like my XBox.. but with a smaller HDD.. and no MS software!
Imagine a Beowulf cluster of CTSS installations running in 7094 emulators on a... oh, what's the point!
People wear analogue watches because they look much nicer than tacky digitals.
I wear an analog watch because time is an analog concept. That and they're often thinner than digital watches...
Thus far, the only solution I've found is to use some kind of SQL access plug-in for FileMaker. This way, I get to keep the FileMaker interface but ditch its lousy relational model. Unfortunately, I'd still have to pay for FileMaker, and the SQL plug-in requires tons of extra coding to pass the data from FileMaker to SQL and back again.
I think you're on the right track with this. Yes, it will take time and effort to build the FileMaker to SQL bridge. However, once that's in place, you've got your raw SQL access for the other apps you mentioned. Plus, you can start turning out reports directly from SQL, and create apps to enter data directly to SQL as needed. If you make them prettier/faster/easier than the "native" FileMaker interfaces, people will start using them instead. Before you know it, you've weaned everyone!
Short-term, you may or may not need the new FileMaker licenses (can you stick with the current version?), you will need the SQL plugin licenses, and you'll have to spend some time coding the SQL/FileMaker bridge.
Long-term, you've gained the raw DB access you need, provided an alternate means of both data entry and access, and released your data from proprietary lockin.
1) Put together your project plan and budget,
2) Compute the project's ROI,
3) Run it all by the comptroller,
4) ???
5) Profit!
Bullshit. Put an erase head after the read head. Write once, play once. That has been the case for decades. To claim it wasn't possible before, is a poor excuse to undo a decades-old accepted practice.
... and who's going to ge the first one of us to open that end-user product up and cut the leads going to the erase head?
There's a reason you don't find any products that use that type of read-once technology, besides the fact that nobody would pay extra for the erase head: there's always a way around it!
I don't think you are right with this. You're taking the word "process" too strict. I have not seen that it sasys in the patent that it needs to be a daemon.
How about something as mundane as traceroute (a setuid binary)?
For example:
I'm logged in as an unprivileged user.
I run "traceroute www.uspto.gov"
My shell makes a system call to the kernel to launch the traceroute executable.
The kernel (a previously running, privileged process if there ever was one) creates the traceroute process space and runs it as a privileged user.
It sounds to me like the setuid mechanism itself is prior art. As mentioned elsewhere, that's circa 1988 or so...