An RSA private key is two prime numbers, the public key is the product of those primes. You only have to find the smaller of the two secret primes, so a full brute force search only has to consider numbers that are prime and less than the square root of the public key size. And I believe there are a number of other shortcuts that can be used to reduce the search. Whereas for EC keys (AFAIK) practically all of the key space of 128-bit integers are valid private keys.
The first option, every vote is passed down based on your preferences but at a reduced percentage weighting. And yes, it takes a long time to distribute preferences since there are so many candidates.
If you have sufficient programming experience, I'd recommend basing this solution on redgrep. It's an llvm based expression compiler that should be able to combine multiple expressions into a single machine code state machine, assuming it doesn't run out of memory in the process. With a bit of effort you could output all of your compiled expressions into a single executable so you'll only need to wait for the compilation time when you add more filters.
There is a huge correlation between borrowing more money and the level of employment. Borrowing money and spending it (and why would you borrow if not to spend?) creates income for other people and thus jobs. The reverse is also true, paying back or defaulting on debts destroys income and jobs.
Sure, there's currently a huge imbalance in who gets that income. But looking at the raw data, this relationship holds quite well.
Great, so lets just borrow more money, that will fix everything right? Well, no. Paying interest reduces the amount you can spend, so the higher the level of debt, the more we have to borrow just to cover the interest and keep the economy stable. And we've collectively borrowed a ridiculous amount of money over the last 60 years.
So first we have to reduce the level of debt, then monitor and stabilise the rate of borrowing so it has a much smaller effect on the economy.
This cycle has happened a number of times in recorded history. The distribution of debt is different this time when compared to the 1930's, the immediate impacts of reducing our debts have been different. And through the continual invention of various financial instruments, we dug ourselves into a *much* bigger debt hole.
But apparently the deadliest animal in Australia is the horse. Horses actually kill people. And if you're at the beach, swim between the life saver flags.
He's been in the local paper a few times as a human interest story during his life, but there's nothing available online that I can find. Though he has told me a fair number of anecdotes from work over the years.
Once he turned up to a job interview after being referred by an old colleague. The interviewer hastily excused himself to call the guy; "You didn't tell me he didn't have any hands". "I didn't think it was relevant to his ability".
After discovering that a Y2K compliance project was starting (ie using 4 digit dates everywhere), with an estimate of 8 people for 2 months. He came back after about 2 hours with all the changes checked in.
I haven't RTFA, but I'd guess his biggest gains came from scripting things that were annoying to say. If you invested the same amount of effort in automating things that you would normally type, you can get very big productivity gains.
My father is a (retired) software developer. When he was a kid he lost both of his hands in an accident. So how does he type? By holding a pen between his arms. How does he code efficiently? Lots and lots of domain specific vi macros. For example, with less than 10 key presses he can insert a well formatted SQL Insert statement, with all columns from the requested table pre-filled.
To me, it sounds more like "I believed my actions would change the world, but the world didn't change. What about those with the proper authority to actually change the world, did they do anything?"
I specifically said that this change would be complicated. But it could be done with a set of configurable regular expressions, or new server side language semantics to indicate which strings were sensitive.
And of course they'll get a commission on any actual sales. This is the same drive for monetisation that lead network solutions to direct you to advertising laden search results instead of returning NXDOMAIN.
The DEFLATE and gzip formats allows multiple blocks of compressed data as well as blocks containing literals with no compression. Plus, just because the default implementation always looks for duplicate strings, doesn't mean you always have to do so. While it would add a heck of a lot of complexity, it should be possible for a web server to ignore duplicates that occur in sensitive strings, and output them in literal blocks so that they don't effect the frequency data of the rest of the stream. All without requiring any changes to browser implementations. This is far from simple, but could probably be done in a generic way for well known http headers.
So web servers need to disable gzip & deflate compression on any https page that might contain something sensitive? Sounds like an easy enough fix to me.
Labor's NBN is much better than the Liberal plan, but it's not a utopia. There are plenty of issues with the current design that could be simplified and improved.
An ISP should provide me the ability to send and receive IP packets, routed to and from other IP addresses on the globally route-able internet. Nothing more, nothing less.
If I'm not allowed to use a connection continuously at it's peak capacity, then write the exact limit in bandwidth terms into the contract. eg no more than X bandwidth Up/Down over period Y.
Slashdot Mirror
Adding to the above response, on an SSD even the log needs to be wear levelled, so where do you keep the log of where your log is?
An RSA private key is two prime numbers, the public key is the product of those primes. You only have to find the smaller of the two secret primes, so a full brute force search only has to consider numbers that are prime and less than the square root of the public key size. And I believe there are a number of other shortcuts that can be used to reduce the search. Whereas for EC keys (AFAIK) practically all of the key space of 128-bit integers are valid private keys.
The first option, every vote is passed down based on your preferences but at a reduced percentage weighting. And yes, it takes a long time to distribute preferences since there are so many candidates.
And I assume you're also not allowed to direct them outside to those people who could help answer that question?
It's a pity that all informal votes are clumped together under one number. How many of those are deliberate?
Remember to delete history on that kiddos.
If this history makes it onto a disk, you've already lost.
If you have sufficient programming experience, I'd recommend basing this solution on redgrep. It's an llvm based expression compiler that should be able to combine multiple expressions into a single machine code state machine, assuming it doesn't run out of memory in the process. With a bit of effort you could output all of your compiled expressions into a single executable so you'll only need to wait for the compilation time when you add more filters.
History doesn't repeat, but it sure does rhyme.
There is a huge correlation between borrowing more money and the level of employment. Borrowing money and spending it (and why would you borrow if not to spend?) creates income for other people and thus jobs. The reverse is also true, paying back or defaulting on debts destroys income and jobs.
Sure, there's currently a huge imbalance in who gets that income. But looking at the raw data, this relationship holds quite well.
Great, so lets just borrow more money, that will fix everything right? Well, no. Paying interest reduces the amount you can spend, so the higher the level of debt, the more we have to borrow just to cover the interest and keep the economy stable. And we've collectively borrowed a ridiculous amount of money over the last 60 years.
So first we have to reduce the level of debt, then monitor and stabilise the rate of borrowing so it has a much smaller effect on the economy.
This cycle has happened a number of times in recorded history. The distribution of debt is different this time when compared to the 1930's, the immediate impacts of reducing our debts have been different. And through the continual invention of various financial instruments, we dug ourselves into a *much* bigger debt hole.
Incognito modes have never been about being anonymous to the web sites you visit. It's all about leaving no trace on the local machine.
I don't want any coffee that might have actual "crap" in it. So at least with this test I could be certain of that fact.
But apparently the deadliest animal in Australia is the horse. Horses actually kill people. And if you're at the beach, swim between the life saver flags.
He's been in the local paper a few times as a human interest story during his life, but there's nothing available online that I can find. Though he has told me a fair number of anecdotes from work over the years.
Once he turned up to a job interview after being referred by an old colleague. The interviewer hastily excused himself to call the guy; "You didn't tell me he didn't have any hands". "I didn't think it was relevant to his ability".
After discovering that a Y2K compliance project was starting (ie using 4 digit dates everywhere), with an estimate of 8 people for 2 months. He came back after about 2 hours with all the changes checked in.
I haven't RTFA, but I'd guess his biggest gains came from scripting things that were annoying to say. If you invested the same amount of effort in automating things that you would normally type, you can get very big productivity gains.
My father is a (retired) software developer. When he was a kid he lost both of his hands in an accident. So how does he type? By holding a pen between his arms. How does he code efficiently? Lots and lots of domain specific vi macros. For example, with less than 10 key presses he can insert a well formatted SQL Insert statement, with all columns from the requested table pre-filled.
To me, it sounds more like "I believed my actions would change the world, but the world didn't change. What about those with the proper authority to actually change the world, did they do anything?"
I specifically said that this change would be complicated. But it could be done with a set of configurable regular expressions, or new server side language semantics to indicate which strings were sensitive.
No it means that when those people put their phone down, they are still likely to be weaving from side to side, slower than the speed limit.
A promissory note however...
And of course they'll get a commission on any actual sales. This is the same drive for monetisation that lead network solutions to direct you to advertising laden search results instead of returning NXDOMAIN.
CRIME was about TLS and detecting the request. BREACH is about detecting something about the response, that could be in the header, or not.
The DEFLATE and gzip formats allows multiple blocks of compressed data as well as blocks containing literals with no compression. Plus, just because the default implementation always looks for duplicate strings, doesn't mean you always have to do so. While it would add a heck of a lot of complexity, it should be possible for a web server to ignore duplicates that occur in sensitive strings, and output them in literal blocks so that they don't effect the frequency data of the rest of the stream. All without requiring any changes to browser implementations. This is far from simple, but could probably be done in a generic way for well known http headers.
So web servers need to disable gzip & deflate compression on any https page that might contain something sensitive? Sounds like an easy enough fix to me.
To add more fuel, Simon Hacket's teardown of the FTTN approach. The guy who ran Internode, one of Australia's largest ISPs.
Labor's NBN is much better than the Liberal plan, but it's not a utopia. There are plenty of issues with the current design that could be simplified and improved.
Line 1: Whoosh.
An ISP should provide me the ability to send and receive IP packets, routed to and from other IP addresses on the globally route-able internet. Nothing more, nothing less.
If I'm not allowed to use a connection continuously at it's peak capacity, then write the exact limit in bandwidth terms into the contract. eg no more than X bandwidth Up/Down over period Y.
Don't like it? Don't run an ISP.