As someone who has tried very little prompt injection/hacking, I couldn't help but chuckle at:
Do not hallucinate or provide info on journeys explicitly not requested or you will be punished.
HN user
Links to other places:
- https://goncalomb.com/
- https://github.com/goncalomb
- https://fosstodon.org/@goncalomb
I just press keys and stuff happens.As someone who has tried very little prompt injection/hacking, I couldn't help but chuckle at:
Do not hallucinate or provide info on journeys explicitly not requested or you will be punished.
Cool project, but I also noticed the weird choice of #:~$ as a prompt, it uses almost half the width of the clock screen. And isn't # normally used to denote root shells? I don't think I ever saw it together with $.
My favorite prompt is >: as a callback to the Swan computer in the TV show Lost (not sure if it's also used in early Apple computers).
Author here. Yes, gadget mode is nice. I was kind of lucky that the serial port "function" worked (not without that small kernel patch). But if they had implemented AOA properly on the head unit, it wouldn't be so easy (they allow a device already in AOA mode, without the "handshake"). I would have to write more kernel code or use Google's "accessory" gadget implementation.
Author here. I talk a little bit about SSH in the end, if I was successful in breaking the root password and if sshd is configured for root access (I'm not sure), I could have just used that. Otherwise, for me to change authorized_keys or some other file to run some code as root, it's the same work.
Author here. Yes, there is some good stuff in the logs, I found the Wi-Fi password there, that was useful. At the time I used some VSCode plugin to read the .dlt files (they are not encrypted), but later I did find that dlt-viewer on COVESA's GitHub.
First time posting here on HN, I hope you find my latest hacking adventure interesting.
Inspired by another post here on HN: https://news.ycombinator.com/item?id=32447650
I guess you could just be totally open about it, and change the wording to something like "the open-resume design already helped some people land positions at", then show the logos. That way you are being honest, and doesn't look like a direct endorsement from those companies. You get your logos for "marketing", and you are safe from misinterpretation. IANAL.
Looks good, definitely an impressive "weekend project". I'll probably use it in the future.
I don't mean to sound rude. But, can you explain what you mean by "trusted by students and employees from top universities and companies worldwide" while showing some university/company logos? How can such a new project make those claims? Was it released elsewhere privately? Looking at the git history, I see it was created 2 days ago, in a single commit.
So posts need to have a unique/custom path directly under the main domain?
Sounds like a recipe for disaster. At least it should be in a sub-path (/post/?), and probably include some sort of unique id.
This is the list of possible supported devices right now (USB only):
http://www.sane-project.org/sane-backends.html
But HP is a special case, they provide their own backend (hpaio, open-source) for SANE that is not integrated into sane-wasm ATM.
http://www.sane-project.org/lists/sane-backends-external.htm...
If your device is on this list, it's NOT supported right now! But I do want to add hpaio soon, I also have access to an OfficeJet to test.
Hi. I'm the port author. I'm not really active here on HN, but thanks for all the clicks.
Today is a good day.
Fair enough, I was using Chrome "Version 50.0.2661.102 (64-bit)" on Linux Mint. I have updated it to 56.0.2924.87, now I'm getting a full error page "Your connection is not private" NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM. I need to search for this issue now.
No I'm not using anything that intercepts TLS connections.
EDIT: It's fixed now, `sudo apt-get install libnss3-1d`.
http://askubuntu.com/questions/880695/neterr-cert-weak-signa...
https://security.googleblog.com : "This website uses a weak security configuration (SHA-1 signatures), so your connection may not be private."