Then there are the cases where you want the LLM to actually interact with the page, using the current web page state and your credentials.
For example, one might want to tell it to uncheck all the “opt in” checkboxes in the page… And express this task in plain English language.
Many useful interactive agent tasks could be achieved with this. The chatbot would be merely the first step.
Maybe consider static ip assignment in your DHCP server (e.g. internet router) if at all possible… Then you can add a name to it to /etc/hosts.
Alternatively you could use Avahi to provide mdns names to your local network
Do you have that file? If not, then unset SSH_AUTH_SOCK will work just as well.
If it does exist, then I suppose it has good chances of working correctly :). ssh-add -l will try to use that socket and list your keys in the service (or list nothing if there are no keys, but it would still work without error).
At the end of the log you find:
822413 connect(4, {sa_family=AF_UNIX, sun_path="/run/user/1000/gcr/ssh"}, 110) = 0
...
822413 read(4,
meaning it’s trying to interact with the ssh-agent, but it (finally) doesn’t give a response.
Use the lsof command to figure out which program is providing the agent service and try to resolve issue that way. If it’s not the OpenSSH ssh-agent, then maybe you can disable its ssh-agent functionality and use real ssh-agent in its place…
My wild guess is that the program might be trying to interactively verify the use of the key from you, but it is not succeeding in doing that for some reason.
I guess it’s worth checking if those names point to the expected binaries, but I also think it would be highly unlikely they would be anything else than just /usr/bin/ssh and /usr/bin/ssh-agent.
As mentioned, -v (or -vv) helps to analyze the situation.
My theory is that you already have something providing ssh agent service, but that process is somehow stuck, and when ssh tries to connect it, it doesn’t respond to the connect, or it accepts the connection but doesn’t actually interact with ssh. Quite possibly ssh doesn’t have a timeout for interacting with ssh-agent.
Using eval $(ssh-agent -s) starts a new ssh agent and replaces the environment variables in question with the new ones, therefore avoiding the use of the stuck process.
If this is the actual problem here, then before running the eval, echo $SSH_AUTH_SOCK would show the path of the existing ssh agent socket. If this is the case, then you can use lsof $SSH_AUTH_SOCK to see what that process is. Quite possibly it’s provided by gnome-keyring-daemon if you’re running Gnome. As to why that process would not be working I don’t have ideas.
Another way to analyze the problem is strace -o logfile -f ssh .. and then check out what is at the end of the logfile. If the theory applies, then it would likely be a connect call for the ssh-agent.
I highly doubt businesses would have been this fast in making the switch.
Well that’s exactly the worry. Why shouldn’t it be? It is their business and livehood.
As if taking down the systems is the biggest cybersecurity threat a company might have.
But how many use it for browsing, which I imagine this data is from?
Am I to understand correctly that if you are running Gtk+ apps in the Gnome compositor, you get this working, but if you are running non-Gnome compositor with Gtk+ apps, it will not work? Or is it independent of the compositor?
You should have backups. Preferably also snapshots. Then rm will feel less scary.
If you want to have multi-host redundant storage at home (via e.g. minio or ceph), S3 is a pretty good protocol to provide it.
S3 is nice in the way it’s not a file system so it can have relaxed semantics, while also providing secure access to individual files over HTTPS via URL signing.
Some people seem to be stuck in the idea that S3 means cloud hosting. Not sure if that was your view, but it’s worth spelling out sometimes.
That was a Firefox bug, based on one comment in the Bitwarden isue tracker . It should be fixed now in Firefox 116.
Boox Tab Ultra
Looks pretty nice device! Even the camera makes a bit sense in the demo they give (though apparently in practice the scanning rarely works). And cheaper to boot as well. I might consider getting this one.
But is the display really better quality? Atleast the DPI is slightly higher at 219 on the Boox Tab Ultra vs 190 on the Daylight. And Boox weighs 70 grams less, and that’s the device some reviews call heavy (and some lightweight…).
These reviews mention the slow display speed:
So perhaps there is some room for improvement? That being said, some other reviews don’t mention it and one says it’s faster than typical e-ink display, though that doesn’t sound immediately purely praising.
In the end it probably comes to the software: how fast it is, it well it works, how nice it is to use. It seems both have customized the standard Android, so I suppose the difference is in which one has done it better and which one has better custom apps. Per the reviews Boox doesn’t fare too well in this aspect. Maybe someone will make a comparative review of the devices.
As opposed to buing a separate display for the computer?
I like to think this thing would be nice reading the news while having a breakfast or reading an e-book outside or at the bed, not near my computer. So it makes a lot of sense to build a tablet with this display technology.
Zooming and panning a pdf is arguably more comfortable with higher frame rate.
What a nice succinct explanation!
But also completely useless. Run0 ignores the suid bit for the same reason as 99% of command line apps do: it ignores because it isn’t relevant to its functionality.
Would that kind of provision allow me to have my code removed from a git repository history, if that git repository is hosted by a company?
Alas my game PC is going to stick with Windows due to bad state of VR in Linux :/. And therefore one day it might need to update to Windows 11.
In particular if you have a headset that is not Valve Index, though apparently with Meta Quest one can use ALVR, as long as you get the actual games running.