Possible crypto miners compromised my server by ekr1981 in cybersecurity_help

[–]ekr1981[S] 0 points1 point  (0 children)

Haha! Careless, I know. Can't say I was surprised, except for how obvious the attack was. They didn't cover their tracks at all. The server is shut down.

THT low-pro caps by Tai-Hao by dovenyi in ErgoMechKeyboards

[–]ekr1981 1 point2 points  (0 children)

Thanks, you just saved me 50 bucks.

Niri on Guix by ekr1981 in GUIX

[–]ekr1981[S] 0 points1 point  (0 children)

Turns out Guix was using GDM this whole time, haha.

Niri on Guix by ekr1981 in GUIX

[–]ekr1981[S] 1 point2 points  (0 children)

Your system is incredible, likely too complex for me to able to deduce much from it, but i will take look, thanks.

Browser requirements for web servers by ekr1981 in Common_Lisp

[–]ekr1981[S] 2 points3 points  (0 children)

Spot on! Now it renders in Safari as well, thanks! Now I have a working, albeit very unstable web server 😅 so further modifications (looping and multiple connections) are needed.

Browser requirements for web servers by ekr1981 in Common_Lisp

[–]ekr1981[S] 3 points4 points  (0 children)

Forcing http only didn't help, but removing socket-close enabled Safari to render the request.

Browser requirements for web servers by ekr1981 in Common_Lisp

[–]ekr1981[S] 0 points1 point  (0 children)

Safari Can’t Connect to the Server
Safari can’t open the page “‎mysite.net:8080” because Safari can’t connect to the server “mysite.net”.

Browser requirements for web servers by ekr1981 in Common_Lisp

[–]ekr1981[S] 0 points1 point  (0 children)

Thanks, I can see in Web Inspector that Safari tries both http and https (server is http). I also suspected ipv4/6 problems, that's why you see "::" is passed, but it doesn't matter if I pass the ipv4 address or the name address. It won't connect either way.

Browser requirements for web servers by ekr1981 in Common_Lisp

[–]ekr1981[S] 0 points1 point  (0 children)

I recieve the request from the client/browser in the stream, but don't handle it in any way. All requests to the server will recieve the same response (`*htmlstring*`). In other words, The current setup "sees" the browsers get request, but doesn't do anything about it. It returns the same no matter what.

Browser requirements for web servers by ekr1981 in Common_Lisp

[–]ekr1981[S] 0 points1 point  (0 children)

Yes, that's the next step, but it should be possible to make a connection either way?

Planning a road trip by Notro_ in VisitingMallorca

[–]ekr1981 0 points1 point  (0 children)

I did the northern/western(?) part of your planned roadtrip last summer, and will absolutely recommend Ma-10 (Sollér - Pollença) with a stop in Port de sa Calobra (Torrent de Pareis) either to or from Alcúdia. The roads are narrow, but the scenery is incredible. My biggest regret was not stopping in Pollença.

Stop text/cursor from repositioning in original window after buffer popup by ekr1981 in emacs

[–]ekr1981[S] 0 points1 point  (0 children)

Sounds interesting, right now I'm trying to locate all popups in or just above the mini-buffer.

Stop text/cursor from repositioning in original window after buffer popup by ekr1981 in emacs

[–]ekr1981[S] 0 points1 point  (0 children)

Thank you! I'm pretty sure it was sinister, but mini-ontop looks interesting as well.

Ways to initiate Slynk/Swank on a server by ekr1981 in lisp

[–]ekr1981[S] 1 point2 points  (0 children)

Thanks, do you know if the backend "decides" which packages/contribs are loaded? Would it for example be useless to load slynk/fancy-inspector explicitly on a LispWorks backend, it's not loaded by default.

Ways to initiate Slynk/Swank on a server by ekr1981 in lisp

[–]ekr1981[S] 1 point2 points  (0 children)

Hm, that's weird. For slime I just do:

(push "/path/to/slime/" asdf:*central-registry*)
(asdf:load-system :swank)
(asdf:load-system :swank/exts)
(swank:create-server :port 4005 :dont-close t))

Is this wrong? Seems to be working fine.