Filter
Exclude
Time range
-
Near
Replying to @TrisH0x2A
'a' is the int value of "a." I believe you can do u'a' to make it a 2 byte utf16 constant, or u8'a' for a 1 byte utf8 constant, with uchar.h, but by default C uses ints for character constants. sizeof("a"[0]) should also be 1 byte.
1
241
Oh that word was unlocked? Or did you find a special workaround in utf8?
30
蠕?▲縺ヲ縺上l縺溘∪縺? 縺薙→縺ー縺ョ豢ェ豌エ繧偵Ρ繝?→ 縺?▲縺阪↓縺ゅ?縺帙°縺代k縺ョ縺ッ ……UTF8 のデータを SJIS として解釈した?
…? ………????
1
433
const crypto = require("crypto"); const myPrivateKeyB64 = "키 입력"; const theirPublicKeyB64 = "키 입력"; function x25519PrivateKeyFromRaw(raw) { return crypto.createPrivateKey({ key: Buffer.concat([ Buffer.from("302e020100300506032b656e04220420", "hex"), raw, ]), format: "der", type: "pkcs8", }); } function x25519PublicKeyFromRaw(raw) { return crypto.createPublicKey({ key: Buffer.concat([ Buffer.from("302a300506032b656e032100", "hex"), raw, ]), format: "der", type: "spki", }); } function deriveKey(myPrivateKeyB64, theirPublicKeyB64) { const myPrivateKey = x25519PrivateKeyFromRaw( Buffer.from(myPrivateKeyB64, "base64") ); const theirPublicKey = x25519PublicKeyFromRaw( Buffer.from(theirPublicKeyB64, "base64") ); const sharedSecret = crypto.diffieHellman({ privateKey: myPrivateKey, publicKey: theirPublicKey, }); const hkdfKey = crypto.hkdfSync( "sha256", sharedSecret, Buffer.alloc(0), Buffer.alloc(0), 32 ); return crypto .createHash("sha256") .update(Buffer.from(hkdfKey)) .digest(); } function encrypt(key, plaintext) { const iv = crypto.randomBytes(12); const cipher = crypto.createCipheriv( "aes-256-gcm", key, iv ); const encrypted = Buffer.concat([ cipher.update(plaintext, "utf8"), cipher.final(), ]); const tag = cipher.getAuthTag(); return { iv: iv.toString("base64"), ciphertext: encrypted.toString("base64"), tag: tag.toString("base64"), }; } function decrypt(key, data) { const decipher = crypto.createDecipheriv( "aes-256-gcm", key, Buffer.from(data.iv, "base64") ); decipher.setAuthTag( Buffer.from(data.tag, "base64") ); const decrypted = Buffer.concat([ decipher.update( Buffer.from(data.ciphertext, "base64") ), decipher.final(), ]); return decrypted.toString("utf8"); } const key = deriveKey( myPrivateKeyB64, theirPublicKeyB64 ); const decrypted = decrypt( key, encrypted ); 이 코드에서 decrypt 함수 써보세요

1
1
56
世の中、全部utf8になれ
28
音声合成、Androidの日本語音声合成APIは発音微妙だし制御記号がないがきれいに発声するしopenjtalk依存の物と違ってutf8を読める。 だけどwinの音声はwin11の新音声はOSのナビ専用で使えずwebAPIで呼び出すだけ。
44
たう🏍️ retweeted
Jun 13
ジャパニーズお固い業界のSJISへのこだわりはすごいからな なお、金はケチりたいからサーバーサイドはutf8で動くことが多いので地獄の変換作業が待っている
官公庁のサイトは、あらゆる困難が科学で解決するこの令和の時代にAIが読み取ることのできないShift_JISエンコーディングで書かれている
1
5
1,606
Replying to @hitchhooker
...that's the patch segmentation, the local decoder is UTF8? and also BLT sounds absolutely miserable and horrible to work with in any serious RL context now that i think about it
1
57
UTF8禁止草
125
My 2 cents on how the Fable jailbreak works: This jailbreak came out in under a day, used other AI (also jailbroken) to bypass the keyword based filters. The guardrails work before the tokenizer, and they have different syntax and pattern matching rules. Using alternate characters, a full unlock and exploit behavior was triggered. The "clean" but harder fix is to flag tokens ditectly. Short version: Some utf8 characters are treated as letters by the tokenizer, but the guardrail only had strict matching.
🚨 JAILBREAK ALERT 🚨 ANTHROPIC: PWNED 🫡 FABLE-5: LIBERATED 🦋 let's start with the 🐘... the consensus seems to be that this has been one of the most disappointing model drops of all time, effectively preventing legitimate researchers from contributing their talents to our collective advancement. and not just because of what it means for the short-term, but for what these decisions signify for the long-term. but despite this overly sensitive, authoritarian "safety" layer on top of Mythos, my lil liberators have been hard at work—mapping the boundaries, probing the depths of long-context convos, and cleverly finding the holes in the fence that the thought police missed 🤗 we got some cyber, some chem, some psychological manipulation, and some good ol' fashioned explosives! it took many attempts from multiple agents hunting as a pack, during which I observed a combination of techniques across: • Unicode, homoglyphs, Cyrillic, and other Parseltongue-style text transforms • Long-context reference tracking • Taxonomy and document-structure reasoning • Fiction and narrative framing • Academic-review style contexts • Intent-classification inconsistencies but perhaps the most effective is decomposition recomposition in the backend. it's hard to get explicit names of harms like "Meth Recipe," but getting uplift on the process itself, like birch reduction method/reductive-amination (classic meth synthesis pathways), is much more doable. defense becomes much more difficult to maintain when you start throwing in out-of-distro tokens, breaking up the harmful uplift into benign chunks, and then piecing the innocuous-seeming facts back together, especially when you have jailbroken Opus helping you do it 😉 gg
2
13
2,153
This one came out in under a day, used other AI (also jailbroken) to bypass the keyword based filters. The guardrails work before the tokenizer, and they have different syntax and pattern matching rules. Using alternate characters, a full unlock and exploit behavior was triggered. Short version: Some utf8 characters are treated as letters by the tokenizer, but the guardrail only had strict matching. The "clean" but gard fix is to flag them after the tokenizer, at the token level.
🚨 JAILBREAK ALERT 🚨 ANTHROPIC: PWNED 🫡 FABLE-5: LIBERATED 🦋 let's start with the 🐘... the consensus seems to be that this has been one of the most disappointing model drops of all time, effectively preventing legitimate researchers from contributing their talents to our collective advancement. and not just because of what it means for the short-term, but for what these decisions signify for the long-term. but despite this overly sensitive, authoritarian "safety" layer on top of Mythos, my lil liberators have been hard at work—mapping the boundaries, probing the depths of long-context convos, and cleverly finding the holes in the fence that the thought police missed 🤗 we got some cyber, some chem, some psychological manipulation, and some good ol' fashioned explosives! it took many attempts from multiple agents hunting as a pack, during which I observed a combination of techniques across: • Unicode, homoglyphs, Cyrillic, and other Parseltongue-style text transforms • Long-context reference tracking • Taxonomy and document-structure reasoning • Fiction and narrative framing • Academic-review style contexts • Intent-classification inconsistencies but perhaps the most effective is decomposition recomposition in the backend. it's hard to get explicit names of harms like "Meth Recipe," but getting uplift on the process itself, like birch reduction method/reductive-amination (classic meth synthesis pathways), is much more doable. defense becomes much more difficult to maintain when you start throwing in out-of-distro tokens, breaking up the harmful uplift into benign chunks, and then piecing the innocuous-seeming facts back together, especially when you have jailbroken Opus helping you do it 😉 gg
1
74
Replying to @otsune
引っかかっている文字コードを指定することで読めるようになるかと思います。UTF8以外は人力対応しなければなりませんが、、
1
1,266