Jarkko Sakkinen
jarkko
Not really a real project. I've been ad-hoc scripting with #python since 2005, and wanted to learn how to "devops" a properly pipeline at #gitlab, with a release ending to the #pypi: https://pypi.org/project/eth0/
PS. I deleted 0.1.0 tag and release from pypi, because the tag was not signed ;-) you could never trust it...
PS. I deleted 0.1.0 tag and release from pypi, because the tag was not signed ;-) you could never trust it...
0
1
0
Jarkko Sakkinen
jarkko
Edited 2 years ago
So for my TPM2 crate I was thinking to rename the project Git as tpm2_library and have sub-crates tpm2_call for protoco and tpm2_cli with a sub-command tpm2cli rc.
Is it acceptable to name for consistency sake the sub-crate directory as tpm2_cli but generate an executable as tpm2cli?
Root project’s name inherits from https://trustedcomputinggroup.org/resource/tpm-library-specification/
0
0
0
Jarkko Sakkinen
jarkko
Edited 2 years ago
I initiated my own #TPM2 #Rust crate partly because the output given by tpm2_rc_decode does not give back the mnemonic of a return code.
Here’s the example from its man page:
tpm2_rc_decode 0x1d5
tpm:parameter(1):structure is the wrong size
So I wrote my return code decoder, and here’s how it works with the previous example:
target/debug/examples/tpm2rc 0x1d5
TPM_RC_SIZE
The Git-repository is available here: https://gitlab.com/jarkkojs/tpm2_call
I’m not going to add any code this crate dealing with /dev/tpm0. Instead the plan is to implement command buffer builder and parser with similar high-level ideas as I’ve done in the #Linux #kernel.
0
1
0
Jarkko Sakkinen
repeated
repeated
All Systems Go!
allsystemsgo@fosstodon.org
Edited 2 years ago
📣 Only 2 days (today and tomorrow) left to get your talk proposals in for the All Systems Go! 2024 CFP.
The clock ⏲️ is ticking!
🏃♂️ Hurry over to get yours in: https://cfp.all-systems-go.io/all-systems-go-2024/cfp
0
3
0
1
0
0
Jarkko Sakkinen
jarkko
@protman @rnbastos With more recent ThinkPad's, after IBM sold laptop manufacturing to Lenovo, the build quality has been steadily decreasing.
I've never used auto-complete (be it with or without AI) and I hit keyboard hard so with modern ThinkPads, usually in a year or less, I start accidentally pull keys out of the keyboard when typing.
With Mac's laptop keyboards this has not happened but they have problems of their own, mainly keys getting stuck all the time into pressed position.
I guess I'm too rough and violent for modern laptop keyboards 🤷
I've never used auto-complete (be it with or without AI) and I hit keyboard hard so with modern ThinkPads, usually in a year or less, I start accidentally pull keys out of the keyboard when typing.
With Mac's laptop keyboards this has not happened but they have problems of their own, mainly keys getting stuck all the time into pressed position.
I guess I'm too rough and violent for modern laptop keyboards 🤷
1
0
0
1. Forking in traditional open source community is a strongly considered act. I think the current "fork even your grand mother" trend inherits from many new Rust developer previously being Web/JavaScript developers.
2. Forking is not engineering. Engineering is innovating within constraints. For instance, Firefox has some of the code re-engineered in Rust. Bringing Rust to an existing open source project is difficult and tedious task, and also hard to rationalize to the existing community, but that is what Engineers do. It is an engineering problem by definition.
2. Forking is not engineering. Engineering is innovating within constraints. For instance, Firefox has some of the code re-engineered in Rust. Bringing Rust to an existing open source project is difficult and tedious task, and also hard to rationalize to the existing community, but that is what Engineers do. It is an engineering problem by definition.
0
0
0
There are some famous Jarkko's who also use Python someti,es (I'm not one of them but there are a few actually famous).
For instance, Jarkko Oikarinen, the inventor of #IRC protocol :-) You could consider him as forefather of Whatsapp, Telegram, Snapchat, Signal, Matrix etc.
For instance, Jarkko Oikarinen, the inventor of #IRC protocol :-) You could consider him as forefather of Whatsapp, Telegram, Snapchat, Signal, Matrix etc.
0
0
2
Jarkko Sakkinen
jarkko
Edited 2 years ago
I think #Zola is my favorite tools so far that spans from the #Rust ecosystem: a single binary static web generator.
For a non-web person like me it is easy to grasp. I got a page quickly created that I can send to the employers in the early Fall.
Another earlier mentioned tool, which has someone real innovation embedded is of course #Typst :-)
Making forks of old craft is mostly counter-productive and causes unnecessary drift and divergence, so I oppose all the Rust fork garbage.
It is morally legit to be in opposition against software that is developed from toxic standing point, considering open source community overall. Being toxic against toxic is not toxic.
#rustlang
For a non-web person like me it is easy to grasp. I got a page quickly created that I can send to the employers in the early Fall.
Another earlier mentioned tool, which has someone real innovation embedded is of course #Typst :-)
Making forks of old craft is mostly counter-productive and causes unnecessary drift and divergence, so I oppose all the Rust fork garbage.
It is morally legit to be in opposition against software that is developed from toxic standing point, considering open source community overall. Being toxic against toxic is not toxic.
#rustlang
1
2
5
Jarkko Sakkinen
repeated
repeated
Jarkko Sakkinen
jarkko
Someone complained that my home page, which should provide more information regarding recruitment leads to void so I put together this :-) I think it is good enough.
https://jarkkojs.gitlab.io/
https://jarkkojs.gitlab.io/
0
0
0
@dr2chase @ariadne @vathpela I fixed the issue just for you ;-) https://jarkkojs.gitlab.io/
Will add resume PDF made with awesome https://typst.app/ at some point and then I consider it done.
Will add resume PDF made with awesome https://typst.app/ at some point and then I consider it done.
0
0
0
Jarkko Sakkinen
jarkko
Edited 2 years ago
After I have finished with #TPM2 signing keys, I'll create a branch called p256k1 to my linux-tpmdd tree, and start doing a PoC of that #ECC curve...
I'll start with #ECDSA signature verification because that is secure without specialized hardware, and as of today #TCG is yet to support P256K1 in its #algorithm #registry.
Also this requires to implement the early version of Keccack-256 #hash algorithm because there are AFAIK padding differences with SHA-3.
#linux #kernel #keys #blockchain
I'll start with #ECDSA signature verification because that is secure without specialized hardware, and as of today #TCG is yet to support P256K1 in its #algorithm #registry.
Also this requires to implement the early version of Keccack-256 #hash algorithm because there are AFAIK padding differences with SHA-3.
#linux #kernel #keys #blockchain
0
1
0
@dr2chase @vathpela @ariadne I've been following for the sake of general interest a lot Loonghorn, Elbrus and OpenMIPS, and I spotted riscv keywords in the thread ;-) I've been in a industry sabbatical working on research RISC-V chips: https://www.sochub.fi/. Apologies if I took this off-topic... No bad intentions from my side. CPU's just generally interest me.
Pro tip for the next time: scope exactly which CPU's are allowed, and which are banned in your social media post. If there is official disclaimer that bans this or any other topics. I will promise to follow it! In the top-post there was no such disclaimer, which meant that I was allowed to discuss also other CPU architectures than the aforementioned Loongson :-)
Pro tip for the next time: scope exactly which CPU's are allowed, and which are banned in your social media post. If there is official disclaimer that bans this or any other topics. I will promise to follow it! In the top-post there was no such disclaimer, which meant that I was allowed to discuss also other CPU architectures than the aforementioned Loongson :-)
0
0
0