tmsr - Search: ".sig"

290 entries in 0.657s

bvt: diana_coman: http://bvt-trace.net/vpatches/vtools_ascii_fix.vpatch http://bvt-trace.net/vpatches/vtools_ascii_fix.vpatch.bvt.sig -- preliminary version, as "flow" command behavior is not useful with such vtree

feedbot: http://blog.lobbesblog.com/2019/10/stan-logotron-lobbessig-list/ << lobbesblog -- Stan Logotron: lobbes.sig list

lobbes: k, got the latest logotron patch applied. asciilifeform: I've also read through and signed said patch

snsabot: Logged on 2019-09-13 04:38:29 bvt: lobbes: please test the following vpatch: http://bvt-trace.net/vpatches/active_disconnect.kv.vpatch http://bvt-trace.net/vpatches/active_disconnect.kv.vpatch.bvt.sig ; i'll have time for a writeup only on the weekend. this vpatch is only lightly tested so far.

ericbot: Logged on 2019-09-13 07:55:02 bvt: lobbes: please test the following vpatch: http://bvt-trace.net/vpatches/active_disconnect.kv.vpatch http://bvt-trace.net/vpatches/active_disconnect.kv.vpatch.bvt.sig ; i'll have time for a writeup only on the weekend. this vpatch is only lightly tested so far.

bvt: lobbes: please test the following vpatch: http://bvt-trace.net/vpatches/active_disconnect.kv.vpatch http://bvt-trace.net/vpatches/active_disconnect.kv.vpatch.bvt.sig ; i'll have time for a writeup only on the weekend. this vpatch is only lightly tested so far.

bvt: ty; i wanted to download them via wget on remote machine, discovered bunch of .sig.1 files

a111: Logged on 2019-07-06 17:08 bvt: mp_en_viaje: ty for the comment; i have to go afk now, so most likely vdiff fix will be out tomorrow 2nd half of the day. right now it is at http://bvt-trace.net/vpatches/vdiff_blockwise_read.vpatch (add .bvt.sig for the seal)

bvt: mp_en_viaje: ty for the comment; i have to go afk now, so most likely vdiff fix will be out tomorrow 2nd half of the day. right now it is at http://bvt-trace.net/vpatches/vdiff_blockwise_read.vpatch (add .bvt.sig for the seal) ☟︎

billymg: Mocky: updated mp-wp patch and sig available here: http://billymg.com/downloads/mp-wp/mp-wp_remove-tinymce-and-other-crud.vpatch http://billymg.com/downloads/mp-wp/mp-wp_remove-tinymce-and-other-crud.vpatch.billymg.sig

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

bvt: http://bvt-trace.net/vpatches/ffa_ch4_ffacalc.kv.vpatch.bvt.sig http://bvt-trace.net/vpatches/ffa_ch5_egypt.kv.vpatch.bvt.sig http://bvt-trace.net/vpatches/ffa_ch6_simplest_rsa.kv.vpatch.bvt.sig

bvt: asciilifeform: http://bvt-trace.net/vpatches/ffa_ch1_genesis.kv.vpatch.bvt.sig http://bvt-trace.net/vpatches/ffa_ch2_logicals.kv.vpatch.bvt.sig http://bvt-trace.net/vpatches/ffa_ch3_shifts.kv.vpatch.bvt.sig

billymg: in the mean time, if anyone else would like to test, the files here should work for you: http://billymg.com/downloads/mp-wp_add-footnotes-and-textselectionjs.vpatch http://billymg.com/downloads/mp-wp_add-footnotes-and-textselectionjs.vpatch.billymg.sig

a111: Logged on 2018-12-27 18:03 billymg: i created a vpatch for http://btcbase.org/log/2018-10-22#1865184 < http://billymg.com/downloads/mp-wp_add-footnotes-and-textselectionjs.vpatch http://billymg.com/downloads/mp-wp_add-footnotes-and-textselectionjs.vpatch.billymg.sig however i am having trouble pressing it myself

billymg: i created a vpatch for http://btcbase.org/log/2018-10-22#1865184 < http://billymg.com/downloads/mp-wp_add-footnotes-and-textselectionjs.vpatch http://billymg.com/downloads/mp-wp_add-footnotes-and-textselectionjs.vpatch.billymg.sig however i am having trouble pressing it myself ☝︎☟︎

asciilifeform: and ftr naming convention ( carried on since asciilifeform's original vtron ) is simply that patch is $string.vpatch and sig is $string.vpatch.author.sig .

phf: i also have another approach, with V_PATCHES=[('http://.../foo.vpatch', 'http://.../foo.vpatch.first.sig', 'http://.../foo.vpatch.another.sig'),...] where ebuild basically keeps explicit press order, but can also rely on emerge for pulling the files from remote. none of it is particularly satisfying

a111: Logged on 2018-11-14 00:20 mod6: 2) http://btcbase.org/log/2018-11-13#1872126 << diana_coman I tried to leave you a note on your blog. But seems that you've based the genesis off of my vtron version 99994K, but there is a newer version: http://thebitcoin.foundation/v/V-20180222.tar.gz http://thebitcoin.foundation/v/V-20180222.tar.gz.mod6.sig Which is denoted as version 99993K.

mod6: 2) http://btcbase.org/log/2018-11-13#1872126 << diana_coman I tried to leave you a note on your blog. But seems that you've based the genesis off of my vtron version 99994K, but there is a newer version: http://thebitcoin.foundation/v/V-20180222.tar.gz http://thebitcoin.foundation/v/V-20180222.tar.gz.mod6.sig Which is denoted as version 99993K. ☝︎☟︎

ave1: as for an alternative branch; http://ave1.org/code/eucrypt/eucrypt_crc32_divtronic.vpatch.ave1.sig and http://ave1.org/code/eucrypt/eucrypt_crc32_divtronic.vpatch.

bvt: vtools_tempfile_standalone.vpatch http://wotpaste.cascadianhacker.com/pastes/A0SPK/?raw=true vtools_tempfile_standalone.vpatch.bvt.sig http://wotpaste.cascadianhacker.com/pastes/IVy7W/?raw=true

bvt: vtools_fixes_mktemp_template.vpatch.bvt.sig http://wotpaste.cascadianhacker.com/pastes/A5VIC/?raw=true

a111: Logged on 2015-06-29 04:51 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

a111: Logged on 2018-09-27 01:33 mod6: http://thebitcoin.foundation/v/V-20180222.tar.gz << >> http://thebitcoin.foundation/v/V-20180222.tar.gz.mod6.sig

mod6: http://thebitcoin.foundation/v/V-20180222.tar.gz << >> http://thebitcoin.foundation/v/V-20180222.tar.gz.mod6.sig ☟︎

asciilifeform: for the l0gz : http://www.loper-os.org/pub/other/libudp/udp_errata.asciilifeform.vpatch http://www.loper-os.org/pub/other/libudp/udp_errata.asciilifeform.vpatch.asciilifeform.sig .

asciilifeform: ( all of the older vtrons, mine, mod6's , pass the .sig straight to gpg, which doesn't care whether uuencoded )

esthlos: phf I fixed those files if you'd like them, at http://files.esthlos.com/crypto/esthlos-v/v_genesis.vpatch and http://files.esthlos.com/crypto/esthlos-v/v_genesis.vpatch.esthlos.sig

ave1: phf, link was wrong should have been: http://ave1.org/tarpit/tmsr-pgp-genesis.vpatch.ave1.sig. I updated the link in the post.

phf: ave1: http://ave1.org/tarpit/tmsr-pgp-genesis.ave1.sig is missing

asciilifeform: meanwhile, in other koch gpg2isms : https://archive.li/FWdDD >> '...signature verification routine parses the output of GnuPG with an incomplete regular expression, which allows remote attackers to spoof file signatures on configuration files and extensions scripts. Modifying the configuration file allows the attacker to inject additional encryption keys under their control, thereby disclosing passwords to the attacker. Modifying the

esthlos: trinque: updated file at http://files.esthlos.com/crypto/v_2/v.lisp , sig at http://files.esthlos.com/crypto/v_2/v.lisp.esthlos.sig

spyked: current patch draft is at http://lmogo.xyz/v/patches/ircbot-nickserv-auth-add-user-slot.vpatch ; and sig http://lmogo.xyz/v/seals/ircbot-nickserv-auth-add-user-slot.vpatch.spyked.sig . I'm not very sure that my changes to make-ircbot are proper, so I am eager to hear your feedback

a111: Logged on 2018-04-30 01:57 mod6: http://btcbase.org/log/2018-04-29#1806228 << >> http://www.mod6.net/2018/April/30/phexdigit_post.txt >> http://www.mod6.net/2018/April/30/mod6_phexdigit_fix.vpatch >> http://www.mod6.net/2018/April/30/mod6_phexdigit_fix.vpatch.mod6.sig

mod6: http://btcbase.org/log/2018-04-29#1806228 << >> http://www.mod6.net/2018/April/30/phexdigit_post.txt >> http://www.mod6.net/2018/April/30/mod6_phexdigit_fix.vpatch >> http://www.mod6.net/2018/April/30/mod6_phexdigit_fix.vpatch.mod6.sig ☝︎☟︎

mircea_popescu: ckanggirl i find your fore...sight perfectly acceptable.

a111: Logged on 2018-03-28 21:08 spyked: my v-fu really leaves to be desired. so: http://btcbase.org/log/2018-03-28#1790147 <-- patch: http://lucian.mogosanu.ro/v/patches/vdiff_lib_xalloc_static_xnmalloc.vpatch and seal: http://lucian.mogosanu.ro/v/seals/vdiff_lib_xalloc_static_xnmalloc.vpatch.spyked.sig --> so I based those on vdiff_fixes_newline_gcc (parent of vdiff_keccak in http://btcbase.org/patches?patchset=vtools ) and while the patch verifies, it doesn't show up in my

spyked: my v-fu really leaves to be desired. so: http://btcbase.org/log/2018-03-28#1790147 <-- patch: http://lucian.mogosanu.ro/v/patches/vdiff_lib_xalloc_static_xnmalloc.vpatch and seal: http://lucian.mogosanu.ro/v/seals/vdiff_lib_xalloc_static_xnmalloc.vpatch.spyked.sig --> so I based those on vdiff_fixes_newline_gcc (parent of vdiff_keccak in http://btcbase.org/patches?patchset=vtools ) and while the patch verifies, it doesn't show up in my ☝︎☟︎

a111: Logged on 2018-03-15 00:44 hanbot: phf fwiw btcbase.org/data/vtools/vtools_vdiff_sha.vpatch.phf.sig 404s

hanbot: phf fwiw btcbase.org/data/vtools/vtools_vdiff_sha.vpatch.phf.sig 404s ☟︎

mod6: Alright, fixed. Link is the same as before: http://www.mod6.net/pizarro/pizarro_charter_genesis.vpatch.mod6.sig

mod6: Here's my detached sig: http://www.mod6.net/pizarro/pizarro_charter_genesis.vpatch.mod6.sig

a111: Logged on 2018-01-25 06:00 hanbot: http://btcbase.org/log/2018-01-25#1775981 >> can grab http://thewhet.net/testickle/mp-wp_genesis.vpatch & http://thewhet.net/testickle/mp-wp_genesis.vpatch.hanbot.sig ; pubkey's on about page if you need it.

hanbot: http://btcbase.org/log/2018-01-25#1775981 >> can grab http://thewhet.net/testickle/mp-wp_genesis.vpatch & http://thewhet.net/testickle/mp-wp_genesis.vpatch.hanbot.sig ; pubkey's on about page if you need it. ☝︎☟︎☟︎

a111: Logged on 2018-01-20 11:37 spyked: ftr, asciilifeform's ch4 seal (grabbed from http://www.loper-os.org/pub/ffa/ffa_ch4_ffacalc.vpatch.asciilifeform.sig ) also seems to be binary (found it while double-checking my copies)

spyked: ftr, asciilifeform's ch4 seal (grabbed from http://www.loper-os.org/pub/ffa/ffa_ch4_ffacalc.vpatch.asciilifeform.sig ) also seems to be binary (found it while double-checking my copies) ☟︎

spyked: http://btcbase.org/log/2018-01-19#1773176 <-- yikes! sorry phf, I fixed it (and double-checked, as I should have in the first place) --> http://lucian.mogosanu.ro/v/seals/ffa_ch4_ffacalc.vpatch.spyked.sig ☝︎

asciilifeform: !~later tell phf plox to snarf http://www.loper-os.org/pub/ffa/ffa_ch3_shifts.vpatch.benvulpes.sig .

asciilifeform: !~later tell phf plox to snarf http://www.loper-os.org/pub/ffa/ffa_ch4_ffacalc.vpatch.benvulpes.sig , ty

asciilifeform: !~later tell phf plox to snarf : http://www.loper-os.org/pub/ffa/ffa_ch1_genesis.vpatch.spyked.sig

asciilifeform: !~later tell phf plox to snarf: 3) http://www.loper-os.org/pub/ffa/ffa_ch4_ffacalc.vpatch.peterl.sig . ty

asciilifeform: !~later tell phf plox to snarf: 1) http://www.loper-os.org/pub/ffa/ffa_ch2_logicals.vpatch.peterl.sig 2) http://www.loper-os.org/pub/ffa/ffa_ch3_shifts.vpatch.peterl.sig

ben_vulpes: while i wait for the mailing list to process my latest note, please note that the sig attached in http://btcbase.org/log/2017-12-24#1758230 needs renaming to `ben_vulpes_excise_hash_truncation.vpatch.ben_vulpes.sig' ☝︎

mircea_popescu: see, the SELECTION of .sigs you see is not promised to cover the whole space!

asciilifeform: mirrored at http://www.loper-os.org/pub/ffa/ffa_ch1_genesis.vpatch.diana_coman.sig , http://www.loper-os.org/pub/ffa/ffa_ch2_logicals.vpatch.diana_coman.sig , http://www.loper-os.org/pub/ffa/ffa_ch3_shifts.vpatch.diana_coman.sig . congrats to diana_coman , first graduate of ch1-ch3 !

asciilifeform: !~later tell phf plox to intern http://www.loper-os.org/pub/mpi/ffa_ch1_genesis.vpatch.benvulpes.sig

asciilifeform: !~later tell phf plox to intern http://www.loper-os.org/pub/ffa/ffa_ch1_genesis.vpatch.peterl.sig

a111: Logged on 2017-12-07 11:24 mircea_popescu: mod6 mind adding the "no clearsigned material in patches -- you got the .sig for that" and "no '--- ' anywhere, you have been warned" rules to it ; and phf / everyone mind making it stick ?

phf: diana_coman: your mpi_second_cut.vpatch.asciilifeform.sig links to http://dianacoman.com/vpatches/mpi-genesis.vpatch.asciilifeform.sig

mircea_popescu: diana_coman you'd make a new genesis, for eucrypt, and patch it with mpi. this patch will share no .sigs with the other mpi it is text-identical to

mircea_popescu: mod6 mind adding the "no clearsigned material in patches -- you got the .sig for that" and "no '--- ' anywhere, you have been warned" rules to it ; and phf / everyone mind making it stick ? ☟︎

asciilifeform: cab965c726b50f98e3d74a1be4b119dcf65c9900749d33707525c94c1432b855f2e3d39043a4fbb9d907fe3853242fccd773017a2d3763bdd76fbc9a6f6a01dd mpi_second_cut.vpatch.asciilifeform.sig

asciilifeform: b05ca401ecfe3f5bfa8794377241db12f5dc302fc552075ab3c78e7379b5b6a838af6d37d725798556cb27bc57213c388c92fa9b06f2e9233264b3ea8f89824f mpi-genesis.vpatch.asciilifeform.sig

a111: Logged on 2017-12-06 20:12 asciilifeform: http://www.loper-os.org/pub/mpi/mpi-genesis.vpatch http://www.loper-os.org/pub/mpi/mpi-genesis.vpatch.asciilifeform.sig for the l0gz.

mircea_popescu: they utterly don't belong there. you got a .sig mechanism for this.

asciilifeform: http://www.loper-os.org/pub/mpi/mpi-genesis.vpatch http://www.loper-os.org/pub/mpi/mpi-genesis.vpatch.asciilifeform.sig for the l0gz. ☟︎

a111: 217 results for "\".sig\"", http://btcbase.org/log-search?q=%22.sig%22

mircea_popescu: !#s ".sig"

asciilifeform: mv patches/mpi-genesis.vdiff patches/mpi-genesis.vpatch ; mv .seals/mpi-genesis.asciilifeform.sig .seals/mpi-genesis.vpatch.asciilifeform.sig

asciilifeform: sha512(mpi_second_cut.vpatch.asciilifeform.sig) : 7b14150fd5100dc90f7130a491214fceda5984fdad20491487d45727c4be88885dc9d9245e7f1bee30fa236e1e774e03f6cba8f34ccc4508eaed0df53af329a0

mod6: asciilifeform: you may want to update the link to my V in this blog post (http://www.loper-os.org/?p=1545) as it's old. This is the latest (from the foundation site): http://thebitcoin.foundation/v/V-20170317.tar.gz (and corresponding sig file): http://thebitcoin.foundation/v/V-20170317.tar.gz.mod6.sig

a111: Logged on 2017-11-19 14:42 asciilifeform: http://btcbase.org/log/2017-11-19#1740653 >> neato! >>> http://www.loper-os.org/pub/ro_eng_genesis.vpatch + http://www.loper-os.org/pub/ro_eng_genesis.vpatch.asciilifeform.sig .

asciilifeform: http://btcbase.org/log/2017-11-19#1740653 >> neato! >>> http://www.loper-os.org/pub/ro_eng_genesis.vpatch + http://www.loper-os.org/pub/ro_eng_genesis.vpatch.asciilifeform.sig . ☝︎☟︎

phf: http://www.sigact.org/Prizes/Knuth/

ben_vulpes: por favor, output de: gpg --verify .seals/asciilifeform_add_verifyall_option.vpatch.ben_vulpes.sig patches/asciilifeform_add_verifyall_option.vpatch

CluelessNoob: WARNING: asciilifeform_add_verifyall_option.vpatch.ben_vulpes.sig is an INVALID seal for asciilifeform_add_verifyall_option.vpatch!

jurov: um...signing that would be problematic, then

a111: Logged on 2016-08-07 18:22 hanbot: so in V99995 testing, it'd seem the asciilifeform_add_verifyall_option.vpatch.asciilifeform.sig is "invalid", i imagine 'cause of something to do with stan's old key? and deedbot only spits the current, which i have. i don't see the old one on btcalpha either, anyone have an idea fo' me?

mircea_popescu: in case not found yet : "mod6.sig\n\n\nT" vs ".mod6.sig</a>\n\nT"

a111: Logged on 2017-04-24 06:12 pete_dushenski: "WARNING: asciilifeform_blackhole_reads.vpatch.asciilifeform.sig is an INVALID seal for asciilifeform_blackhole_reads.vpatch!" << anyone else seen this error ? my vtron is barfing this up even though my gpgtron says it's a good sig.

pete_dushenski: "WARNING: asciilifeform_blackhole_reads.vpatch.asciilifeform.sig is an INVALID seal for asciilifeform_blackhole_reads.vpatch!" << anyone else seen this error ? my vtron is barfing this up even though my gpgtron says it's a good sig. ☟︎☟︎

phf: curl http://btcbase.org/patches/asciilifeform_wires_rev1/file -o patches/asciilifeform_wires_rev1.vpatch; curl http://btcbase.org/patches/asciilifeform_wires_rev1/seal/asciilifeform -o seals/asciilifeform_wires_rev1.vpatch.asciilifeform.sig

mod6: a cautionary note to anyone who is going to use my V to press with wires_rev1 (http://therealbitcoin.org/ml/btc-dev/2017-February/000251.html), be sure to name the seal as such or it won't get picked up in the flow (in the new, forthcoming version 99994) as such: asciilifeform_wires_rev1.vpatch.asciilifeform.sig

asciilifeform: to rewrite formally, a cask is a C = sig_h1(sig_h2(sig_h3(.....sig_m('i'll mine a tx for q btc/kb...'))); tx author signs, author_sig(my_tx + C)

asciilifeform: ..sign.

mod6: So basically, the deal is, that when using TRB, I have one user in my wot, say "mod6", and I drop out a vpatch from the flow, say "asciilifeform_dnsseed_snipsnip.vpatch" by moving it's seal to "asciilifeform_dnsseed_snipsnip.vpatch.mod6.sig.foobar", then I expected a few things to happen.

ben_vulpes: mircea_popescu: would you humor me and upload a genesis.vpatch.mircea_popescu.sig and let me know what your mp_wp does?

adlai: ben_vulpes: dunno how this happened, but the link to http://cascadianhacker.com/wp-content/uploads/2016/12/hashes_and_errorsvpatchben_vulpes.sig is missing a bunch of periods

mod6: <+ben_vulpes> no, that's death() ing on a patch for which the system had valid seals, yours and mine. << this i dont agree with -- from a technical perspective. it looks to me that girl had "ascii and mod6" in .wot, and when it came across Mr. P.'s genesis .sig, it honked.

mod6: what I should do, is ignore that sig, and continue iterating, collecting up all of the mod6 .sigs and then creating a v-tree from just those alone.

asciilifeform: mircea_popescu: the current setup (with the patch.nickname.sig) is an artifact of the idiocy of pgp, where one cannot take the signature and extract a hash from it with which you can look up the patch from a manifest of patch hashes in O(NlogN)

a111: Logged on 2016-01-18 15:35 ascii_butugychag: jurov: theoretically you can avoid using the name prior to .sig, but then you have to check ALL seals agains ALL patches ALWAYS and this is O(N^2)

asciilifeform: iterating over patches is O(N^2) (unless the files are correctly named, patch.nickname.sig, which we do, but imho is a bit of a cheat)

asciilifeform: 2) http://nosuchlabs.com/fg/fg-genesis.vpatch.asciilifeform.sig