unscaled

17 ms·

121.
by unscaled 2y ago
The cryptography discussed in the article is probably more aptly titled 1980s microcomputers-oriented cryptography. QText was first released in 1988. I'm not sure when they first added supported for passcode-protected files, but the ve
122.
by unscaled 2y ago
I assume the hard part would have been automating this or extracting the key derivation and check code out of QText so you can run it separately in a loop. I'm pretty sure you can automate DOSBox input, but if you're more comforta
123.
by unscaled 2y ago
While all of the languages you mention are memory safe (as is almost every programming language released after 1990), none of them solve all of the safety problems mentioned above, in particular, the two points: - Rust completely elimin
124.
by unscaled 2y ago
> Xml parsing has been hit twice in a week, avoid it in the future, anything wrong with a policy that replaces xml with json? OAuth 2.0 and its extension Open ID Connect have been around for over a decade. They have their own gotchas (li
125.
by unscaled 2y ago
SAML is not the only standard for SSO. Before SAML we had Kerberos and nowadays you can use Open ID Connect. Other standards can have their own gotcha, but SAML is uniquely horrendous. When we get vulnerabilities in the SSO protocol (SAML o
126.
by unscaled 2y ago
Auth0 is owned by Okta, not the other way around, and it used to be an independent company. I don't particularly like the way Auth0 works (like only supporting JWT for access tokens), but as far as I know they have not been impacted by
127.
by unscaled 2y ago
That is certainly one way to write Go, but I wouldn't call it "idiomatic" when evil the Google Best Practices guide recommends against it[1][2]. I'll wager you'll probably find it in most other Go style guides. This
128.
by unscaled 2y ago
To be fair, traditional Java EE apps often required a DI framework, because you couldn't control the main entry point of the program, and the entry point to your code was a class with a default no-argument constructor. This is still in
129.
by unscaled 2y ago
Too many people confuse the concept of DI with a DI framework. You don't even need a DI framework to write straightforward programs in Java. After all, Java also has interfaces! One of the reason people needed a DI framework in Java is
130.
by unscaled 2y ago
I think most of the tools on the second line are not highly applicable to a Kubernetes operator, or otherwise would just use the "Cloud Native way of doing things". Something like JRebel would generally be a big no-no for Kubernet
131.
by unscaled 2y ago
I think we can sum it this way. The blog post writer's intuition was correct: if you write two equivalent Go and and JVM programs, the Go program would use less heap memory and have faster startup times. What they are incorrect about i
132.
by unscaled 2y ago
And the "Worse is Better" follows some good design principles, but in a very twisted way: the program is designed to minimize the effort the programmer needs to write it. Implementation simplicity meant one important thing: Unix c
133.
by unscaled 2y ago
Most programming languages written after 1990 let you initialize global variables lazily. The main problem is that the initialization order might be unexpected or you may run into conflicts. Singletons make the order slightly more predictab
134.
by unscaled 2y ago
Sure, even RSA can be used safely. This site's root certificate is still 4096-bit RSA, and that's probably OK (if we trust Let's Encrypt and our TLS implementations). If what your library exposed was a function called validat
135.
by unscaled 2y ago
I think this chapter just proves GP's point, rather than refuting it. It's much cleaner than the Wikipedia article and it mentions the zero share problem, but it doesn't mention any other concern like constant time implementa
136.
by unscaled 2y ago
Case in point: http://sbudella.altervista.org/blog/20230330-shamir-timing.h... I think that specific attack is pretty hard to pull off pratice (in normal scenarios, Vault secret unseals do not happen very often). But i
137.
by unscaled 2y ago
The sad truth is that even libsodium can be misused (and the article explicitly mentions that twice). Even pretty high-level constructions like libsodium's crypto_secretbox can be misused, and most of the constructs that libsodium expo
138.
by unscaled 2y ago
It looks like FAPI 2.0 has finally been released in December, and thankfully it killed off most of the excesses of FAPI 1.0 and is better aligned with OAuth 2.0. At this point the main differences are: 1. PAR: A good idea that should become
139.
by unscaled 2y ago
Hopefully, when OAuth 2.1 is released, OpenID Connect will be updated to be based on OAuth 2.1. This would make some of the useful advice in FAPI (like PKCE) mandatory. A lot of the FAPI stuff that is not included in OAuth 2.1 or the OAuth
140.
by unscaled 2y ago
The other JVM distributions are a drop-in replacement for Oracle. It seems like most big customers that aren't still running old versions of Java have already moved away from Oracle to different distributions. But Oracle is still exclu
141.
by unscaled 2y ago
Open ID Connect is not OAuth. It is not done as part of the IETF, and the OpenID Foundation seems to have slightly lower standards for specs. For instance, specs can be updated with errata sets that go as far as as introducing significant c
142.
by unscaled 2y ago
The rationale for Dependency Injection was never _just_ about "making testing static methods" easier. In fact, Dependency injection was never about static methods at all. No DI advocate — not even the radical Uncle Bob — will tell
143.
by unscaled 2y ago
There's also no official x64, x86-64 or i686 "architecture", if we want to be pedantic. There is no official name for the 64-bit instruction set for the x86 architecture, as far as I know. As far as I remember, AMD called thi
144.
by unscaled 2y ago
And COM/OLE/ActiveX components (whatever Microsoft fancied calling them that year) could have been used just as easily from Delphi. And you don't even need COM. You could do the same things today with RAD components in, say,
145.
by unscaled 2y ago
I agree with your conclusion, but when you say "VB is totally fine" do you mean VB6? I can get Modern iterations of Visual Basic such as VB.Net. The syntax and semantics hurt my eye and my brain, but if that's your thing, yea
146.
by unscaled 2y ago
FreePascal/Delphi and VB6 are entirely different beasts. For one, FreePascal and Delphi are still under development. Delphi had the following language features added since 1998 (this is just a small selection): Extension methods/p
147.
by unscaled 2y ago
Merging the concepts of arrays and maps was very popular in the 1980s and 1990s. I can count at least Awk, Tcl, Lua, JavaScript and PHP as languages that went with this approach. Looking from today's perspective, I also fail to see the
148.
by unscaled 2y ago
Lua is definitely not underrated as an embedded Language. It is the uncontested winner of this field. If anything, I feel it is slightly overrated: it is easy to embed, but has no other real strength. Everything else feels about Lua feels a
149.
by unscaled 2y ago
> There's also a possibly related matter, in how Sony stopped talking with them. Is it possible that Sony and/or Japanese government aren't very happy to learn that a possibly unique museum piece, of one of the heights of
150.
by unscaled 2y ago
This study only compared camelCase to snake_case and what the results are mixed, depends on what you call "hard to read". They only seem to have tested finding identifiers from a word cloud, and it did take more time to read camel

More ›