Here is an example message encrypted to the key
This is an armored file encrypted with age-tool.com, version 1
-> X25519 DeasSsF-PM4SYVmy0qhVEU3ocF3MBQCmDQaDPeensF0
--- end of file ---
Note that this uses a different end of file marker than the initial
draft implemented by rage (sorry Str4d!).
You received this message because you are subscribed to the Google Groups "age-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to age-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/age-dev/ab7a1151-14fb-4e05-85db-25f4f5d849e8%40www.fastmail.com.
The ASCII armor format is now in the spec and implemented in
github.com/FiloSottile/age (command line flag -a).
Hey, maybe this is off-topic or too late, but is there a reason the spec hard-wraps at 56 columns instead of allowing the file/data viewer to soft-wrap?
The salt pack format simply uses spaces every 15 characters, which wraps much more nicely on various screen sizes, as shown on their website: https://saltpack.org/
Thanks for your work, and I look forward to using
-> X25519 jxogGETLAZtc70T35gEa7-TyTsqRKjoh4w-URI2tHC4FflFC6gUrydahfQj9KmVI8eznYR7XNm5Ra_19CvbvyY--- i7xr4pMS8q4zCzK9-qO4vk6ENoCw-kwcSMYwnJCD6NYkYM5h1pg6qz9UMn j6G7KB2OUX3itkn C30ZZBPzjc8STxf i06TIQhJ4wRFSMU hFa9gmcvl2AW8Kk qmTdLkkppPieOWq o9aWouAaMpQ9kWt eMlv17NOUUr9Gp3 fClo7khRnJ12T7j 6ZVkfDXUpznTp57 0btBywDV848jyp2 EceloYGiuOolWim 8HCx77p22iulWja ixShPFcOi1mkG2i 4Iur3QfGYeKpflx a1GXmvQLi1G99mH 625dH5HGcQ63pOb K1i7g3lXIQ9Kcfy NRDfdBIDMHJaJf1 uTKB4GJ9l4M7glS 07h9QsU4gPueyNC hzm6LmA9CFllzxy 8ZA0Ys5qDnSuwaN obowMNXpbm1nlsx fXFtMolx6ghLuEw 2s8f1jBxBQjQPwa GG90h5BbpoWGPk6 dRsou5kdNxcLaFJ KKXWTUR2h9P0P7p 9UYRsQ6QqGNiwmG wXC7YFh1xCUdAib gjZbUYUKN6KVLem hZI6XYtX2l1w8d5 jL8KJ5ZZpKhJ4JC faVWCU2VRtUFgQO ejKm6wjs6NcekTd KK4bOh5kr87cyRu 0aDjEtfMSyZZTG5 hIrEWcMq1Iotzrx iRdmY5GYf2Kx0Br 4K0rqrj8ZGa.
Using the saltpack armor for just the payload would look kind of awkward.
I do like the Markdown resistance of the saltpack armor
but then to get its benefits we'd have to change the encoding of everything that currently uses Base64. Also, every language has a Base64 implementation, while this is a custom encoding. (Maybe we should use a more innocuous pair of special characters than "_" and "-"? Maybe "!" and "?" or the standard "+" and "/"?)
On Friday, November 29, 2019 at 4:27:33 AM UTC, Filippo Valsorda wrote:Using the saltpack armor for just the payload would look kind of awkward.
However, I don't know if this is a problem with the encoding or with the header. One potential issue with the "This is an armored file..." header is that it's not obvious that the textual header is part of the file. Would age throw an error if that textual header would be left out?
Am Freitag, 29. November 2019 07:03:21 UTC+1 schrieb Aaron Janse:On Friday, November 29, 2019 at 4:27:33 AM UTC, Filippo Valsorda wrote:Using the saltpack armor for just the payload would look kind of awkward.However, I don't know if this is a problem with the encoding or with the header. One potential issue with the "This is an armored file..." header is that it's not obvious that the textual header is part of the file. Would age throw an error if that textual header would be left out?
I agree with their observation. I was following the live stream on Twitch and thought to myself that the armor header looks a bit problematic in exactly that regard. Maybe I am just used to seeing the pgp armor header and it's obvious visual indicators that it is indeed part of the entire file and if removed will cause problems. Maybe there isn't a real problem as I am not a cryptographer, but since someone else noticed it too I thought of speaking up about it.
-----BEGIN AGE MESSAGE-----
Format: age-tool.com version 1Tool: github.com/FiloSottile/age v1.0.1
X25519 CJM36AHmTbdHSuOQL-NESqyVQE75f2e610iRdLPEN20 C3ZAeY64NXS4QFrksLm3EGz-uPRyI0eQsWw7LWbbYig
X25519 ytazqsbmUnPwVWMVx0c1X9iUtGdY4yAB08UQTY2hNCI N3pgrXkbIn_RrVt0T0G3sQr1wGWuclqKxTSWHSqGdkc
Payload: yDgBO22WxBHv7O8X7O/jygAEzol56iUKiXmV+XmpCtmpqQUKiQrFqclFqUDBovzS vBSFjNSiVHsuAA===njUN -----END AGE MESSAGE-----