Skip to content

Ja4r failed when Ja3 setting existed #411

@ngloom

Description

@ngloom

Description

const initCycleTLS = require('cycletls');

(async () => {
  const cycleTLS = await initCycleTLS();

  // ios 26.2 ja3 & ja4 settting 
  const response = await cycleTLS('https://tls.peet.ws/api/all', {
  ja3: "771,4866-4867-4865-49196-49195-52393-49200-49199-52392-49162-49161-49172-49171-157-156-53-47-49160-49170-10,0-23-65281-10-11-16-5-13-18-51-45-43-27,4588-29-23-24-25,0",
  ja4r: 't13d2013h2_000a,002f,0035,009c,009d,1301,1302,1303,c008,c009,c00a,c012,c013,c014,c02b,c02c,c02f,c030,cca8,cca9_0005,000a,000b,000d,0012,0017,001b,002b,002d,0033,ff01_0403,0804,0401,0503,0805,0805,0501,0806,0601,0201'
  });

  const data = await response.json();
  // console.log(data);
  console.log('ja3', data.tls.ja3)
  console.log('ja3_hash', data.tls.ja3_hash)
  console.log('ja4', data.tls.ja4)
  console.log('ja4_r', data.tls.ja4_r)

  await cycleTLS.exit();
})();

Issue Type

Bug

Operating System

Linux

Node Version

Node 20.x

Golang Version

Other

Relevant Log Output

--------- when only setting ja3 , ja3_hash is correct 
ja3 771,4866-4867-4865-49196-49195-52393-49200-49199-52392-49162-49161-49172-49171-157-156-53-47-49160-49170-10,0-23-65281-10-11-16-5-13-18-51-45-43-27,4588-29-23-24-25,0
ja3_hash ecdf4f49dd59effc439639da29186671
ja4 t12d2013h2_a09f3c656075_f87fe8abb585
ja4_r t12d2013h2_000a,002f,0035,009c,009d,1301,1302,1303,c008,c009,c00a,c012,c013,c014,c02b,c02c,c02f,c030,cca8,cca9_0005,000a,000b,000d,0012,0017,001b,002b,002d,0033,ff01_0403,0503,0603,0804,0805,0806,0401,0501,0601,0203,0201

--------  when only setting ja4r , ja4 hash is correct 
ja3 771,10-47-53-156-157-4865-4866-4867-49160-49161-49162-49170-49171-49172-49195-49196-49199-49200-52392-52393,0-5-10-11-13-18-23-27-43-45-51-65281-16,29-29-23-24,0
ja3_hash 9a4734e8587ab29a204820cabf735ad3
ja4 t13d2013h2_a09f3c656075_7f0f34a4126d
ja4_r t13d2013h2_000a,002f,0035,009c,009d,1301,1302,1303,c008,c009,c00a,c012,c013,c014,c02b,c02c,c02f,c030,cca8,cca9_0005,000a,000b,000d,0012,0017,001b,002b,002d,0033,ff01_0403,0804,0401,0503,0805,0805,0501,0806,0601,0201



--------- when both ja3 & ja4r setting existed , ja4 hash is incorrect 
ja3 771,4866-4867-4865-49196-49195-52393-49200-49199-52392-49162-49161-49172-49171-157-156-53-47-49160-49170-10,0-23-65281-10-11-16-5-13-18-51-45-43-27,4588-29-23-24-25,0
ja3_hash ecdf4f49dd59effc439639da29186671
ja4 t12d2013h2_a09f3c656075_f87fe8abb585
ja4_r t12d2013h2_000a,002f,0035,009c,009d,1301,1302,1303,c008,c009,c00a,c012,c013,c014,c02b,c02c,c02f,c030,cca8,cca9_0005,000a,000b,000d,0012,0017,001b,002b,002d,0033,ff01_0403,0503,0603,0804,0805,0806,0401,0501,0601,0203,0201

Metadata

Metadata

Assignees

Labels

triageThis ticket will be looked at shortly

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions