175 entries in 0.551s
BingoBoingo:
http://archive.is/3nQJt << Argentina is fatwah'd and even more isolated than Uruguay from an internet perspective, but here's what they offer for 2U 10mbps burstable
symmetric (LACNIC so IP address poor). If Gbps can reasonable be had in Baltimore...
trinque: ah, that's the error then, I thought it was already the
symmetric.
BingoBoingo: A
symmetric pipe would have been much more expensive
mircea_popescu: trinque i'm not that in touch, but iirc it was a good deal as
symmetric.
trinque: what was it, they paid 3x for the
symmetric?
a111: Logged on 2018-10-31 18:27 asciilifeform: ( iirc
symmetric keys are supplied, per protocol, by client, so not an issue there )
mircea_popescu: i agree with that, but im not sure
symmetric cipher hdd wins that much.
a111: Logged on 2018-04-12 18:48 asciilifeform: mircea_popescu: blake2 is bernstein's hash ( consists of a slightly modified chacha, his
symmetric algo )
zx2c4: transport layer is all
symmetric crypto
zx2c4: seems like there are many places and interesting ways to optimize at this point. lots of neat creative work coming out. but that with aes and whatnot, we're in a pretty good place in terms of
symmetric crypto
zx2c4: so anyway, im less concerned about
symmetric cryptography than other things
a111: Logged on 2017-08-22 12:02 asciilifeform: the other lul in the 'noise protocol' is the use of
symmetric ciphers
mircea_popescu: the claim is "The following protocols and primitives are used: ChaCha20 for
symmetric encryption, authenticated with Poly1305, using RFC7539's AEAD construction; Curve25519 for ECDH; BLAKE2s for hashing and keyed hashing, described in RFC7693; SipHash24 for hashtable keys; HKDF for key derivation, as described in RFC5869"
mircea_popescu: anyway, speaking of roman numeral systems, the dumbest thing about writing is that , doesn't come with a
symmetric-comma.
mircea_popescu: so basically, the summary would be, that fellow took
symmetric cyphering, sawed it open, used half of the parts for an ad-hoc rsa padding scheme, and implemented the whole kaboodle in python./
mircea_popescu: "# encrypttoct(): Encrypts a sequence of blocks of constant size of mb bits, on the one side applying the for RSA known method of transformation on the individual blocks, on the other side using certain commonly in
symmetric block encryption employed methods, namely plaintext-and-ciphertext- block-chaining (with a pseudo-random IV). A sequence of blocks that stems from the plaintext of the user can thus be encrypted with RSA
mircea_popescu: asciilifeform it's not very clear to me how your x=y things work, BUT, if you had told me in 2016 that you intend to delay c-s ada impl by 1-2-n years to wait for ffa i'd have told you
symmetric cipher really dun need ffa for any reason and eulora won't wait into 2018 for it etc.
mircea_popescu: the deeper problem here is that the evolution of warfare has rendered a
symmetric cipher useless. for the launch codes or how you call it we're mostly in consensus to use pure rsa, if memory serves, and for the prattle of eg game server, serpent will do.
mircea_popescu: dja see why i'd muchly prefer a native tmsr.rsa length
symmetric cypher rather than this nonsense ?
a111: Logged on 2017-09-28 09:39 mircea_popescu: not necessarily the specific example. but yes,
symmetric cipher always reduces to a "parametrized otp".
mircea_popescu: not necessarily the specific example. but yes,
symmetric cipher always reduces to a "parametrized otp".
☟︎ a111: Logged on 2016-06-06 21:10 mircea_popescu: o btw asciilifeform wanna hear my inept
symmetric encryption scheme ?
a111: Logged on 2016-05-31 19:51 asciilifeform: not a single
symmetric cipher other than otp has ever been proven to be worth a sparrow's fart.
a111: Logged on 2017-07-22 22:40 mircea_popescu:
http://btcbase.org/log/2017-07-22#1689243 << depends what you mean by "rsa encrypted message". a) current rsa "encryption" as implemented by koch-gpg et al consists of encrypting a
symmetric key. trivial to test this against a number of rsa keys. b) conceivably item will include a courtesy key fp to help you know.
mircea_popescu:
http://btcbase.org/log/2017-07-22#1689243 << depends what you mean by "rsa encrypted message". a) current rsa "encryption" as implemented by koch-gpg et al consists of encrypting a
symmetric key. trivial to test this against a number of rsa keys. b) conceivably item will include a courtesy key fp to help you know.
☝︎☟︎ Framedragger: mircea_popescu: yeah, i suppose i follow. hrr, ok i'll need to see what in particular was revealed/claimed in #t. besides "it's snake oil!"; i do hope that if/when aes is broken, #t doesn't go out saying "#t said all
symmetric crypto is snakeoil! plagiarism!!"
thestringpuller: "After further investigation, it turned out that the two AIs were communicating using a novel
symmetric key cipher, and the key that ended up being uncrackable by the third AI was simply '12345', the kind of password an idiot would have on his luggage."
a111: Logged on 2017-02-03 05:46 phf: it's a combination of passphrase mangling (by default sha-1) to derive the key, and
symmetric algorithm (be default aes-128) to encrypt the privkey. i don't think we had any discussion about this..
phf: it's a combination of passphrase mangling (by default sha-1) to derive the key, and
symmetric algorithm (be default aes-128) to encrypt the privkey. i don't think we had any discussion about this..
☟︎ phf: unrelatedly i was wondering if gpg passwords are promisetronic. how do they even work? there's some
symmetric encryption scheme used to encrypt the privkey, or can passwords be somehow integrated into rsa scheme?
Framedragger: jesus you guys, you realise all those deedbot messages are still internally encrypted with
symmetric aes ('session key') right? and you think the lowest-hanging fruit is fingerprint? ok i guess
Framedragger: nonce + hmac? ah, but, hmac uses
symmetric crypto oh noes :/
mircea_popescu: i'm also not entirely certain a
symmetric cypher or perhaps hash-and-rehash scheme won';t be better.
phf: asciilifeform: you're more attached to dismissing
symmetric, then i am to preserving it
phf: each slave vm gets a random int id and a
symmetric key, master store int<->
symmetric key in a binary tree. packet comes in <int><sig>, you get the
symmetric key for int and use it to verify sig
phf: so is a
symmetric key if you have unique
symmetric key for each pairing
phf: a
symmetric-key algorithm is my point, say aes, since i don't know any better
mircea_popescu: anyway. the only way in which the scheme you discuss worked was to prevent effectual use of
symmetric key crypto, and it's altogether doubtful people needed help for that.
mircea_popescu: o btw asciilifeform wanna hear my inept
symmetric encryption scheme ?
☟︎ a111: Logged on 2016-06-03 20:47 Framedragger: (re. pkcs#11, because e.g. that substring-attack is only meant to be against
symmetric keys stored in that shitformat, but since e.g. ECDSA keypair's secret logarithm "is just stored as 32-byte scalar value [it's not meant to be stored that way there, but is, because reasons], [...] extract-key-from-key can be used to successively reveal chunks of that scalar value.")
Framedragger: (re. pkcs#11, because e.g. that substring-attack is only meant to be against
symmetric keys stored in that shitformat, but since e.g. ECDSA keypair's secret logarithm "is just stored as 32-byte scalar value [it's not meant to be stored that way there, but is, because reasons], [...] extract-key-from-key can be used to successively reveal chunks of that scalar value.")
☟︎ Framedragger: (their "hybrid implementation" assumes a good
symmetric-key cipher..)
a111: Logged on 2016-02-02 15:58 ascii_butugychag: anybody got a favourite
symmetric cipher, incidentally ?