The reason for choosing the closest server may merit more explanation. If you're on the west coast and you query a server on thr east coast, your accuracy suffers with every router and switch along that path, so you end up with some unknown offset from the NTP server's time. ISPs and geographically disperse companies don't have that problem. Here's why.
Comcast will have a DNS server / ntp server in Houston. It may have a GPS, tdma, or LTE reciever locally connected, but most importantly it peers with their servers I Miami, Denver, and San Jose. The one in Miami peers back with Houston - and Miami, PLUS San Jose and a tier 1. All of the Comcast NTP servers have to estimate the time sync, but *they all arrive at the same estimate*, because they peer with each other multilaterally. So they all end up with the same time, network time.
By getting your time from a nearby server that does mutual peering, you're getting network time from a server that is only a few milliseconds away, amd probably a *consistent* number of milliseconds, so ntp can make accurate estimates of delay.
The offset value we log isn't the actual difference between your clock and the peer clock, and the logged value is seconds, not milliseconds. If you see 0.08 in the log, that means we're *assuming* that you're about 0.08 *seconds* off from that peer.
If you ping a server "thousands of miles away", you'll notice each ping takes a different number of milliseconds. That difference in ping times, or jitter, is pretty much a hard limit on sync accuracy with the NTP protocol. If you get a response from a server thousands of miles away saying "it's exactly midnight", we don't know if that packet was generated 30ms ago or 35ms ago. So that loses 5ms of precision.
Back to your peerlog. The last four fields show the assumed offset, delay, dispersion and jitter (root mean square). Take delay, multiply by 0.25, then add the jitter, and that's roughly the accuracy you can expect. If you're using ntpclient, add the dispersion, as that's the dispersion of the server. If you're using ntpd, your dispersion value is arough estimate of your accuracy - in seconds.
The good news is, your ISP's DNS server and gateway are many milliseconds closer, and ine or both are probably NTP servers. You CAN get much more accurate time, you just need to use servers that are much, much network-closer to you, such as your ISP's DNS or gateway.
You can get time accurate to within about a thousand to a millionth of a second with PTP, using network time as your reference. That's the time standard used by thr vast majority of people, network time aka ntp time aka internet time, which is closely synced to GPS time.
So which time do you want to consider "correct" - the time used by 98% of the precision clocks, or the time used by one clock in Boulder?
NTP is super easy to use and pretty darn accurate as well. PTP is quite a bit more accurate, with microsecond synchronization within your network.
> only Nintendo can sell games in Nintendo 3DS eShop
And only you can sell stuff in Tepples' shop. So what? You can sell Nintendo 3DS games in your store. Nintnedo can sell them in their store, and I can sell them in mine. Contrast Apple - ONLY Apple can sell iOS applications. Walmart cannot sell them.
> only Nintendo can manufacture Nintendo 3DS Game Cards on publishers' behalf for "Walmart, on Amazon, GameStop, EA.com" to sell.
False. You can even easily buy individual blank cards at retail and put your own game on them. Two popular brands are Gateway 3DS and Sky3DS.
My mom architected the software system that made Dell a major manufacturer. When you placed your order online, it would check whether all the parts were already in stock or if your build would wait a day for parts. It checked which other machines were being built and scheduled yours for optimal efficiency switch between orders. After scheduling your build, it gave the customer an expected ship date.
They replaced that system with "a cool new system" made by young people who "know" JavaScript, from copy-pasting Stackoverflow. Node.js is cool because it's newer, so it must be better.
I wonder if you have any source for that, because everything I'm finding says otherwise, including Sprint's regulatory filing.
They may get some backhaul from AT&T, but that doesn't matter much to the users - the towers matter. Sprint's 3G service is CDMA, AT&T is GSM, so very obviously they aren't the same network - they aren't even the same TYPE of network.
For LTE, Sprint's legal filings compare their LTE network to AT&T's much larger network.
If you say gigawatt is more kilowatt, so the "plan" makes no sense, that's just because you hate nature and want everybody to die.
The audience for this stuff thinks about "should" and "want", not "how". How it's supposed to work is totally irrelevant, and doesn't even enter the minds of the people he's pandering to.
It's not that they actually think declaring / wishing something will make it magically happen like it does in the eco-cartoons. They don't think that saying "the government should give everyone free _____" will make stuff magically appear. It's that how, what the cost is, and unintended affects simply aren't relevant and never enter their mind. All that matters is what you want.
The headline is BS. It's the opposite of the announcement. Here's what the announcement actually said:
We had planned on getting to 50% by 2025, but our new target is 2035.
In other words, they announced that wind and solar are NOT. going to work out like they had previously said. By 2035 Macron will be long out of office and it will be somebody else's problem to explain why the new target is 2055.
I wouldn't know about who all makes / made cards for the Vita, but I know the major game companies ditched it a while back because few people use it.
In any event, the Vita hardly has a monopoly on handheld gaming, with the Nintendo 3DS series being far more popular, and phone / tablet Gam even more so. If Sony becomes the only company still trying to sell games for their failing handheld, who cares.
It's a phone plan that uses the networks of Sprint, T-Mobile, US Cellular, and selected wifi, with transparent handoff between them. Prices are good. You pay only for how much you use that month.
If you regularly use your phone to stream HD video all day, I haven't compared pricing for that use case. I have FiOS for internet and TV while I'm at home.
Yes, to get Sony's help, to have them believe you're actually a game company and not a crakz haxor, you need to have a company. That will cost about $250, you're right.
Compare with Apple, where you can only buy from Apple's store. With Apple, ONE company can sell apps, Apple. With Sony, ANY company can sell games.
The thing about opsec is you only have to screw up once. They tried getting the bad guy to connect without using a proxy, uaing the error message. The bad guy maintained opsec and didn't fall for it. So then they tried the next thing. If the bad guy didn't fall for that, the FBI would go to the next approach.
"the U.S. Copyright Office will not register a government edict that has been issued by any state, local, or territorial government, including legislative enactments, judicial decision, administrative rulings, public ordinances, or similar types of official legal materials." U.S. Copyright Office Practices  313.6(C)(2)
Not it explicitly says judicial decisions can not be registered for copyright. Yes I'm aware Lexis Nexus doesn't like that.
I noticed someone replied poo-pooing certs. Every time I've talked to people who say that in order to understand their thinking, it comes down to "entry level certifications don't guarantee expert knowledge".
MTA and MCSA are explicitly entry-level certifications. They are evidence that the person has sufficient knowledge to BEGIN working with Microsoft products in whichever role they are certified in.
MCSD is evidence of "moderate* knowledge.
MCSE, Microsoft Certified Solutions Expert, is the expert certification.
Each of these levels is available for several different knowledge areas. Someone with an SQL Server MCSE may not be an expert in Azure, and vice versa.
So "I have a cert" doesn't mean much. *What level* cert do you have in which *knowledge area*? A SQL Server MCSE probably knows SQL Server pretty well. They may know nothing about Linux.
> . Don't go for the absolute cheapest solution, unless you're very comfortable with them and they have very strong references.
This in spades! The per-hour rate is negatively correlated with the total cost.
A low rate per hour means "I'm going to spend a lot of hours poking around trying to figure things out". Someone who knows their shit, who has seen this problem before and knows how to fix it correctly, can probably fix it in 15 minutes. They're going to charge for that 15 minutes. It's going to be a lot cheaper overall to have it fixed right the first time, and fixed quickly, than to have someone would "knows a lot about computers" mucking around screwing things up for three hours.
The footnote to that is that there are several service companies which contract the work to contracting companies, who then contract the work to people who can actually do the work. Those layers of companies make it expensive because you're paying middle men, not because you're getting experts. Years ago I was a "Hewlett Packard Fied Engineer". HP contracted TCML to do their field service calls. TCML then contracted people like me. They'd pay me $30/hour, TCML would charge HP $60/hour, and HP charged the customer $120/hour. Going through companies like that, you can easily pay $120/hour for a $30/hour tech.
So you want to find a tech who is good enough to fix it right ans fix it fast - and is therefore good enough to get well paid per-hour. Not to be confused with paying a company who pays another company who pays a cheap tech.
Variations on the idea will ALWAYS be present in any high performance SMT processor. CPUs are just so complicated and there are so many interactions that as long as there are simultaneous threads, one thread will be able to create resource contention with another.
A solution would be to have a very simple (slow) processor, probably an ARM chip, which handles cryptographic tasks. Complexity is very much the enemy of security, especially regarding the types of side channel attacks you mentioned.
Slashdot Mirror
The reason for choosing the closest server may merit more explanation. If you're on the west coast and you query a server on thr east coast, your accuracy suffers with every router and switch along that path, so you end up with some unknown offset from the NTP server's time. ISPs and geographically disperse companies don't have that problem. Here's why.
Comcast will have a DNS server / ntp server in Houston. It may have a GPS, tdma, or LTE reciever locally connected, but most importantly it peers with their servers I Miami, Denver, and San Jose. The one in Miami peers back with Houston - and Miami, PLUS San Jose and a tier 1. All of the Comcast NTP servers have to estimate the time sync, but *they all arrive at the same estimate*, because they peer with each other multilaterally. So they all end up with the same time, network time.
By getting your time from a nearby server that does mutual peering, you're getting network time from a server that is only a few milliseconds away, amd probably a *consistent* number of milliseconds, so ntp can make accurate estimates of delay.
I have good news and bad news for you.
The offset value we log isn't the actual difference between your clock and the peer clock, and the logged value is seconds, not milliseconds. If you see 0.08 in the log, that means we're *assuming* that you're about 0.08 *seconds* off from that peer.
If you ping a server "thousands of miles away", you'll notice each ping takes a different number of milliseconds. That difference in ping times, or jitter, is pretty much a hard limit on sync accuracy with the NTP protocol. If you get a response from a server thousands of miles away saying "it's exactly midnight", we don't know if that packet was generated 30ms ago or 35ms ago. So that loses 5ms of precision.
Back to your peerlog. The last four fields show the assumed offset, delay, dispersion and jitter (root mean square). Take delay, multiply by 0.25, then add the jitter, and that's roughly the accuracy you can expect. If you're using ntpclient, add the dispersion, as that's the dispersion of the server. If you're using ntpd, your dispersion value is arough estimate of your accuracy - in seconds.
The good news is, your ISP's DNS server and gateway are many milliseconds closer, and ine or both are probably NTP servers. You CAN get much more accurate time, you just need to use servers that are much, much network-closer to you, such as your ISP's DNS or gateway.
You can get time accurate to within about a thousand to a millionth of a second with PTP, using network time as your reference. That's the time standard used by thr vast majority of people, network time aka ntp time aka internet time, which is closely synced to GPS time.
So which time do you want to consider "correct" - the time used by 98% of the precision clocks, or the time used by one clock in Boulder?
NTP is super easy to use and pretty darn accurate as well. PTP is quite a bit more accurate, with microsecond synchronization within your network.
> only Nintendo can sell games in Nintendo 3DS eShop
And only you can sell stuff in Tepples' shop. So what?
You can sell Nintendo 3DS games in your store. Nintnedo can sell them in their store, and I can sell them in mine. Contrast Apple - ONLY Apple can sell iOS applications. Walmart cannot sell them.
> only Nintendo can manufacture Nintendo 3DS Game Cards on publishers' behalf for "Walmart, on Amazon, GameStop, EA.com" to sell.
False. You can even easily buy individual blank cards at retail and put your own game on them. Two popular brands are Gateway 3DS and Sky3DS.
My mom architected the software system that made Dell a major manufacturer. When you placed your order online, it would check whether all the parts were already in stock or if your build would wait a day for parts. It checked which other machines were being built and scheduled yours for optimal efficiency switch between orders. After scheduling your build, it gave the customer an expected ship date.
They replaced that system with "a cool new system" made by young people who "know" JavaScript, from copy-pasting Stackoverflow. Node.js is cool because it's newer, so it must be better.
Try using a modern certificate in an SSL server, such as Apache 1.2.
Some people mistakenly call it SSL. That doesn't make it SSL.
For example, you can call OpenVPN an SSL connection, but the fact is, it doesn't support SSL and it never has. It speaks TLS.
I wonder if you have any source for that, because everything I'm finding says otherwise, including Sprint's regulatory filing.
They may get some backhaul from AT&T, but that doesn't matter much to the users - the towers matter. Sprint's 3G service is CDMA, AT&T is GSM, so very obviously they aren't the same network - they aren't even the same TYPE of network.
For LTE, Sprint's legal filings compare their LTE network to AT&T's much larger network.
If you say gigawatt is more kilowatt, so the "plan" makes no sense, that's just because you hate nature and want everybody to die.
The audience for this stuff thinks about "should" and "want", not "how". How it's supposed to work is totally irrelevant, and doesn't even enter the minds of the people he's pandering to.
It's not that they actually think declaring / wishing something will make it magically happen like it does in the eco-cartoons. They don't think that saying "the government should give everyone free _____" will make stuff magically appear. It's that how, what the cost is, and unintended affects simply aren't relevant and never enter their mind. All that matters is what you want.
The headline is BS. It's the opposite of the announcement. Here's what the announcement actually said:
We had planned on getting to 50% by 2025, but our new target is 2035.
In other words, they announced that wind and solar are NOT. going to work out like they had previously said. By 2035 Macron will be long out of office and it will be somebody else's problem to explain why the new target is 2055.
I wouldn't know about who all makes / made cards for the Vita, but I know the major game companies ditched it a while back because few people use it.
In any event, the Vita hardly has a monopoly on handheld gaming, with the Nintendo 3DS series being far more popular, and phone / tablet Gam even more so. If Sony becomes the only company still trying to sell games for their failing handheld, who cares.
It's a phone plan that uses the networks of Sprint, T-Mobile, US Cellular, and selected wifi, with transparent handoff between them. Prices are good. You pay only for how much you use that month.
If you regularly use your phone to stream HD video all day, I haven't compared pricing for that use case. I have FiOS for internet and TV while I'm at home.
Yes, to get Sony's help, to have them believe you're actually a game company and not a crakz haxor, you need to have a company. That will cost about $250, you're right.
Compare with Apple, where you can only buy from Apple's store. With Apple, ONE company can sell apps, Apple. With Sony, ANY company can sell games.
"Any" is slightly more than "one".
> In reality, the https:/// part of the address (also called "Secure Sockets Layer" or SSL)
SSL was a protocol used by Netscape in the 1990s.
For ten last decade or two we've been using TLS.
The thing about opsec is you only have to screw up once. They tried getting the bad guy to connect without using a proxy, uaing the error message. The bad guy maintained opsec and didn't fall for it. So then they tried the next thing. If the bad guy didn't fall for that, the FBI would go to the next approach.
In your mind, the worst insult you can come up with is "homosexual recruiter"?
Your bigoted ideas went of fashion in the 1970s, bro.
The relevant docs can be found here:
https://partners.playstation.n...
They do not have a 30% royalty like Apple does.
If the case against Apple is won by the plaintiffs, someone could try to file suit against Sony, though they'd have a weaker case.
Sometimes Amazon's plans don't end well. They brought in the massage parlor to ensure the project has a happy ending.
You can buy PlayStation 4 games at Walmart, on Amazon, GameStop, EA.com etc. Sony does not have a monopoly on PS4 games.
Says someone who has clearly never achieved any significant certification.
Try memorizing your way through a CCIE. I'd love to see someone try the 8-hour CCIE lab based on memorization.
Let's say you got a CISSP by a) memorizing and b) deeply understanding roles. You still have 40 hours of CE to do every year to keep the cert.
"the U.S. Copyright Office will not register a government edict that has been issued by any state, local, or territorial government, including legislative enactments, judicial decision, administrative rulings, public ordinances, or similar types of official legal materials." U.S. Copyright Office Practices  313.6(C)(2)
Not it explicitly says judicial decisions can not be registered for copyright. Yes I'm aware Lexis Nexus doesn't like that.
Neither statutes nor court opinions are copyright Lexis Nexus or Westlaw.
What these companies have copyright on are:
Their formatting tags they add (copy-pasted text from them as plain text, unformatted, to avoid any problems).
The text of their notes about relevant cases, which they have selected and summarized.
So if Westlaw says this:
Subsection C was limited based on fair use considerations in Jones vs Smith (2012) regarding digital libraries.
You can NOT directly copy-paste that. You CAN write this:
See Jones vs Smith (2012)
Or this:
For fair use exceptions, see Jones v Smith
Or even put the entire text of the Jones v Smith ruling.
You just can't copy-pasted the exact words that LN or Westlaw wrote.
> Honestly is Bitcoin any worse than a portfolio that has biotech stocks?
Yes, Bitcoin is worse than a portfolio, period.
A portfolio of produce would be smarter.
I noticed someone replied poo-pooing certs. Every time I've talked to people who say that in order to understand their thinking, it comes down to "entry level certifications don't guarantee expert knowledge".
MTA and MCSA are explicitly entry-level certifications. They are evidence that the person has sufficient knowledge to BEGIN working with Microsoft products in whichever role they are certified in.
MCSD is evidence of "moderate* knowledge.
MCSE, Microsoft Certified Solutions Expert, is the expert certification.
Each of these levels is available for several different knowledge areas. Someone with an SQL Server MCSE may not be an expert in Azure, and vice versa.
So "I have a cert" doesn't mean much. *What level* cert do you have in which *knowledge area*? A SQL Server MCSE probably knows SQL Server pretty well. They may know nothing about Linux.
https://www.microsoft.com/en-u...
> . Don't go for the absolute cheapest solution, unless you're very comfortable with them and they have very strong references.
This in spades! The per-hour rate is negatively correlated with the total cost.
A low rate per hour means "I'm going to spend a lot of hours poking around trying to figure things out". Someone who knows their shit, who has seen this problem before and knows how to fix it correctly, can probably fix it in 15 minutes. They're going to charge for that 15 minutes. It's going to be a lot cheaper overall to have it fixed right the first time, and fixed quickly, than to have someone would "knows a lot about computers" mucking around screwing things up for three hours.
The footnote to that is that there are several service companies which contract the work to contracting companies, who then contract the work to people who can actually do the work. Those layers of companies make it expensive because you're paying middle men, not because you're getting experts. Years ago I was a "Hewlett Packard Fied Engineer". HP contracted TCML to do their field service calls. TCML then contracted people like me. They'd pay me $30/hour, TCML would charge HP $60/hour, and HP charged the customer $120/hour. Going through companies like that, you can easily pay $120/hour for a $30/hour tech.
So you want to find a tech who is good enough to fix it right ans fix it fast - and is therefore good enough to get well paid per-hour. Not to be confused with paying a company who pays another company who pays a cheap tech.
Variations on the idea will ALWAYS be present in any high performance SMT processor. CPUs are just so complicated and there are so many interactions that as long as there are simultaneous threads, one thread will be able to create resource contention with another.
A solution would be to have a very simple (slow) processor, probably an ARM chip, which handles cryptographic tasks. Complexity is very much the enemy of security, especially regarding the types of side channel attacks you mentioned.