1,431 karma · joined December 16, 2009
Contact: gergely@imreh.net
Based at http://gergely.imreh.net
Taipei Hackerspace co-founder https://taipeihack.org
[ my public key: https://keybase.io/imrehg; my proof: https://keybase.io/imrehg/sigs/Vqc30FUDkAzeR6b4jTTQown3Qjned_Xju7DqvvT6DfU ]
To me this understanding and shift in perception came after a few days of intense experimentation with IPFS, trying different use cases, etc. There are plenty of surprises if you just want to use IPFS as decentralized storage, as most introduction seems to approach it.
And it's definitely very cool & inspiring to find different use cases for IPFS :) For example the IPFS-backed docker registry is similarly cool https://github.com/jvassev/image2ipfs/ (though unfortunately seems abandoned or just in deep hibernation...)
If I use "pkcs15-tool --read-ssh-key 1" to read out the public key, (in the "ssh-rsa AAAAB3Nza....." format), then I get a vulnerable key warning (2048bit SSH key).
On the other hand, if I use "pkcs15-tool --read-ssh-key 1 --rfc4716" to output in "---- BEGIN SSH2 PUBLIC KEY ----...." format, then it shows different key tests and tells me it's "safe key".
Is this a weakness of the test, or is there really some difference between the "regular" and the "RFC4716 formatted key (I wouldn't expect that)? What am I missing?
EDIT: using the standalone "roca-detect" (note, Python2 is required), then the first format reports potential vulnerability, while running it on the second format results in "Exception in processing PGP rec file estonia1.asc: Incorrect padding". So I guess it is indeed that the tool does not handle RFC4716 formatted SSH keys correctly?
[0]: https://membership.theguardian.com/event/salman-rushdie-a-li...
Resin.io provides a software platform that helps developers build, deploy and manage the code that runs on connected devices. Our technology is open, standards-based, and proven in production across a wide range of scenarios from drones, 3D printers, point-of-sale devices, tidal turbines, skyscrapers and more.
Current open positions:
* Rust Software Engineer | Remote | https://resin.workable.com/j/ACF748D4A2
* DevOps Engineer | Remote | https://resin.workable.com/j/5F000FAEC5
* Technical Content Lead | Remote | https://resin.workable.com/j/A6833569B5
* Solution Architect (US West Coast) | Seattle | https://resin.workable.com/j/D3A0DFBBF9
* and also open call, if you enjoy working on the various facets of IoT | Remote | https://resin.workable.com/j/2A9DEA16E5
See full job listing, and apply at https://resin.workable.com/ and mention Hacker News. The interview process includes a programming test, and remote interviews with relevant members of the team.
According to the article Mender releases under Apache 2.0, and all resin.io's open source code is also on Apache 2.0, so it should be the same permissive setup.
(Source: working at resin.io)
http://docs.aws.amazon.com/lambda/latest/dg/current-supporte...
Resin.io brings DevOps to IoT. We help organizations deploy software to remote devices for use in far-ranging scenarios, from smart locks, to drones, to wind turbines and more.
- Solutions Architect | Seattle, USA
- Full Stack Developer for Resin Supervisor (JavaScript + Rust) | remote
- DevOps Engineer | remote
- Application Security Engineer |remote
- Linux Engineer | remote
- Open Call | remote
See full job listing, and apply at https://resin.workable.com/ and mention Hacker News. The interview process includes a programming test, and remote interviews with relevant members of the team.