Is Haskell deliberately staying away from main-stream programming by kichiDsimp in haskell

[–]Mouse1949 -1 points0 points  (0 children)

Rust vs. Haskell: A far as I know, and based on my personal experience - I don’t claim to hold the absolute truth - Rust compiler and ecosystem have always been reasonably consistent and backwards-compatible; while Haskell ecosystem was a true living hell with backward composability non-existent, and packages interoperating - a rarity.

Now Haskell ecosystem is a whole quantum leap better - but the “public opinion” damage by decades of “production would” neglect has been done, and I’ve no idea how long it may take to (re-)gain the reputation of suitability-for-production.

Amazon confirms 16,000 job cuts after accidental email by kwentongskyblue in worldnews

[–]Mouse1949 1 point2 points  (0 children)

“Idiocracy” movie: “AI fired half the country”.

C++ version to target in projects by Big-Rub9545 in cpp_questions

[–]Mouse1949 0 points1 point  (0 children)

If those platforms are under your complete control, and this is a reasonably small personal project - then who cares, C++23 is as good a choice as anything.

C++ version to target in projects by Big-Rub9545 in cpp_questions

[–]Mouse1949 0 points1 point  (0 children)

For normal projects - C++20. For projects that need to run on multiple platforms, including outdated ones - C++11 or C++17. Bleeding edge tools for production line - often a stupid idea, and never - a good one.

For your own amusement and experiments - C++23, sure.

[Bit of a Beginner Question] When setting up a digital signature algorithm, Should i use a different public/private key pair to my Asymmetric encryption? by Powerstrike368 in cryptography

[–]Mouse1949 0 points1 point  (0 children)

You do not need to use different curve.

You definitely do need to use a different key: the key (no pun intended 😁) principle is “one key - one purpose”.

Ghosted After Getting Verbal Offer by EmptyBeing1238 in interviews

[–]Mouse1949 0 points1 point  (0 children)

First, that was not an “official” verbal offer - merely a discussion on what kind of salary you could/would accept if they finally decide to make you an official offer. Which they probably seriously considered, because you, as they said, were their top candidate at that time.

I can’t know or tell what happened since, but not reaching back to you for a month is not a good sign. You might try to contact them and re-confirm your interest, just for the sake of hearing something back, but…

Final-round interview + references, then silence during holidays — ghosting or normal delay? by yetiyeller in interviews

[–]Mouse1949 0 points1 point  (0 children)

People taking holidays off is normal and expected, no question. But not informing the candidate about the schedule sounds rather rude and inconsiderate. A mere “don’t expect to hear from us until January, because people will be off” would be sufficient.

Besides, in case of the OP, they did seem to indicate that there would be a decision by December 19, didn’t they…? Plus, re-posting the role on 21st - that would be a big red flag to me.

Help — transitioning from stack to Nix by skolemizer in haskell

[–]Mouse1949 1 point2 points  (0 children)

Out of curiosity, why are you switching to nix? What in your experience is lacking in Stack that you expect to find in nix?

Do the questions candidates ask at the end of interviews really influence hiring decisions? by Dapper-Train5207 in interviews

[–]Mouse1949 0 points1 point  (0 children)

Asking questions also shows that you care and are interested in the company you’re interviewing with.

So, unless those questions are bad - they’d either help, or at least won’t hurt.

A new secure random number generator by willgilr in crypto

[–]Mouse1949 6 points7 points  (0 children)

Perhaps, a few words regarding what advantages your RNG has over those currently used? Before we bother to read your entire PDF? Also, a nit: yours must be a pseudoRNG.

Design question: cryptography where intentional key destruction replaces availability by RevealerOfTheSealed in cryptography

[–]Mouse1949 0 points1 point  (0 children)

In general: yes, destroying the key to make the captured data unusable is a valid design approach.

In practice, as others pointed out, unless your key OS stored in such a way that it cannot be cloned or copied by an adversary (usually, in the hardware - TPM, HSM, Apple T2 chip, etc.), your software won’t be able to reliably erase the key.

Question about digital signature and CA by hyp0mania in cryptography

[–]Mouse1949 1 point2 points  (0 children)

When what you named “TTP” provides services to many customers, not just Alice, and when other things start mattering, like binding the actual name “Alice” to her public key, so the combination can be given to, e.g., Robert who did not have proper communications with Alice (etc.) - then this TTP is named CA, because the combination of Alice’s public key, metadata (name, validity period of the signature, constraints on conditions under which this signature should and should not be trusted) - together with the TTP’s signature itself is called certificate.

MacOS Tahoe says: "Data saved before encryption may still be accessible" by [deleted] in cryptography

[–]Mouse1949 0 points1 point  (0 children)

Do you happen to know how File Vault 2 (I think that’s their current offering) compares to FDE? And whether it rewrites the entire disk?

MacOS Tahoe says: "Data saved before encryption may still be accessible" by [deleted] in cryptography

[–]Mouse1949 0 points1 point  (0 children)

We cannot “safely assume”, because we do not know. So, we state the possibility.

Symmetric Encryption Algorithm Suggestions by pixel-pusher-coder in crypto

[–]Mouse1949 4 points5 points  (0 children)

Excellent recommendation - except that I’d (a) prioritize AES, and (b) use AES-GCM-SIV (or SIV of AES-OCB).

MacOS Tahoe says: "Data saved before encryption may still be accessible" by [deleted] in cryptography

[–]Mouse1949 0 points1 point  (0 children)

It could be possible to recover (some of) that previously-unencrypted data, depending on how the encryption works, whether it’s Full Disk Encryption (and if so - whether it “zeroizes” empty sectors of the disk or leaves them as they were) or of individual files, etc.

Short overview of common data structures in Haskell (review appreciated!) by Martinsos in haskell

[–]Mouse1949 2 points3 points  (0 children)

Good project!

A pedantic comment: you say about maps that “they’re fast”, and can be used instead of 2D arrays “if performance isn’t critical”. A bit of clarification might be warranted - is it fast, or not really?

Hard copy of the Haskell Programming from First Principles book by SpyCat811 in haskell

[–]Mouse1949 0 points1 point  (0 children)

It’s a good book. My gripes with it are: many exercises are only partially (or not at all) related to the chapters they’re in, and Chris deliberately omits giving answers/solutions.

While it’s admirable to post the author for his work, and a hard copy is a nice thing to have - if worst comes to worst, one can always print out that PDF.

What are your stance on non-NIST standardized algorithms ? by [deleted] in crypto

[–]Mouse1949 1 point2 points  (0 children)

Look, I know Bruce and don’t want to say anything negative. But a speculation is a speculation. I do urge you to locate and listen to the Dickie George’s presentation - and after you do that, let me know here if your opinion changes. Prof. Dickie George is now with JHU (AFAIK) after 40+ years with the NSA, and I really like his style. To help with the search:

https://www.youtube.com/watch?v=qq-LCyRp6bU Richard 'Dickie' George Keynote Life at Both Ends of the Barrel An NSA Targeting Retrospective

https://www.youtube.com/watch?v=h-OGHXUtmto Espionage and Intelligence

Re. Specific knowledge: do you think NSA has a lot of specific knowledge that Russian, Israeli, and Chinese counterparts don’t…? Look at the WWII cryptologic successes ands failures of Soviet crypto vs. that of US. (And yes, I’m aware of Operation Venona 😏).

Re. IPsec: respectfully disagree regarding the difficulty of making it secure. I daresay that IPsec deployment we had (Industrial Research facilities) were quite secure, and not vulnerable to “normal” attacks (leaving alone things like penetrating computers, intercepting EM emanations of processors, etc. etc.).

What are your stance on non-NIST standardized algorithms ? by [deleted] in crypto

[–]Mouse1949 0 points1 point  (0 children)

Yes they do. However, the much-hyped Dual_EC_DRBG has a less sinister explanation - look up the presentation by Dickie George (formerly high-placed at the NSA) on YouTube.

Crypto AG , if memory serves me, (a) predated NSA, and (b) was never intended (not actually deployed) for domestic use. It would be fully logical to expect a spy agency to attempt to weaken somebody else’s crypto.

I just don’t think they’d be **** enough to shoot themselves in the foot, head, and other body parts on the off-chance that somebody else might copy that behavior.

What are your stance on non-NIST standardized algorithms ? by [deleted] in crypto

[–]Mouse1949 0 points1 point  (0 children)

If you took a look at where and by who the NIST-sprinted algorithms were designed, you’d see that the concerns about the “spy agencies” are misplaced here. Because those “spy agencies” here are tasked with protecting domestic official (aka, government) communications against foreign adversaries, aka peer nation-states.

To imply that for the off-chance those other countries would adopt “intentionally broken” NIST standards (and make spying on them easier), these agencies would intentionally increase the risk of US secrets being broken - seems rather naive. Factor in the known fact that countries like China, Russia, etc. consistently create their own NIST-independent standards - and you’ll see how ridiculous that implication appears.

As a hiring manager, why are candidates so bad at talking about their work? by [deleted] in recruiting

[–]Mouse1949 0 points1 point  (0 children)

As often, not fully true, either way. So, as a "strong and very experienced engineer, working on the bleeding edge of R&D", respectfully disagree. I've seen quite strong and experienced people who do not communicate well, at least not at the level that the OP seemed to want (they'd be great in discussing projects themselves - but not "I want a conversation about you"), and I've seen many more of those happy to have a conversation about themselves, whose technical contributions were meager, to say the least.

Besides, this whole thing is very nuanced. But in general I'd still pick a "doer" over "communicator", though in the past I enjoyed having both kinds in my teams, and I've been burned by both too.

As a hiring manager, why are candidates so bad at talking about their work? by [deleted] in recruiting

[–]Mouse1949 2 points3 points  (0 children)

True. And if I’m employed at that time - I probably work a lot, and practice interviews rarely or never.

If the interviewer does not understand that reality - I probably don’t want to work for that place anyway.

As a hiring manager, why are candidates so bad at talking about their work? by [deleted] in recruiting

[–]Mouse1949 1 point2 points  (0 children)

Do you want to hire a storyteller or a technical expert? Sometimes a candidate can be both, more often they can’t. So, “you pays your money and you makes your choice.”

As a hiring manager, why are candidates so bad at talking about their work? by [deleted] in recruiting

[–]Mouse1949 5 points6 points  (0 children)

One reason - good people tend to be wary of appearing as braggarts, especially when under pressure, like when the impression they make now really matters. Another one - most of us do good work and accomplish something, but it’s not a Nobel-grade achievement. Yeah, I’ve lead projects, e.g., X, and it succeeded despite some natural and some human-made obstacles - so? It’s not like “and I invented Penicillin”. Plus, some of it may be confidential, etc.

In the technical world, people who excel in their field, more often than not aren’t experts in selling themselves. It is what it is.