Interesting. I'm using ed25519 keys in my open source project [1] to sign GitHub releases (amongst other things) and the encoding question appeared during the development. I settled on supporting reading ssh keys, but saving keys in a specific format. I'll need to have a look to possible revisit my choices as it is developed in rust too.
I would love to take an Interrail, eg to visit France, but it's x days in one month (8 days is 292€ per person) and doesn't match my travel habits. I would prefer to make short travels everyday rather than long travels 8 days of the month.
Can this be useful for someone with no prior knowledge of lean? I'd like to verify a software I'm working on, but I have no experience in formal verification. Can I get useful result with the spec, the code and some (limited) learning time on my side?
I'd expect that if females start to breed more than once it would represent a problem. It's surprising it hasn't happened yet (for the ignorant of the field that I am at least)
I am currently recording tutorial videos for an open source project. It's produced fully with Foss software (on Linux, obs, kdenlive) and about an open source project, so I wanted to host it with peertube (though YouTube might be used later on for its network effect, it was easier to publish with peertube as yt required an video of me and my ID).
It's going fine until now. I don't host peertube myself though, I use an existing instance, and embed the videos in the website.
It was a really good experience, so I'll continue that way.
In case anyone is interested, I'm also using bash scripts to run my agents in containers. It's simple, but has only bash and docker as dependency: https://github.com/asfaload/agents_container
It probably started as a helper script and grew from there. The script seems quite focused and doesn't grow, so a rewrite might not be warranted.
It also has no other dependency, which is also good. I have written helper script to run coding agents in a container. And you guessed it, it's in bash. For the reasons I just wrote down. Should it have to grow I would rewrite it, but not currently.
At a time I was very interested in haxe, but their focus on games made it (perceived as) lacking in the area I wanted to use it (cross platform client-server apps). Recently rust seems to have taken this role for me.
Damn! Would you have the opportunity to share experiences? My emails is in my profile, it would be great to hear from you. (It is an open source project, which makes it even harder to sell probably, so every hint might help!)
Good timing for me too. I'm currently looking for a first customer with whom I'd possibly shape the product a bit. The development phase was fun, now comes the hard part.
Additionally I'm working on a security related product (digital artifact authenticity validation) and I feel like security is a hard sell especially in my network as they don't seem to correspond to the product's target (or I'm a poor promoter of the solution....). .
Putting finishing touches on an open source multi sig solution to authenticate digital artifact, aiming to increase security of the software supply chain. It's open source, completely self hostable, incl internally, support air gapped signers, fully auditable (data store is a puglic git repo). It's an alternative to sigstore, making different decision.
The open source project I'm working on aims to authenticate artifact downloads (project name is asfaload, in short it is a sigstore alternative).
My understanding is that in a post-quantum world, the private key can be derived from an ed25519 pub key. That means that an attacker can generate new signatures. But I don't think an attacker would be able to generate a malicious artifact that matches an existing signature. It would seem that once we are nearing PQC, Asfaload would need to support PQC signatures, and its uses would need to migrate to new keys, but that existing signatures would still be safe to use for validation. Is that right?
I've been working on a new project using ed25519 signatures and discovered they are not quantum resistant.... I went with ed25519 due to possibility of using openssh keys. Any opinion on this choice at the light of this article and other quantum computing news?
I agree! It's amazing to require the visitor to edit the url to go from blog to main site. For my projects I pay attention to avoid this as I find it so annoying. I want visitor that are interested to have easy access to the website!
Open source multisig signoff solution: https://asfaload.com