HN user

kevinoid

305 karma

Email: kevin@kevinlocke.name

Website: https://kevinlocke.name

GitHub: https://github.com/kevinoid

GitLab: https://gitlab.com/kevinoid

Posts0
Comments75
View on HN
No posts found.

A significant effect is through opioid receptor activation, as demonstrated by Williams et al. <https://doi.org/10.1038/s41380-019-0503-4> by blocking the receptor with naltrexone, which attenuated the antisuicidality effects.

The Huberman Lab episode Ketamine: Benefits and Risks for Depression, PTSD & Neuroplasticity <https://www.hubermanlab.com/episode/ketamine-benefits-and-ri...> and the referenced journal articles (including the above) have a lot of detail on it.

Location: Bozeman, MT

Remote: Yes

Willing to relocate: No

Technologies: C#, Python, Node.js, MSSQL, ASP.NET WebForms, ASP.NET Core, JavaScript, OpenAPI, Selenium, REST, XML, XSLT, Git, Docker, Ansible, Debian, Bash, POSIX Shell, and many others.

Résumé/CV: https://kevinlocke.name/resume

Email: kevin@kevinlocke.name

Hi, I'm Kevin. I'm a generalist senior software engineer and consultant with over a decade of experience with a broad range of technologies, roles, and industries. I graduated magna cum laude with a B.S. in C.S. from Cornell, co-founded Digital Engine Software in 2009, joined early-stage fintech startup Quantpost in 2013, and have been developing and consulting independently since 2016 for a variety of clients, particularly in home health care and construction. Recently I've worked on many backend web sites and services (ASP.NET+MSSQL and MEAN Stack), automation, integration, and synchronization (Selenium+C#, Python, PowerShell), and Linux DevOps (Docker, Ansible, Bash) projects, but I particularly enjoy lower-level embedded and systems programming. I'm a free and open-source software proponent and contributor. I'm looking forward to joining a team doing meaningful work, particularly toward a social good, contributing my expertise, and learning and collaborating with other professionals.

Perhaps this is a good time to ask: I'd like to use UEFI for my qemu+libvirt virtual machines, but I need snapshot support. Since QEMU doesn't support pflash internal snapshots <https://gitlab.com/libvirt/libvirt/-/commit/9e2465834f4bff40...> and libvirt can't revert or delete external snapshots <https://bugzilla.redhat.com/show_bug.cgi?id=1519002>, I don't see a way to achieve this. The issue was discussed on virt-tools in 2017 <https://listman.redhat.com/archives/virt-tools-list/2017-Sep...> and the situation appears to be unchanged. Do others have a workable solution?

Interesting. If I understand correctly, the "bypass" is https://github.com/coofcookie/Windows11Upgrade/blob/1.0.0/Wi... which is a copy of https://github.com/AveYo/MediaCreationTool.bat/blob/main/MCT... which appears to be intentionally cryptic.

It sets HKLM\SYSTEM\Setup\MoSetup\AllowUpgradesWithUnsupportedTPMOrCPU=1 which is mentioned by Microsoft in https://support.microsoft.com/windows/ways-to-install-window... which seems reasonable.

According to the comment, the rest of the script "uses IFEO to attach to Virtual Disk Service Loader process running during setup, then erases appraiserres.dll [...] it must also do some ping-pong renaming of vdsldr in system32\11" Could anyone explain this in more detail?

Also note, according to https://github.com/AveYo/MediaCreationTool.bat/issues/11 it skips the CPU and TPM checks, but not the Secure Boot checks.

I've been running with ssh-rsa disabled for a while (with a config based on https://infosec.mozilla.org/guidelines/openssh#modern-openss... ) and it's been pretty smooth. Support for better algorithms is widespread, with a few exceptions (like bazaar.launchpad.net).

One gotcha: OpenWrt does not enable ECDSA by default[1] and only recently enabled support for ed25519 by default.[2][3] It's available in release candidates for 21.02, but not in current stable releases. So if you're running a stable release you'll need to either add `PubkeyAcceptedKeyTypes +ssh-rsa` to your client ssh_config or use a custom build of OpenWrt with DROPBEAR_ECC or DROPBEAR_ECC_FULL enabled.

[1] https://bugs.openwrt.org/index.php?do=details&task_id=786

[2] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=d0...

[3] https://bugs.openwrt.org/index.php?do=details&task_id=3216&s...

[4] https://bugs.openwrt.org/index.php?do=details&task_id=3452

I agree. As with many things, it's only simple as long as you ignore the complexities. As they say, the devil's in the details.

this "server" only responds to a simple well formed GET request.

And not even that. The Request-URI in a Simple-Request line (inherited from HTTP/0.9) may contain escape characters. (e.g. `GET /my%20file.txt` to get `my file.txt`) HTTP/1.0 states "The origin server must decode the Request-URI in order to properly interpret the request."[1] This server does not.

Which is not to say that this server isn't interesting. Just that it's not a demonstration of how easy HTTP/1 is to parse.

[1] https://www.w3.org/Protocols/HTTP/1.0/spec.html#Request-URI

You can read about the specific reasons that driver versions were blocked on the Mozilla Wiki https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drive... Most are due to the drivers causing crashes or security issues in Firefox.

I think a broader answer to your question is that most apps accept that if a driver causes a crash or security problem, it's not their problem and it's up to the user (and driver developer) to remediate it. Firefox has chosen to attempt software fallback to avoid the issues. There are obviously many trade-offs for good and ill with this approach.

I ran into similar issues with driver blocklists on both Linux and Windows. There are workarounds, such as setting MOZ_GFX_SPOOF_* environment variables, but even the suggestions on the Mozilla Wiki at https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drive... no longer work, because the spoofed driver version (8.15.10.2302) was blocked in https://bugzilla.mozilla.org/843273 It's a mess.

I can understand the desire to avoid using drivers which cause a poor user experience. I don't envy the task of trying to implement and maintain a system to achieve that. I do wish it wasn't so painful and confusing for users when the behavior doesn't match our expectations.

Since both the video and Shutup10 cover lots of different settings, I'm guessing you are referring to sending "activity history"[1] to Microsoft specifically? Was disabling it via Settings[2] not sufficient? Is there another registry change that is required? Or was DNS filtering the only solution you found workable?

[1] https://support.microsoft.com/kb/4468227

[2] https://www.tenforums.com/tutorials/100341-enable-disable-co...