The author is fanboying Java. It's Java, it should be everywhere, Java is awesome, etc.
Java is proprietary, supplanted by CIL, which is ISO standard. There are better languages--like Python--and anything could run on CIL if you got LLVM to output CIL. You could even run Ruby and Java on CIL, if you were so insane as to go with Ruby. C and C++ work on CIL.
You just described what it did, and described 1080i. It's like describing a human with male junk and physique and chromosomes and claiming you were promised a woman, and when someone points out it sounds like you got a man instead, you're like, "It's not a man, either."
libpoppler works; it just only meets the requirements that libpoppler was designed for. It correctly displays most PDFs, but fails with esoteric features used only in a small subset.
In that sense, libpoppler is like a swiffer mop: it handles most normal dirt, dust, and general cleaning needs for tile and hardwood; but you will need a mop, or potentially nylon or bristle scrubbers and power tools, to clean some deep-set grime from linoleum or porcelain tile. I've had mops fail to clean traffic grime from kitchen linoleum, at all; stuck a drill brush in a 3000RPM 600W output cordless drill and blasted that shit right off.
After these databases have been added, and after final firmware validation and testing, the OEM locks the firmware from editing, except for updates that are signed with the correct key or updates by a physically present user who is using firmware menus, and then generates a platform key (PK). The PK can be used to sign updates to the KEK or to turn off Secure Boot.
So if you have the PK, you can sign updates to the KEK. Okay, so this requires the user to intentionally load a PK first, and store it on the machine. Makes sense.
So then the chain is shorter: have your kernel load a signed initrd, perform useful scans, and then load the real initrd and engage the boot process. I likes this.
Even worse: he proposes that our universe is only 3 spatial dimensions, when it's well-accepted that this is a consequence of inflation. Originally, we had ten dimensions in balance; but the force between them gave out, and six of these contracted while three expanded. The three expanding dimensions make up our growing bubble of space--the universe--while the six shrinking are not major forces in our universe, but possibly have an impact on the quantum level (see: quantum foam).
Thus we have three-dimensional space-time, and six dimensions of no note. It's like having a few rich people and some non-notable Ska.
Oh, huh. SecureBoot isn't Palladium; it's some new-fanegaled UEFI feature.
It looks like you can insert new keys into the SecureBoot DB with dpkg-reconfigure secureboot-db in Ubuntu, so sufficient OS-level access should allow for bypassing SecureBoot in UEFI. This is a little easier than it was with the TPM, I guess.
That depends on a TPM, which depends largely on a secret key in the OS RAM (magic cookie) that can be accessed if you have a kernel exploit. From there, you can modify the TPM.
And it doesn't end there. To really get a high-security setup, boot chain, you need to do a lot of start-up work.
To start, you need a pre-boot scan. The occasional scan from a USB image would provide an integrity check: EFI settings (boot order), bootloader, kernel image, and initrd. You'd need to validate the boot loader against the installed package, validate the installed ClamAV database signature, pull ClamAV updates if the signature doesn't validate, validate kernels against installed packages, and validate the bootloader and kernel and initrd contents via ClamAV.
At boot time, the initrd should do similar: it should run clamscan against ClamAV itself, init, the basic libraries and services, and so on. This takes about 9 seconds--it takes 7 seconds to start ClamAV, so a running, resident service to execute scans is desirable for continuous scanning.
During boot, a service loads which hooks into LSM or otherwise to catch all execve(), mmap(), and open() calls, as well as any writes.Any such call first checks if the access is to a file; if so, it checks if the file is known safe; if not, it validates the file. If the file does not validate, it taints the process or blocks access. If the process is tainted and is allowed to write to a file, it un-validates that file. Upon load, the daemon immediately scans all running processes, checking their open files (including the main binary, mmap()ed segments, etc.) for validation.
To validate, the scanner daemon scans the file. If the file contains no malware, it's entered into a patricia trie and marked as clean. If it contains malware, it's entered as malware. Whenever the file enters an unknown state, it's removed from the trie. Patricia tries are compact structures which branch away from common prefixes: "/usr/lib/libc.so.6" and "/usr/lib/libclobber.so.2" are entered as "/usr/lib/libc" pointing to ".so.6" and "lobber.so.2"; likewise, more entries will create breaks after "/usr/" and "lib/lib" and whatever else. 100MB of RAM should suffice to track almost 300,000 files.
Any already-validated files are skipped: a fast trie look-up is performed, and the state is returned. If the file is not found in the trie, it is validated. If the file is written to by a tainted process, it's marked as tainted. If a process opens a malware file, it is marked as tainted.
For further protection, processes should not be allowed to transition any memory area from non-executable to executable, or to a state of both writability and executability. This prevents direct code injection, as you cannot write to executable code, and you cannot execute writable code. Further, tracking of processes which have communicated with tainted processes (IPC, pipes, sockets, network connections, etc.) should be done.
Now you can see that a tainted malware app has connected to your Skype process!
OIG explained to us that each viewing of an illegal child pornography image re-victimizes the children in it: as soon as you open the file, some woman somewhere suddenly stops, gasps, and holds her tummy, then begins to sob inconsolably.
OIG told us they had "hashes", then explained feature extraction as a "hash". People are insanely non-technical and use the wrong words all the time, because they can't use English properly.
increasing demand without providing incentive? Like, not purchasing?
How is this a sustainable business? The sheer volume of homeless in America has increased the demand for free housing greatly. Where is Pfeizer with the new free-housing research?
Yes. You would think in a world of information being impossible to put back in the jar, the emphasis would be on distribution and solicitation--payment for the materials. The materials themselves are criminal evidence; the creation of said materials are illegal; and the monetary funding of said materials increases the value against the risk proposition.
We've somehow decided that hoarders are dangerous, and commanded them to be not-dangerous by not hoarding pictures and videos. Considering the human trafficking involved in actually making these videos, I say we have bigger problems, and law enforcement is wasting its time.
The tire that blew hadn't been subjected to abuse. I replaced the ones that had been abused with better tires, because I wanted an upgrade; I hated the stock tires. Got rid of the one I'd ridden flat in the transaction.
It was, at the time, fully inflated and in good condition. My TPMS wasn't alarming at me. The tire just blew, and the car started going thud-thud-thud-thud while driving; I assumed I had a flat tire, and found instead what looked like it may have once been a tire. TPMS is marketed as a safety feature to prevent driving on a low tire, because driving on a low tire can cause a blowout, which supposedly causes the car to spin out of control; I could have readily continued at 80mph on that tire until it ripped off the wheel, had I not been concerned for the welfare of the vehicle, so of course I didn't guess the tire blew apart into small, loosely-attached fragments.
So yeah. Tires ridden flat on the drive wheels at expressway speeds for hundreds of miles? No problem. Tires not subject to abuse? Explode. Obviously abusing tires doesn't extend their life; I can only assume they blow up pretty much when they care to.
Uh. It had no useful impact on emissions, it cost more money to administrate than it generated, and it had negative economic impacts. So it failed to accomplish its goal even in part, it failed to provide additional revenue to fund other efforts, and it failed to create jobs.
Of course the coal lobby had stake. It annoyed the coal lobby. It also cost the government money, and didn't do a damned thing it was supposed to. That counts as "didn't work".
If you have tires rated to handle 100PSI without fault, you don't have $80 tires.
Lorry tires are run at 125PSI fairly often. They're built that way. They're also large, handle long-distance driving fine, and cost $2000+.
The high pressure helps with puncture resistance and braking. Not so sure about cornering; it's not a single-track vehicle, and they're not hilariously cambered for lapping track. It's a road vehicle for driving on normal highway at proscribed speeds.
My tires are rated for 50 and I run them about 5 below. The car suggests 32 for load, as this will keep normal tires from ballooning (high spot in the middle, accelerated tread wear). My tires retain shape with or without load, so this is not a problem; they perform better with a more round profile.
My TPMS had been alarming at me, but I ignored it. It turns out I knocked a nail out of the tire when pulling out of the driveway, causing it to rapidly deflate. I assumed it was around 28PSI and not critical.
Slashdot Mirror
The author is fanboying Java. It's Java, it should be everywhere, Java is awesome, etc.
Java is proprietary, supplanted by CIL, which is ISO standard. There are better languages--like Python--and anything could run on CIL if you got LLVM to output CIL. You could even run Ruby and Java on CIL, if you were so insane as to go with Ruby. C and C++ work on CIL.
Are you RACIST?
Are you a REPUBLICAN?
Are you a RACIST REPUBLICAN?!
Then you can join the Racist Republican Association of America! Just watch this movie, RacistRepublicans from Outer Space!
You just described what it did, and described 1080i. It's like describing a human with male junk and physique and chromosomes and claiming you were promised a woman, and when someone points out it sounds like you got a man instead, you're like, "It's not a man, either."
libpoppler works; it just only meets the requirements that libpoppler was designed for. It correctly displays most PDFs, but fails with esoteric features used only in a small subset.
In that sense, libpoppler is like a swiffer mop: it handles most normal dirt, dust, and general cleaning needs for tile and hardwood; but you will need a mop, or potentially nylon or bristle scrubbers and power tools, to clean some deep-set grime from linoleum or porcelain tile. I've had mops fail to clean traffic grime from kitchen linoleum, at all; stuck a drill brush in a 3000RPM 600W output cordless drill and blasted that shit right off.
You just described 1080i, which is not 1080p.
Pretty much this. They're all just a waste of time.
Yes four-dimensional space-time, not three-dimensional space.
After these databases have been added, and after final firmware validation and testing, the OEM locks the firmware from editing, except for updates that are signed with the correct key or updates by a physically present user who is using firmware menus, and then generates a platform key (PK). The PK can be used to sign updates to the KEK or to turn off Secure Boot.
So if you have the PK, you can sign updates to the KEK. Okay, so this requires the user to intentionally load a PK first, and store it on the machine. Makes sense.
So then the chain is shorter: have your kernel load a signed initrd, perform useful scans, and then load the real initrd and engage the boot process. I likes this.
Even worse: he proposes that our universe is only 3 spatial dimensions, when it's well-accepted that this is a consequence of inflation. Originally, we had ten dimensions in balance; but the force between them gave out, and six of these contracted while three expanded. The three expanding dimensions make up our growing bubble of space--the universe--while the six shrinking are not major forces in our universe, but possibly have an impact on the quantum level (see: quantum foam).
Thus we have three-dimensional space-time, and six dimensions of no note. It's like having a few rich people and some non-notable Ska.
Security: Confidentiality, Integrity, Accessibility. Removing Accessibility is called a Denial of Service.
It's like you just said the only way to be safe from murder is to kill yourself.
Oh, huh. SecureBoot isn't Palladium; it's some new-fanegaled UEFI feature.
It looks like you can insert new keys into the SecureBoot DB with dpkg-reconfigure secureboot-db in Ubuntu, so sufficient OS-level access should allow for bypassing SecureBoot in UEFI. This is a little easier than it was with the TPM, I guess.
That depends on a TPM, which depends largely on a secret key in the OS RAM (magic cookie) that can be accessed if you have a kernel exploit. From there, you can modify the TPM.
And it doesn't end there. To really get a high-security setup, boot chain, you need to do a lot of start-up work.
To start, you need a pre-boot scan. The occasional scan from a USB image would provide an integrity check: EFI settings (boot order), bootloader, kernel image, and initrd. You'd need to validate the boot loader against the installed package, validate the installed ClamAV database signature, pull ClamAV updates if the signature doesn't validate, validate kernels against installed packages, and validate the bootloader and kernel and initrd contents via ClamAV.
At boot time, the initrd should do similar: it should run clamscan against ClamAV itself, init, the basic libraries and services, and so on. This takes about 9 seconds--it takes 7 seconds to start ClamAV, so a running, resident service to execute scans is desirable for continuous scanning.
During boot, a service loads which hooks into LSM or otherwise to catch all execve(), mmap(), and open() calls, as well as any writes.Any such call first checks if the access is to a file; if so, it checks if the file is known safe; if not, it validates the file. If the file does not validate, it taints the process or blocks access. If the process is tainted and is allowed to write to a file, it un-validates that file. Upon load, the daemon immediately scans all running processes, checking their open files (including the main binary, mmap()ed segments, etc.) for validation.
To validate, the scanner daemon scans the file. If the file contains no malware, it's entered into a patricia trie and marked as clean. If it contains malware, it's entered as malware. Whenever the file enters an unknown state, it's removed from the trie. Patricia tries are compact structures which branch away from common prefixes: "/usr/lib/libc.so.6" and "/usr/lib/libclobber.so.2" are entered as "/usr/lib/libc" pointing to ".so.6" and "lobber.so.2"; likewise, more entries will create breaks after "/usr/" and "lib/lib" and whatever else. 100MB of RAM should suffice to track almost 300,000 files.
Any already-validated files are skipped: a fast trie look-up is performed, and the state is returned. If the file is not found in the trie, it is validated. If the file is written to by a tainted process, it's marked as tainted. If a process opens a malware file, it is marked as tainted.
For further protection, processes should not be allowed to transition any memory area from non-executable to executable, or to a state of both writability and executability. This prevents direct code injection, as you cannot write to executable code, and you cannot execute writable code. Further, tracking of processes which have communicated with tainted processes (IPC, pipes, sockets, network connections, etc.) should be done.
Now you can see that a tainted malware app has connected to your Skype process!
OIG explained to us that each viewing of an illegal child pornography image re-victimizes the children in it: as soon as you open the file, some woman somewhere suddenly stops, gasps, and holds her tummy, then begins to sob inconsolably.
OIG told us they had "hashes", then explained feature extraction as a "hash". People are insanely non-technical and use the wrong words all the time, because they can't use English properly.
What if nobody paid for a ticket, but just torrented it?
increasing demand without providing incentive? Like, not purchasing?
How is this a sustainable business? The sheer volume of homeless in America has increased the demand for free housing greatly. Where is Pfeizer with the new free-housing research?
Essentially it puts them and the abused children out of work.
I'm sorry, but the implied argument of 12 year old whores doesn't hold water.
Everyone knows 12 year old hookers hold whiskey. Well, everyone who's vacationed in Cambodia. /too old to be flamebait
Yes. You would think in a world of information being impossible to put back in the jar, the emphasis would be on distribution and solicitation--payment for the materials. The materials themselves are criminal evidence; the creation of said materials are illegal; and the monetary funding of said materials increases the value against the risk proposition.
We've somehow decided that hoarders are dangerous, and commanded them to be not-dangerous by not hoarding pictures and videos. Considering the human trafficking involved in actually making these videos, I say we have bigger problems, and law enforcement is wasting its time.
You get a lot more use out of a boat oar pushing against the water than you do hurling it like a javelin away from your boat.
The tire that blew hadn't been subjected to abuse. I replaced the ones that had been abused with better tires, because I wanted an upgrade; I hated the stock tires. Got rid of the one I'd ridden flat in the transaction.
It was, at the time, fully inflated and in good condition. My TPMS wasn't alarming at me. The tire just blew, and the car started going thud-thud-thud-thud while driving; I assumed I had a flat tire, and found instead what looked like it may have once been a tire. TPMS is marketed as a safety feature to prevent driving on a low tire, because driving on a low tire can cause a blowout, which supposedly causes the car to spin out of control; I could have readily continued at 80mph on that tire until it ripped off the wheel, had I not been concerned for the welfare of the vehicle, so of course I didn't guess the tire blew apart into small, loosely-attached fragments.
So yeah. Tires ridden flat on the drive wheels at expressway speeds for hundreds of miles? No problem. Tires not subject to abuse? Explode. Obviously abusing tires doesn't extend their life; I can only assume they blow up pretty much when they care to.
Uh. It had no useful impact on emissions, it cost more money to administrate than it generated, and it had negative economic impacts. So it failed to accomplish its goal even in part, it failed to provide additional revenue to fund other efforts, and it failed to create jobs.
Of course the coal lobby had stake. It annoyed the coal lobby. It also cost the government money, and didn't do a damned thing it was supposed to. That counts as "didn't work".
If you have tires rated to handle 100PSI without fault, you don't have $80 tires.
Lorry tires are run at 125PSI fairly often. They're built that way. They're also large, handle long-distance driving fine, and cost $2000+.
The high pressure helps with puncture resistance and braking. Not so sure about cornering; it's not a single-track vehicle, and they're not hilariously cambered for lapping track. It's a road vehicle for driving on normal highway at proscribed speeds.
My tires are rated for 50 and I run them about 5 below. The car suggests 32 for load, as this will keep normal tires from ballooning (high spot in the middle, accelerated tread wear). My tires retain shape with or without load, so this is not a problem; they perform better with a more round profile.
My TPMS had been alarming at me, but I ignored it. It turns out I knocked a nail out of the tire when pulling out of the driveway, causing it to rapidly deflate. I assumed it was around 28PSI and not critical.