dsp1234 · HackerTrans

> language injection where you write code and later on you inject a different language.

I (still) work with a Classic ASP code base.

I kid you not, that there are VBScript functions, which call JScript (not JavaScript) functions, which in turn call VBScript functions.

It is a terrifying and glorious mess.

edit:

I also worked with a system at one time that used node.js to create C# files on the file system, then use the C# compiler to create an executable and then run it. It was... not great.

dsp1234

7년 전discuss

The blog post is buried a bit deep, but has the actual technical information on the topic

https://www.cyberus-technology.de/posts/2019-05-14-zombieloa...

dsp1234

7년 전discuss

This isn't all on the non-developers. I've walked into two rooms this week, which contained several senior developers, and when I asked them about non-functional requirements, they had to ask what they were, and why they were important.

I've also seen teams where the Defintion of Done doesn't include any steps at all towards deployment. Done is when someone approves the pull request.

Not surprisingly, it takes longer for those teams to 'complete' a change. In the former case, they are continuously surprised, and angered, by 'requirements' that 'no one' told them about. In the later, they stop halfway, and wonder why everyone is waiting on them, because it's 'development complete'.

dsp1234

7년 전discuss

> The difference between China and Russia is 77x.

The population of Russia is ~146.7M [0]

The population of China is ~1,403M (~1.4B) [1]

This makes China ~9.6 times larger than Russia.

The US is ~327M [2], which makes China about ~4.3 times as large.

It's a big difference, but not as large as 77x.

[0] - https://en.wikipedia.org/wiki/Russia

[1] - https://en.wikipedia.org/wiki/China

[2] - https://en.wikipedia.org/wiki/United_States

dsp1234

8년 전discuss

Per that study, "This analysis of 5-y weight-loss maintenance indicates, on average, that obese individuals maintained weight losses of 3.0 kg, representing a reduced weight of 3.2% below initial body weight. These individuals were successfully maintaining a weightloss averaging 23.4% of their initial weight loss at 5y"

Put another way, after 5 years, the average weight loss was ~3kg, with an average weight gain of 78.6% of the original lost weight.

Also, in general, an obese person who is obese before, and after 5 years has a weight that is ~3kg is likely still obese.

So this study basically just says that an average person isn't successful at keeping a large amount of weight, and gains most of it back. The specific statistics stated by the commenter above may not be correct, but the sentiment is definitely true.

That said, the study does confirm that very low energy diets (~800 meal replacement) beat out hypoenergetic balanced diet (~1200-1500 normal food) in long term weight maintence. Which is what the article is suggesting being implemented. So it's still not a great long term solution, but it's the better of the two non-exercise based solutions which this study evaluated.

dsp1234

8년 전discuss

The closing price on Thursday was $168.84. The close yesterday was $162.44. That's a 3.8% decline.

I'm not sure where you got the $219 price from, but the stock price was nowhere near that before the breach.

dsp1234

8년 전discuss

The load could be zero, it could be infinite, or anywhere in between. Infinite universes sending infinite work is inf/inf. It's not possible to know if that's going to tend towards something like 0 or something like positive infinity without having some way to measure. But it's an error to just assume it's zero.

dsp1234

8년 전discuss

There are several layers where a registrar has control over DNS resolution.

Terms:

ICANN: The organization responsible for coordinating the maintenance of the domain name system (among other things).

Registrar: A company authorized to update ICANN database on behalf of registrants. Google, GoDadddy, Enom, etc are registrars

Registrants: An entity that wants to register a domain name. In this case, Zoho is a registrant, but it could also be an individual. This is your role if you 'own' a domain.

Authoritative Name Server: A domain name server that is considered authoritative for a specific domain.

Stuff registrars can do (among other things):

1.) They can update the ICANN database to disable a domain completely[1]

2.) They can replace your authoritative name servers with their own or someone else's (ex: botnet domains being reassigned to a security company for dismantling via court order)[2]

3.) If the authoritative name servers for a domain are owned by the registrar, then the registrar can merely change the DNS entries themselves to point to something other than the domain owner's wishes.

[0] - https://en.wikipedia.org/wiki/ICANN

[1] - https://www.icann.org/resources/pages/epp-status-codes-2014-...

[2] - https://www.icann.org/en/system/files/files/guidance-domain-...

dsp1234

8년 전discuss

From the GetItem docs[0]

"GetItem provides an eventually consistent read by default."

This seems to meet the definition of "DynamoDB's default settings"

[0] - https://docs.aws.amazon.com/amazondynamodb/latest/APIReferen...

dsp1234

8년 전discuss

users should never have assumed it would be stable in the first place.

It's not an assumption. It's directly in the documentation.

"If the same seed is used for separate Random objects, they will generate the same series of random numbers."[0]

[0] - https://docs.microsoft.com/en-us/dotnet/api/system.random

dsp1234

8년 전discuss

There appears to be an on premesis version, which doesn't use AWS services.

https://www.datomic.com/on-prem.html

dsp1234

8년 전discuss

The spec sheet at [0] claims:

Hydrogen storage is "Approx. 5.0 kg"

122.4L of volume (60L front, 62.4L rear)

pressure is between 70 MPa and 87.5MPa

Doing the math shows:

density of hydrogen at 70MPa equals 36.69 g/L [1]

122.4L at 36.69 g/L equals 4.49kg [2]

density of hydrogen at 87.5MPa equals 45.96 g/L [3]

122.4L at 45.96 g/L equals equals 5.63kg [4]

So the amount is somewhere between 4.5kg and 5.63kg, depending upon the final pressure after filling. Which seems to line up squarely with "Approx. 5.0kg".

[0] - https://pressroom.toyota.com/releases/2016+toyota+mirai+fuel...

[1] - http://www.wolframalpha.com/input/?i=density+of+hydrogen+at+...

[2] - http://www.wolframalpha.com/input/?i=122.4L+at+36.69+grams%2...

[3] - http://www.wolframalpha.com/input/?i=density+of+hydrogen+at+...

[4] - http://www.wolframalpha.com/input/?i=122.4L+at+45.96+g%2FL

dsp1234

8년 전discuss

Note that the beginning of the article quickly mentions the new attack that doesn't require the 4-way handshake. Then the rest of the article describes the 4-way handshake attack.

Here is the source for information on the attack that only requires a single EAPOL frame[0].

"This attack was discovered accidentally while looking for new ways to attack the new WPA3 security standard. WPA3 will be much harder to attack because of its modern key establishment protocol called "Simultaneous Authentication of Equals" (SAE).

The main difference from existing attacks is that in this attack, capture of a full EAPOL 4-way handshake is not required. The new attack is performed on the RSN IE (Robust Security Network Information Element) of a single EAPOL frame.

At this time, we do not know for which vendors or for how many routers this technique will work, but we think it will work against all 802.11i/p/q/r networks with roaming functions enabled (most modern routers).

The main advantages of this attack are as follow: No more regular users required - because the attacker directly communicates with the AP (aka "client-less" attack) No more waiting for a complete 4-way handshake between the regular user and the AP No more eventual retransmissions of EAPOL frames (which can lead to uncrackable results) No more eventual invalid passwords sent by the regular user No more lost EAPOL frames when the regular user or the AP is too far away from the attacker No more fixing of nonce and replaycounter values required (resulting in slightly higher speeds)" [0]

[0] - https://hashcat.net/forum/thread-7717.html

dsp1234

8년 전discuss

Party A records every interaction with Party B. Party B records every interaction with Party A.

Who owns what Party A recorded, and who owns what Party B recorded?

dsp1234

8년 전discuss

If I write down every song that I play through Spotify for a year. Does Spotify own that?

dsp1234

8년 전discuss

Want a debugger? Nope.

https://www.markheath.net/post/remote-debugging-azure-functi...

dsp1234

8년 전discuss

What makes you say this?

About half of nearby stars that we can observe[0] have planetary make up that is different than our own Sun. By definition, the rest either have a make up that is like our own or not like our own. So let's assume that every single nearby solar system looks exactly like our solar system, we are just unable to detect that they are at this time. That still means that our solar system is distinctly different than half of the other solar systems. That ratio of difference will never go lower, it'll always be "The solar system is different than at least 50% of other nearby solar systems". But after we do more observations, it might be 60%, 70%, 80%, etc.

Or in other words, as the original commenter said, "It is certainly possible that the more we study the rarer it will become. (It can't really go the other direction at this point.)".

[0] - FTA, "Of order half of nearby stars have at least one (and often several) worlds with masses substantially greater than Earth and orbital periods ranging from mere days to weeks; in our system, the space interior to tiny Mercury’s 88-day orbit is entirely empty."

dsp1234

10년 전discuss

shouldn't you have "transactions", "transaction_senders", and "transaction_receivers"

were doing the right way(TM), that wouldn't happen

Having a separate transaction_senders and transaction_receivers wouldn't be the right way(TM) unless it's possible to have multiple senders/receivers. If a transaction can only have 1 sender/receiver then normalization is complete when the sender/receiver data is removed from 'transactions' table and replaced with the sender_id and receiver_id columns.

When introducing transaction_senders/transaction_receivers tables without further constraints, it would be immediately possible to have multiple transaction senders and multiple transaction receivers for a single transaction, which is likely an error.

dsp1234

10년 전discuss

subject to self-joins and other query approaches

Which means that the original argument about reserveration_id vs id doesn't matter since it's likely that both table and column aliases would be needed anyways.

dsp1234

10년 전discuss

Not that I think it effects your point, but just off the top of my head:

System clock will take a larger step than usual. It won't go backwards.

Assumes that checkpoint and restore to a previous time won't happen.

NTP only drifts the clock (under normal operation).

Unless it's a system like this. Note that this was pulled at about 1pm EST.

  Waiting for clock tick...
  ...got clock tick
  Time read from Hardware Clock: 2016/02/09 22:36:50
  Hw clock time : 2016/02/09 22:36:50 = 1455057410 seconds since 1969
  Tue 09 Feb 2016 02:36:50 PM PST  -1.038948 seconds

Under normal operation it will only move forward

'Under normal operation' is not really a high bar for distributed systems. After all, the network is reliable 'under normal operation' too.

comments