-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.xml
763 lines (753 loc) · 47.4 KB
/
index.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
<?xml version='1.0' encoding='UTF-8'?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
<channel>
<title>@hyperdbg - Telegram group archive</title>
<link>https://tg-archive.hyperdbg.org</link>
<description>Public archive of HyperDbg Telegram messages.</description>
<docs>http://www.rssboard.org/rss-specification</docs>
<generator>tg-archive 1.2.1</generator>
<lastBuildDate>Fri, 11 Oct 2024 13:24:46 +0000</lastBuildDate>
<item>
<title>@honorary_bot on 2024-10-11 13:15:36+00:00 (#8086)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8086</link>
<description>Then you might find this article curious :)
https://pulsedbg.com/codequal.html</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8086</guid>
<pubDate>Fri, 11 Oct 2024 13:15:36 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-10-11 13:14:54+00:00 (#8085)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8085</link>
<description>The problem for HyperDbg is that, as we used RtlZeroMemory in almost all of the VM-exit handling routines, this function (and probably other functions) use XMM registers to zero the memory (to speed up). I couldn't find a way of forcing MSVC not to use XMM registers for this purpose. So, I think this approach as you mentioned, won't work for HyperDbg.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8085</guid>
<pubDate>Fri, 11 Oct 2024 13:14:54 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-10-11 13:12:05+00:00 (#8084)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8084</link>
<description>I know it wouldn't work for you, but my approach was to ditch any sse in the hypervisor, so no xmm context save and restore needed</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8084</guid>
<pubDate>Fri, 11 Oct 2024 13:12:05 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-10-11 13:10:05+00:00 (#8083)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8083</link>
<description>I wrote the patch for this bug which is context-switching (saving and restoring) XMM registers in VM-exits and VM-entries. Though, I'm still unsure whether to apply it or not, since it might have an overall negative influence on the performance of the HyperDbg as we need to save and restore all XMM registers each time a VM-exit happens.
What do you guys think/suggest?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8083</guid>
<pubDate>Fri, 11 Oct 2024 13:10:05 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-10-11 13:09:58+00:00 (#8082)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8082</link>
<description>Guys, we need to have a discussion in the group about whether fixing or not fixing the issue mentioned here:
https://github.com/HyperDbg/HyperDbg/issues/468</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8082</guid>
<pubDate>Fri, 11 Oct 2024 13:09:58 +0000</pubDate>
</item>
<item>
<title>@HyperDbgChannel on 2024-10-11 11:31:23+00:00 (#8081)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8081</link>
<description>HyperDbg v0.10.2 is released!
This release comes with lots of bugfixes and improved stability, check it out here:
https://github.com/HyperDbg/HyperDbg/releases/tag/v0.10.2</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8081</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://github.com/HyperDbg/HyperDbg/releases/tag/v0.10.2" length="0" type="text/html"/>
<pubDate>Fri, 11 Oct 2024 11:31:23 +0000</pubDate>
</item>
<item>
<title>@7425036241 on 2024-10-10 03:32:42+00:00 (#8080)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8080</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8080</guid>
<pubDate>Thu, 10 Oct 2024 03:32:42 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-10-09 17:40:25+00:00 (#8079)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8079</link>
<description>So, if you put a !monitor hook on a range in which one or some of pages are not residing in RAM, then HyperDbg shows you error. In that case, you need to use the '.pagein' command to force Windows to bring those pages into the RAM.
https://docs.hyperdbg.org/commands/meta-commands/.pagein</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8079</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://docs.hyperdbg.org/commands/meta-commands/.pagein" length="0" type="text/html"/>
<pubDate>Wed, 09 Oct 2024 17:40:25 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-10-09 17:37:30+00:00 (#8077)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8077</link>
<description>But just keep in mind that putting a !monitor hook on a long range of memory is only possible if all of those pages are available at RAM (not paged-out).</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8077</guid>
<pubDate>Wed, 09 Oct 2024 17:37:30 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-10-09 17:36:17+00:00 (#8076)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8076</link>
<description>Yes. That's what the '!monitor' command is designed for.
https://docs.hyperdbg.org/commands/extension-commands/monitor</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8076</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://docs.hyperdbg.org/commands/extension-commands/monitor" length="0" type="text/html"/>
<pubDate>Wed, 09 Oct 2024 17:36:17 +0000</pubDate>
</item>
<item>
<title>@instw0 on 2024-10-09 17:14:27+00:00 (#8075)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8075</link>
<description>can I put a read/execute hook(!epthook) on a section of code (for example, the text ntoskrnl section)</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8075</guid>
<pubDate>Wed, 09 Oct 2024 17:14:27 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-10-07 17:31:53+00:00 (#8074)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8074</link>
<description>But if you use the 't' command, then you just go to the next instruction (just like windbg, x64dbg).</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8074</guid>
<pubDate>Mon, 07 Oct 2024 17:31:53 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-10-07 17:31:16+00:00 (#8073)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8073</link>
<description>If you use the 'i' command, then in the interrupt/exception/fault handler from IDT.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8073</guid>
<pubDate>Mon, 07 Oct 2024 17:31:16 +0000</pubDate>
</item>
<item>
<title>@instw0 on 2024-10-07 17:17:25+00:00 (#8072)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8072</link>
<description>if I use "i" for tracing and get to the instruction causing the exception... where will I be directed by the next step? in the exception handler?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8072</guid>
<pubDate>Mon, 07 Oct 2024 17:17:25 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-10-06 13:05:14+00:00 (#8071)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8071</link>
<description>I tested the patch you made, and it works as expected. It makes sense that the crash occurred because we weren't properly restoring the SS, DS, FS, and other segments for a 32-bit program. Your patch (PR) seems to have resolved the issue. 👍</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8071</guid>
<pubDate>Sun, 06 Oct 2024 13:05:14 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-10-06 12:20:48+00:00 (#8070)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8070</link>
<description>[discord] <ohault> Almost all startups in this space have been acquired by big cloud players - https://www.nextplatform.com/2022/09/12/why-arent-there-software-defined-numa-servers-everywhere/amp/</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8070</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://www.nextplatform.com/2022/09/12/why-arent-there-software-defined-numa-servers-everywhere/amp/" length="0" type="text/html"/>
<pubDate>Sun, 06 Oct 2024 12:20:48 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-10-06 10:50:19+00:00 (#8069)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8069</link>
<description>[discord] <ohault> [reply]: It’s a broader concept, but and I guess we can see introspection also as such a « hardware extensions » to provide capabilities for inspecting, monitoring, debugging, …</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8069</guid>
<pubDate>Sun, 06 Oct 2024 10:50:19 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-10-06 10:49:25+00:00 (#8068)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8068</link>
<description>Too much effort for questionable results</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8068</guid>
<pubDate>Sun, 06 Oct 2024 10:49:25 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-10-06 10:48:45+00:00 (#8067)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8067</link>
<description>I guess I've explained why :)</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8067</guid>
<pubDate>Sun, 06 Oct 2024 10:48:45 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-10-06 10:48:06+00:00 (#8066)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8066</link>
<description>[discord] <ohault> I don’t know yet any open source project leveraging this concept</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8066</guid>
<pubDate>Sun, 06 Oct 2024 10:48:06 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-10-06 10:47:39+00:00 (#8065)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8065</link>
<description>I mean sure, you can try that</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8065</guid>
<pubDate>Sun, 06 Oct 2024 10:47:39 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-10-06 10:46:44+00:00 (#8064)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8064</link>
<description>[discord] <ohault> But this concept of a tiny and transparent type-1 hypervisor for software hardware extensions, is the point I would like to underline</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8064</guid>
<pubDate>Sun, 06 Oct 2024 10:46:44 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-10-06 10:45:53+00:00 (#8063)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8063</link>
<description>And it was designed to be a DRAM controller with optane memory on dram sticks. Even then, optane is a cache for RAM.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8063</guid>
<pubDate>Sun, 06 Oct 2024 10:45:53 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-10-06 10:45:08+00:00 (#8062)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8062</link>
<description>Theres only one technology with flash memory that works as RAM - Intel Optane DC</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8062</guid>
<pubDate>Sun, 06 Oct 2024 10:45:08 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-10-06 10:44:27+00:00 (#8061)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8061</link>
<description>This product doesn't mention it is a RAM replacement, it is still a storage device with "near DRAM speeds". So they use a hypervisor for memory "bubbling". Don't expect this method to be any near DRAM-like performance.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8061</guid>
<pubDate>Sun, 06 Oct 2024 10:44:27 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-10-06 10:42:13+00:00 (#8060)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8060</link>
<description>[discord] <ohault> [reply]: Very very interesting - https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/product/data-center-drives/ultrastar-dc-me200/product-manual-ultrastar-dc-me200.pdf</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8060</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/product/data-center-drives/ultrastar-dc-me200/product-manual-ultrastar-dc-me200.pdf" length="0" type="text/html"/>
<pubDate>Sun, 06 Oct 2024 10:42:13 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-10-06 10:36:09+00:00 (#8059)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8059</link>
<description>[discord] <ohault> [reply]: About CPU extensions, VT would be a required. About RAM extensions, I guess it is this very special product - https://www.westerndigital.com/en-ap/products/internal-drives/data-center-drives/ultrastar-dc-me200-nvme-ssd?sku=0TS1741 and I guess a special type 1 hypervisor should be used somewhere ?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8059</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://www.westerndigital.com/en-ap/products/internal-drives/data-center-drives/ultrastar-dc-me200-nvme-ssd?sku=0TS1741" length="0" type="text/html"/>
<pubDate>Sun, 06 Oct 2024 10:36:09 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-10-06 10:31:10+00:00 (#8058)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8058</link>
<description>While it would be possible to create a hypervisor, pre-popcnt CPUs have the old VTx (pre-EPT). You would need to trap #UD and emulate the needed instruction. But I'm afraid you'll be disappointed by the performance of this method, it will be very slow. The better idea would be to instrument target binaries directly.
As for the RAM from NVME - I'm afraid it doesn't work this way, maximum you can can get is a an analog of a page file, which is already implemented in the OS. DRAM traffic can not be magically turned into PCIe traffic, and also it's has a completely different inner workings.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8058</guid>
<pubDate>Sun, 06 Oct 2024 10:31:10 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-10-06 10:23:35+00:00 (#8057)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8057</link>
<description>[discord] <ohault> [reply]: I can think of earlier generations of Intel i7, but this concept could also add some system ram to the host from some fast local NVMEs (Western Digital had a product in the past leveraging this concept)</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8057</guid>
<pubDate>Sun, 06 Oct 2024 10:23:35 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-10-06 10:21:32+00:00 (#8056)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8056</link>
<description>How old is the target CPU? What model is it?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8056</guid>
<pubDate>Sun, 06 Oct 2024 10:21:32 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-10-06 10:18:22+00:00 (#8055)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8055</link>
<description>[discord] <ohault> [reply]: The idea behind « tiny » would be a very slim and transparent layer at boot time as Type1 hypervisor to just add to your existing hardware some additional capabilities emulated</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8055</guid>
<pubDate>Sun, 06 Oct 2024 10:18:22 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-10-06 10:15:42+00:00 (#8054)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8054</link>
<description>can u reproduce it? it works if we set the segment selector. I have sent a pr to dev.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8054</guid>
<pubDate>Sun, 06 Oct 2024 10:15:42 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-10-06 10:12:21+00:00 (#8053)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8053</link>
<description>Why not using QEMU?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8053</guid>
<pubDate>Sun, 06 Oct 2024 10:12:21 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-10-06 08:38:57+00:00 (#8052)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8052</link>
<description>[discord] <ohault> Could a tiny hypervisor emulate PopCnt and SSE4.2 on top of a legacy CPU without these instructions ?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8052</guid>
<pubDate>Sun, 06 Oct 2024 08:38:57 +0000</pubDate>
</item>
<item>
<title>@c12a12 on 2024-10-05 07:08:21+00:00 (#8051)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8051</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8051</guid>
<pubDate>Sat, 05 Oct 2024 07:08:21 +0000</pubDate>
</item>
<item>
<title>@invlpg on 2024-10-04 15:58:43+00:00 (#8050)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8050</link>
<description>🎉</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8050</guid>
<pubDate>Fri, 04 Oct 2024 15:58:43 +0000</pubDate>
</item>
<item>
<title>@HyperDbgChannel on 2024-10-04 15:58:23+00:00 (#8049)</title>
<link>https://tg-archive.hyperdbg.org/2024-10.html#8049</link>
<description>We are celebrating today as we've reached 200,000 lines of code! A big thank you to all the friends and contributors who made this possible! 🤗
https://github.com/HyperDbg/HyperDbg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-10.html#8049</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8049.jpg" length="150906" type="image/jpeg"/>
<pubDate>Fri, 04 Oct 2024 15:58:23 +0000</pubDate>
</item>
<item>
<title>@5668733022 on 2024-09-30 18:57:08+00:00 (#8048)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8048</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8048</guid>
<pubDate>Mon, 30 Sep 2024 18:57:08 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-29 17:44:24+00:00 (#8047)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8047</link>
<description>Yes</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8047</guid>
<pubDate>Sun, 29 Sep 2024 17:44:24 +0000</pubDate>
</item>
<item>
<title>@instw0 on 2024-09-29 16:30:31+00:00 (#8046)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8046</link>
<description>that is, to set the condition directly from the C code?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8046</guid>
<pubDate>Sun, 29 Sep 2024 16:30:31 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-29 16:14:27+00:00 (#8045)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8045</link>
<description>And this is where a Cpp code gets called when you step one instructions:
https://github.com/HyperDbg/HyperDbg/blob/38f7e747d688846c0d82e299338b66d7730e4559/hyperdbg/libhyperdbg/code/debugger/kernel-level/kernel-listening.cpp#L361
Add your condition here. ☝️</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8045</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://github.com/HyperDbg/HyperDbg/blob/38f7e747d688846c0d82e299338b66d7730e4559/hyperdbg/libhyperdbg/code/debugger/kernel-level/kernel-listening.cpp" length="0" type="text/html"/>
<pubDate>Sun, 29 Sep 2024 16:14:27 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-29 16:11:57+00:00 (#8044)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8044</link>
<description>This is the function responsible for sending instrumentation step-in requests:
https://github.com/HyperDbg/HyperDbg/blob/38f7e747d688846c0d82e299338b66d7730e4559/hyperdbg/libhyperdbg/code/debugger/core/steppings.cpp#L26</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8044</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://github.com/HyperDbg/HyperDbg/blob/38f7e747d688846c0d82e299338b66d7730e4559/hyperdbg/libhyperdbg/code/debugger/core/steppings.cpp" length="0" type="text/html"/>
<pubDate>Sun, 29 Sep 2024 16:11:57 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-29 16:08:47+00:00 (#8043)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8043</link>
<description>It's actually possible but I'm not sure if I export it properly for the regular usage. But, in case if you can compile HyperDbg's libhyperdbg, you need to check for your condition in the C code and recompile. It should be super easy.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8043</guid>
<pubDate>Sun, 29 Sep 2024 16:08:47 +0000</pubDate>
</item>
<item>
<title>@instw0 on 2024-09-29 16:04:34+00:00 (#8042)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8042</link>
<description>using the "i 10000" command, set a condition for checking the register, for example if @rip < 0x... then....</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8042</guid>
<pubDate>Sun, 29 Sep 2024 16:04:34 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-29 16:01:54+00:00 (#8041)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8041</link>
<description>You mean conditional stepping?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8041</guid>
<pubDate>Sun, 29 Sep 2024 16:01:54 +0000</pubDate>
</item>
<item>
<title>@instw0 on 2024-09-29 16:00:47+00:00 (#8040)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8040</link>
<description>is it possible to create any convenience when tracing " i"? example: if rip<0xffffffff then printf(....)</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8040</guid>
<pubDate>Sun, 29 Sep 2024 16:00:47 +0000</pubDate>
</item>
<item>
<title>@passEAC on 2024-09-29 15:48:37+00:00 (#8039)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8039</link>
<description>HI</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8039</guid>
<pubDate>Sun, 29 Sep 2024 15:48:37 +0000</pubDate>
</item>
<item>
<title>@passEAC on 2024-09-29 15:48:26+00:00 (#8038)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8038</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8038</guid>
<pubDate>Sun, 29 Sep 2024 15:48:26 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-28 21:22:43+00:00 (#8037)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8037</link>
<description>If yes, pls make sure to send a Pull Request to the HyperDbg repo (the 'dev' branch) to fix it.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8037</guid>
<pubDate>Sat, 28 Sep 2024 21:22:43 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-28 21:21:35+00:00 (#8036)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8036</link>
<description>Thanks for reporting it, I'll try to reproduce it.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8036</guid>
<pubDate>Sat, 28 Sep 2024 21:21:35 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-28 21:21:14+00:00 (#8035)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8035</link>
<description>And this change in setting segment selectors fix the issue?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8035</guid>
<pubDate>Sat, 28 Sep 2024 21:21:14 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 12:48:13+00:00 (#8034)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8034</link>
<description>and this program crash, throw GP</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8034</guid>
<pubDate>Sat, 28 Sep 2024 12:48:13 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 12:47:49+00:00 (#8033)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8033</link>
<description>compile to 32 bit</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8033</guid>
<pubDate>Sat, 28 Sep 2024 12:47:49 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 12:46:58+00:00 (#8032)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8032</link>
<description>photo_2024-09-28_12-46-58.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8032</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8032.jpg" length="22476" type="image/jpeg"/>
<pubDate>Sat, 28 Sep 2024 12:46:58 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 12:46:52+00:00 (#8031)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8031</link>
<description>while runing this code, we execute program obfuscation with vmp. like this</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8031</guid>
<pubDate>Sat, 28 Sep 2024 12:46:52 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 12:42:26+00:00 (#8030)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8030</link>
<description>photo_2024-09-28_12-42-26.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8030</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8030.jpg" length="36101" type="image/jpeg"/>
<pubDate>Sat, 28 Sep 2024 12:42:26 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 12:42:23+00:00 (#8029)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8029</link>
<description>ok. there is some code to reproduce this problem.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8029</guid>
<pubDate>Sat, 28 Sep 2024 12:42:23 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-28 11:25:59+00:00 (#8028)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8028</link>
<description>Not sure if I understand it correctly. Can you explain the scenario where this error might happen?
I assume you're trying to unload HyperDbg while it's in the middle of running a user-mode application?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8028</guid>
<pubDate>Sat, 28 Sep 2024 11:25:59 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 06:54:18+00:00 (#8027)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8027</link>
<description>and reset segment may solve this probram</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8027</guid>
<pubDate>Sat, 28 Sep 2024 06:54:18 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 06:53:41+00:00 (#8026)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8026</link>
<description>photo_2024-09-28_06-53-41.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8026</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8026.jpg" length="85399" type="image/jpeg"/>
<pubDate>Sat, 28 Sep 2024 06:53:41 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 06:52:25+00:00 (#8025)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8025</link>
<description>photo_2024-09-28_06-52-25.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8025</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8025.jpg" length="54332" type="image/jpeg"/>
<pubDate>Sat, 28 Sep 2024 06:52:25 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 06:52:05+00:00 (#8024)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8024</link>
<description>photo_2024-09-28_06-52-05.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8024</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8024.jpg" length="46559" type="image/jpeg"/>
<pubDate>Sat, 28 Sep 2024 06:52:05 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 06:51:17+00:00 (#8023)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8023</link>
<description>wow64 program may throw GP</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8023</guid>
<pubDate>Sat, 28 Sep 2024 06:51:17 +0000</pubDate>
</item>
<item>
<title>@yxxyz on 2024-09-28 06:49:26+00:00 (#8022)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8022</link>
<description>HvRestoreRegisters just reset fs gs gdtr idtr may be unsafe? i find that may cause program which runs wow64 and obfuscation with vmprotect crash.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8022</guid>
<pubDate>Sat, 28 Sep 2024 06:49:26 +0000</pubDate>
</item>
<item>
<title>@6695510551 on 2024-09-27 07:02:39+00:00 (#8021)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8021</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8021</guid>
<pubDate>Fri, 27 Sep 2024 07:02:39 +0000</pubDate>
</item>
<item>
<title>@7286665625 on 2024-09-25 13:34:31+00:00 (#8019)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8019</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8019</guid>
<pubDate>Wed, 25 Sep 2024 13:34:31 +0000</pubDate>
</item>
<item>
<title>@1185223315 on 2024-09-23 16:49:42+00:00 (#8018)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8018</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8018</guid>
<pubDate>Mon, 23 Sep 2024 16:49:42 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-21 12:11:21+00:00 (#8016)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8016</link>
<description>Based on our previous group discussions, it seems that the physical serial connection is not working properly. We've tried several times to port kdnet to HyperDbg but, unfortunately, have not succeeded yet. For now, only VMI Mode is available for a physical machine.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8016</guid>
<pubDate>Sat, 21 Sep 2024 12:11:21 +0000</pubDate>
</item>
<item>
<title>@instw0 on 2024-09-21 12:10:23+00:00 (#8015)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8015</link>
<description>"Attach to a remote machine"</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8015</guid>
<pubDate>Sat, 21 Sep 2024 12:10:23 +0000</pubDate>
</item>
<item>
<title>@instw0 on 2024-09-21 12:06:22+00:00 (#8014)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8014</link>
<description>full</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8014</guid>
<pubDate>Sat, 21 Sep 2024 12:06:22 +0000</pubDate>
</item>
<item>
<title>@instw0 on 2024-09-21 12:06:19+00:00 (#8013)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8013</link>
<description>debugger</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8013</guid>
<pubDate>Sat, 21 Sep 2024 12:06:19 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-21 12:05:46+00:00 (#8012)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8012</link>
<description>In VMI mode?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8012</guid>
<pubDate>Sat, 21 Sep 2024 12:05:46 +0000</pubDate>
</item>
<item>
<title>@instw0 on 2024-09-21 12:05:22+00:00 (#8011)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8011</link>
<description>how to connect hyperdbg to a physical computer?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8011</guid>
<pubDate>Sat, 21 Sep 2024 12:05:22 +0000</pubDate>
</item>
<item>
<title>@872223321 on 2024-09-18 10:02:01+00:00 (#8010)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8010</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8010</guid>
<pubDate>Wed, 18 Sep 2024 10:02:01 +0000</pubDate>
</item>
<item>
<title>@xmaple555 on 2024-09-17 14:44:59+00:00 (#8009)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8009</link>
<description>for old WDK version, you can try to replace ExAllocatePool2 to ExAllocatePool</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8009</guid>
<pubDate>Tue, 17 Sep 2024 14:44:59 +0000</pubDate>
</item>
<item>
<title>@xmaple555 on 2024-09-17 14:44:18+00:00 (#8008)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8008</link>
<description>https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/updating-deprecated-exallocatepool-calls</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8008</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/updating-deprecated-exallocatepool-calls" length="0" type="text/html"/>
<pubDate>Tue, 17 Sep 2024 14:44:18 +0000</pubDate>
</item>
<item>
<title>@xmaple555 on 2024-09-17 14:44:12+00:00 (#8007)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8007</link>
<description>I guess the problem from ExAllocatePool</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8007</guid>
<pubDate>Tue, 17 Sep 2024 14:44:12 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-17 14:28:16+00:00 (#8006)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8006</link>
<description>Nothing special changed in this commit, it's just bringing all allocation functions into a unified function. 🤔</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8006</guid>
<pubDate>Tue, 17 Sep 2024 14:28:16 +0000</pubDate>
</item>
<item>
<title>@kutaskozla3 on 2024-09-16 20:05:50+00:00 (#8005)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8005</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8005</guid>
<pubDate>Mon, 16 Sep 2024 20:05:50 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-15 16:37:36+00:00 (#8004)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8004</link>
<description>16db766 is no working</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8004</guid>
<pubDate>Sun, 15 Sep 2024 16:37:36 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-15 16:37:10+00:00 (#8003)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8003</link>
<description>40c9f5a is working</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8003</guid>
<pubDate>Sun, 15 Sep 2024 16:37:10 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-15 16:36:04+00:00 (#8002)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8002</link>
<description>photo_2024-09-15_16-36-04.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8002</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8002.jpg" length="18337" type="image/jpeg"/>
<pubDate>Sun, 15 Sep 2024 16:36:04 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-15 16:36:02+00:00 (#8001)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8001</link>
<description>vs version</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8001</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8001.jpg" length="32387" type="image/jpeg"/>
<pubDate>Sun, 15 Sep 2024 16:36:02 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-15 16:32:56+00:00 (#8000)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#8000</link>
<description>https://learn.microsoft.com/en-us/windows-hardware/drivers/develop/validating-windows-drivers</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#8000</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://learn.microsoft.com/en-us/windows-hardware/drivers/develop/validating-windows-drivers" length="0" type="text/html"/>
<pubDate>Sun, 15 Sep 2024 16:32:56 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-15 16:32:51+00:00 (#7999)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7999</link>
<description>photo_2024-09-15_16-32-51.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7999</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/7999.jpg" length="174022" type="image/jpeg"/>
<pubDate>Sun, 15 Sep 2024 16:32:51 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-15 16:31:20+00:00 (#7998)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7998</link>
<description>photo_2024-09-15_16-31-20.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7998</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/7998.jpg" length="66030" type="image/jpeg"/>
<pubDate>Sun, 15 Sep 2024 16:31:20 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-15 16:31:13+00:00 (#7997)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7997</link>
<description>photo_2024-09-15_16-31-13.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7997</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/7997.jpg" length="24243" type="image/jpeg"/>
<pubDate>Sun, 15 Sep 2024 16:31:13 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-15 16:31:03+00:00 (#7996)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7996</link>
<description>photo_2024-09-15_16-31-03.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7996</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/7996.jpg" length="16973" type="image/jpeg"/>
<pubDate>Sun, 15 Sep 2024 16:31:03 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-15 16:30:46+00:00 (#7995)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7995</link>
<description>Hello, I might know what the reason is. It seems that an API that is not compatible with older versions of Windows was introduced. I don't have compilation errors at commit 40c9f5a, but I encounter compilation errors at commit 16ab766. After I turned off the "Run ApiValidator" option in Visual Studio 2022 under the hyperkd Property Page -> ApiValidator, I was able to compile, but Windows 1903 refuses to load it.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7995</guid>
<pubDate>Sun, 15 Sep 2024 16:30:46 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-15 16:30:42+00:00 (#7994)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7994</link>
<description>你好,我可能知道是什么原因了,应该是引入了旧版windows不兼容的api导致的,,我在40c9f5a没有编译错误,在16ab766出现编译错误,我关闭了Visual Studio 2022->hyperkd Property Page->ApiValidator->Run ApiValidator之后可以编译,但是windows1903拒绝加载它</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7994</guid>
<pubDate>Sun, 15 Sep 2024 16:30:42 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-14 10:10:53+00:00 (#7993)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7993</link>
<description>I think this commit might be the one that breaks the support for your processor (within v0.5 to v0.6).</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7993</guid>
<pubDate>Sat, 14 Sep 2024 10:10:53 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-14 10:09:34+00:00 (#7992)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7992</link>
<description>Can you check before and after this commit?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7992</guid>
<pubDate>Sat, 14 Sep 2024 10:09:34 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-14 10:09:13+00:00 (#7991)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7991</link>
<description>I see. I suspect to this commit:
https://github.com/HyperDbg/HyperDbg/commit/bf6370d5a3d35bb7aeb16ce0d45fd77fda7bcca0</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7991</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://github.com/HyperDbg/HyperDbg/commit/bf6370d5a3d35bb7aeb16ce0d45fd77fda7bcca0" length="0" type="text/html"/>
<pubDate>Sat, 14 Sep 2024 10:09:13 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-14 10:08:51+00:00 (#7990)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7990</link>
<description>Not sure why it's needed</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7990</guid>
<pubDate>Sat, 14 Sep 2024 10:08:51 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-13 15:33:14+00:00 (#7989)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7989</link>
<description>"Are these macro definitions correct?
#define POOL_FLAG_NON_PAGED 0x0000000000000040UI64 // Non paged pool NX
#define POOL_FLAG_USE_QUOTA 0x0000000000000001UI64 // Charge quota
SDK 10.0.18362.0 does not have these macro definitions. I copied them from GitHub."</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7989</guid>
<pubDate>Fri, 13 Sep 2024 15:33:14 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-13 14:58:25+00:00 (#7988)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7988</link>
<description>photo_2024-09-13_14-58-25.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7988</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/7988.jpg" length="27411" type="image/jpeg"/>
<pubDate>Fri, 13 Sep 2024 14:58:25 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-13 14:58:22+00:00 (#7987)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7987</link>
<description>-----------------------------------------------------</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7987</guid>
<pubDate>Fri, 13 Sep 2024 14:58:22 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-13 14:58:18+00:00 (#7986)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7986</link>
<description>photo_2024-09-13_14-58-18.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7986</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/7986.jpg" length="64931" type="image/jpeg"/>
<pubDate>Fri, 13 Sep 2024 14:58:18 +0000</pubDate>
</item>
<item>
<title>@634346522 on 2024-09-13 13:50:51+00:00 (#7985)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7985</link>
<description>v0.6 is not working. v0.5 is work,,How can I obtain the error log? Use DbgView?"</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7985</guid>
<pubDate>Fri, 13 Sep 2024 13:50:51 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-09-13 11:36:13+00:00 (#7984)</title>
<link>https://tg-archive.hyperdbg.org/2024-09.html#7984</link>
<description>We used this feature a lot in a couple of main functionalities of HyperDbg.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-09.html#7984</guid>
<pubDate>Fri, 13 Sep 2024 11:36:13 +0000</pubDate>
</item>
</channel>
</rss>