tmsr - Search: ".sig"

290 entries in 0.635s

lobbes: ascii_field: I can confirm the same behavior on my graphical winblowz browsers (Firefox, Chrome). On Firefox, I get additional message of 'MrTAHIXE.sig.part could not be saved, because the source file could not be read.'

ascii_field: http://www.loper-os.org/pub/mpi/mpi-genesis.tar.gz.sig doesn't load in any version of 'chrome' or 'chromium' also.

assbot: Logged on 02-11-2015 19:05:41; ascii_field: does anyone else find that http://www.loper-os.org/pub/mpi/mpi.tar.gz.sig will NOT download in any ver of firefox ?

ascii_field: does anyone else find that http://www.loper-os.org/pub/mpi/mpi.tar.gz.sig will NOT download in any ver of firefox ? ☟︎☟︎

mod6: http://thebitcoin.foundation/v/V-20151025.tar.gz && http://thebitcoin.foundation/v/V-20151025.tar.gz.mod6.sig

ben_vulpes: armored and clearsigned body + patch + patch.sig, right?

mod6: http://thebitcoin.foundation/v/V-20151014.tar.gz.mod6.sig

mod6: http://thebitcoin.foundation/v/V-20151011.tar.gz.mod6.sig

trinque: mircea_popescu: also http://deedbot.org/genbootstrap.sh and http://deedbot.org/genbootstrap.sh.sig << the configuration in the script currently dumps out a root.img which can be loaded into qemu

asciilifeform: trinque: http://www.loper-os.org/pub/derive.zip.sig

assbot: Logged on 07-09-2015 21:39:45; ascii_field: ;;later tell gabriel_laddel http://www.sigsam.org/bulletin/articles/178/stoutemyer.pdf << some actual implementation details re: 'derive' & 'mulisp'

assbot: bitcoinxt/gitian.sigs · GitHub ... ( http://bit.ly/1NoCA1J )

midnightmagic: I think they do sign them: https://github.com/bitcoinxt/gitian.sigs

asciilifeform: http://www.sigsam.org/bulletin/articles/178/stoutemyer.pdf << again, for anyone who missed this, and is interested in 'derive' or 'mulisp'. this article was co-written by the authors of mulisp and derive! chock-full of implementation details and interesting lore. and yes, it is in pdf. and no, it cannot be represented in ascii. fuckyou buy a printer.

ascii_field: ;;later tell gabriel_laddel http://www.sigsam.org/bulletin/articles/178/stoutemyer.pdf << some actual implementation details re: 'derive' & 'mulisp' ☟︎☟︎

assbot: Logged on 04-09-2015 23:54:25; asciilifeform: mircea_popescu: here's how i do it: 1) clearsigned (asciiarmoured) body. 2) attachment 3) signature (asciiarmoured, detached) of attachment, having the filename attach.foo.sig for every attach.foo

asciilifeform: mircea_popescu: here's how i do it: 1) clearsigned (asciiarmoured) body. 2) attachment 3) signature (asciiarmoured, detached) of attachment, having the filename attach.foo.sig for every attach.foo ☟︎

mircea_popescu: the "with clearsigned body and .sig signature" version is exact replica of the single email i successfully sent to date, back in the days of the V patch.

mircea_popescu: ok, for the record : sent it with no body, and with a clearsigned body ; the latter with .asc armored signature and with .sig binary signature. still nothing there.

mod6: asciilifeform: I took a look at v99 just briefly, so far, looks good. I dropped in my sigs from http://therealbitcoin.org/ml/btc-dev/2015-August/000158.html into ~/.seals along with the sigs/*.sig files that it comes with and I was able to genereate the following: http://dpaste.com/198XBTF.txt

asciilifeform: loper-os.org/pub/derive.zip.sig

mod6: so if we do <patchname>.<wotGuy>.sig then will fail

mod6: these sigs that you posted won't verify out-of-the box, not that i've tried. but the detached sig must match the file name with the exception of the trailing .sig on the end.

mod6: asciilifeform: I see you attached the sigs for the vpatch files, and included the tarballs in your orchestra+breath-of-life (UPDATED) email. I think it'd like to attach the raw .vpatch files as well as the .sigs for completeness. Anything against this other than it's a bit redundant since you already posted the tarballs of the .vpatches?

mod6: <+asciilifeform> mod6: i recommend to follow the format nameofpatch.vpatch.mod6.sig << cool, sounds good.

asciilifeform: mod6: i recommend to follow the format nameofpatch.vpatch.mod6.sig

asciilifeform: punkman: a .sig file should consist wholly of the detached sig

jurov: mircea_popescu: only clearsigned text is mandatory, there can be none or any number of further attachments(not necessarily only patches), each with detached attachment.name.ext.sig

ascii_field: mircea_popescu: third, if the second exists - a detached .sig for it

mircea_popescu: your .sign file, look at it. is it empty ?

mircea_popescu: http://buildroot.uclibc.org/downloads/buildroot-2015.05.tar.gz.sign << it doesn't actually dld.

assbot: Logged on 15-08-2015 22:32:03; trinque: shinohai: http://deedbot.org/genbootstrap.sh.sig

gribble: POCSAG - Wikipedia, the free encyclopedia: <https://en.wikipedia.org/wiki/POCSAG>; POCSAG - Signal Identification Wiki: <http://www.sigidwiki.com/wiki/POCSAG>; RTL-SDR Tutorial: POCSAG Pager Decoding - rtl-sdr.com: <http://www.rtl-sdr.com/rtl-sdr-tutorial-pocsag-pager-decoding/>

trinque: shinohai: http://deedbot.org/genbootstrap.sh.sig ☟︎☟︎

assbot: Logged on 09-11-2014 01:21:15; punkman: here's a thought: .sign AQLSTVsF http://paste.com/detached_sig.txt

mod6: http://thebitcoin.foundation/test-builds/v0.5.4/amd64/bitcoin-v0_5_4-TEST2.tar.gz && http://thebitcoin.foundation/test-builds/v0.5.4/amd64/bitcoin-v0_5_4-TEST2.tar.gz.sig

asciilifeform: i don't see why i should EVER have to mv bitcoin-v0_5_4-TEST1_8a8d52a747f0b0bd5d7a2cce9d0938f1dd6e1239.tar.gz.sig bitcoin-v0_5_4-TEST1.tar.gz.sig

asciilifeform: http://therealbitcoin.org/ml/btc-dev/attachments/20150725/ak47_8e05a9c323700966880c198e1baec51f76a025d8.sh.sig << confirmed, verifies

asciilifeform: ('diff ak47_05243673e45fc4c4ce30467f8ffc003deec1d184.sh.sig ak47.sh.sig' rather than foo)

asciilifeform: ben_vulpes: here is proof. 'dos2unix -f ak47_05243673e45fc4c4ce30467f8ffc003deec1d184.sh.sig' then 'diff foo.sig ak47.sh.sig'

asciilifeform: $ pgpdump -i ak47_05243673e45fc4c4ce30467f8ffc003deec1d184.sh.sig

hanbot: 3197e61aff68e988c611b6ef4c4d7092645804a800112435089da3af1a9ef2bea8fb6198de3f0ab17483e601cc1ce1a0e0afd4132607bdc7f6ef5d08953e1f83 ak47_05243673e45fc4c4ce30467f8ffc003deec1d184.sh.sig

mod6: `gpg --verify stator.tar.gz.sig`

mod6: then `mv stator_7447d6ad798179d04e9d277acb72799b3c7d0eae.tar.gz stator.tar.gz` and `mv stator_72424e6da0f81aea5ab09165c377fd8b7418983f.tar.gz.sig stator.tar.gz.sig`

mod6: once pulled down do this `sha1sum stator_7447d6ad798179d04e9d277acb72799b3c7d0eae.tar.gz stator_72424e6da0f81aea5ab09165c377fd8b7418983f.tar.gz.sig` and ensure that the output hashes match what's embedded in the file name.

mod6: hanbot: pull down http://therealbitcoin.org/ml/btc-dev/attachments/20150627/stator_7447d6ad798179d04e9d277acb72799b3c7d0eae.tar.gz & http://therealbitcoin.org/ml/btc-dev/attachments/20150627/stator_72424e6da0f81aea5ab09165c377fd8b7418983f.tar.gz.sig

punkman: well if it doesn't reject files that don't match .sig, I could just put them in a tar.gz

punkman: also works if I download .sig and --verify it

punkman: my .sig verifies right?

jurov: if you sent lenna_full.jpg and lenna_full.jpg.sig it should add them to list, too

assbot: dpaste: 2DDHFF4: jautenim_openssl_docs_snip.patch.sig ... ( http://bit.ly/1f1Ifwl )

assbot: Logged on 29-06-2015 04:51:04; asciilifeform: ;;later tell mircea_popescu http://www.loper-os.org/pub/turdsums/readme_s.txt http://www.loper-os.org/pub/turdsums/sums.txt.gz http://www.loper-os.org/pub/turdsums/sums.txt.gz.sig

asciilifeform: ;;later tell mircea_popescu http://www.loper-os.org/pub/turdsums/readme_s.txt http://www.loper-os.org/pub/turdsums/sums.txt.gz http://www.loper-os.org/pub/turdsums/sums.txt.gz.sig ☟︎☟︎☟︎☟︎

jurov: mats as the .sig file verifies, the hash must be therein

mod6: so after review you just expect or perhaps exepect to just see a .sig file attached alone without the patch itself?

decimation: ascii_field: what about these http://www.signatec.com/products/daq/high-speed-digitizer-pc-interfaces.html

jurov: then why are all .tar.gz.sig?

danielpbarron: the patch.sig is by ascii's key, so it shouldn't matter what it hashes to or what btc-dev says

mod6: curl -s http://therealbitcoin.org/ml/btc-dev/attachments/20150504/asciilifeform_orphanage_thermonuke_6f320afb2423a2892d89e855829e3915c8b7a170.patch.sig -o asciilifeform_orphanage_thermonuke.patch.sig

lobbes: http://therealbitcoin.org/ml/btc-dev/attachments/20150318/README_f53e601e464af51f37d2b1f2ed38a7e8712a5462.txt.sig

gribble: Ravenscar profile - Wikipedia, the free encyclopedia: <http://en.wikipedia.org/wiki/Ravenscar_profile>; Guide for the use of the Ada Ravenscar Profile in high ... - SIGAda: <http://www.sigada.org/ada_letters/jun2004/ravenscar_article.pdf>; The SPARK Ravenscar Profile - AdaCore: <http://docs.adacore.com/sparkdocs-docs/Examiner_Ravenscar.htm>

mod6: had 2 attachments, a .patch file and a .sig file

decimation: ~/bitcoin-v009/build/chicken/bitcoin-asciilifeform.1.patch.sig

mod6: hmm, still, should be ok. i just re-ran on my side and got: >> Signature verified for bitcoin-asciilifeform.1.patch.sig

Adlai: product link = http://www.sigmaaldrich.com/catalog/product/sigma/L7007?lang=en&region=US

asciilifeform: (x.y.sig is an ascii-armoured detached sig of the usual variety)

asciilifeform: attach foo.gz and foo.gz.sig

mod6: so you're saying that this doesn't work: gpg --logger-file alert-snip.sig.log --homedir .gnupg

asciilifeform: cat: chicken.sig.log: No such file or directory

danielpbarron: mod6, http://danielpbarron.com/build.sh.sig.txt

mod6: http://thebitcoin.foundation/build.sh.sig

mod6: - --verify chicken/bitcoin-asciilifeform.1.patch.sig

mod6: gpg --logger-file chicken.sig.log --homedir .gnupg \

jurov: it will make blablabla...hexporn.patch.sig

punkman: here's a thought: .sign AQLSTVsF http://paste.com/detached_sig.txt ☟︎

asciilifeform: http://www.loper-os.org/pub/bitcoin-asciilifeform-4.snapshot.tar.gz and http://www.loper-os.org/pub/bitcoin-asciilifeform-4.snapshot.tar.gz.sig

ben_vulpes: i'd really like punkbot to take in the raw doc and .sig files. but...whatever.

mod6: so in this case, ben.sig & mod6.sig, each yields a PGP armored message, that's just a signed file that can be verified.

mod6: each party will want to name ``out.sig'' something different obv.

ben_vulpes: if each party runs gpg --output out.sig --sign --armor thing-to-sign.txt, you can run gpg --decrypt out.sig on the blob

asciilifeform: mircea_popescu, ben_vulpes, others: http://www.loper-os.org/pub/rm_rf_upnp-asciilifeform.patch.sig << related

ben_vulpes: jurov: why bother checking body? instead maybe just check .patch.sig for l2 sig, and compare that to the file.

ben_vulpes: mircea_popescu, asciilifeform: re sig stack is the implication that a signs patch, b signs patch and a.sig, c patch and b.sig...

jurov: and whoever want to sign it, sends patch-author-id.sig too

jurov: thus ... for every attachment named patch-author-id attach also patch-author-id.sig

punkman: Azelphur: try this: git config --global user.signingkey FFFFFFFF

ThickAsThieves: http://www.sigmalive.com/inbusiness/news/services/99911

mircea_popescu: but.he.signed.with.the.devil.

mjr_: because it would be awesome to be able to contribute to a business that you are invested in...signing up helps your actual investment