-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.xml
820 lines (796 loc) · 54.9 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
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
<?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>Thu, 02 Jan 2025 18:23:41 +0000</lastBuildDate>
<item>
<title>@HughEverett on 2025-01-02 18:06:04+00:00 (#8487)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8487</link>
<description>Thanks to Bjorn (he is not in the group), @AMJahangirzad, @binophism, and another contributor whose Telegram account I don’t know.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8487</guid>
<pubDate>Thu, 02 Jan 2025 18:06:04 +0000</pubDate>
</item>
<item>
<title>@HyperDbgChannel on 2025-01-02 18:03:47+00:00 (#8486)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8486</link>
<description>photo_2025-01-02_18-03-47.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8486</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8486.jpg" length="164447" type="image/jpeg"/>
<pubDate>Thu, 02 Jan 2025 18:03:47 +0000</pubDate>
</item>
<item>
<title>@HyperDbgChannel on 2025-01-02 18:03:47+00:00 (#8485)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8485</link>
<description>photo_2025-01-02_18-03-47.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8485</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8485.jpg" length="131127" type="image/jpeg"/>
<pubDate>Thu, 02 Jan 2025 18:03:47 +0000</pubDate>
</item>
<item>
<title>@HyperDbgChannel on 2025-01-02 18:03:47+00:00 (#8484)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8484</link>
<description>The first HyperDbg release of 2025 is out! 🎉
This version (v0.12) introduces commands for PCI/PCI-e device tree enumeration and IDT dumping, plus many bug fixes.
🔗 Check it out:
https://github.com/HyperDbg/HyperDbg/releases/tag/v0.12
More information:
- https://docs.hyperdbg.org/commands/extension-commands/pcitree
- https://docs.hyperdbg.org/commands/extension-commands/idt</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8484</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8484.jpg" length="195492" type="image/jpeg"/>
<pubDate>Thu, 02 Jan 2025 18:03:47 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2025-01-02 16:58:40+00:00 (#8483)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8483</link>
<description>So, the easiest way to solve this problem is to preallocate memory before applying any command that the context is meaningful to you. For example, you know that during you debugging journey, you need 1000 more preallocated buffers. So, you preallocate it, then start using other commands like 'bp', etc.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8483</guid>
<pubDate>Thu, 02 Jan 2025 16:58:40 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2025-01-02 16:56:54+00:00 (#8482)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8482</link>
<description>Yes, and that's why you need to run the 'prealloc' command once you're not using the context (register and memory) when the state of the system is not important for you. For example if you want to use the breakpoint command ('bp'), you probably need to apply your commands immediately while you're expecting HyperDbg to preserve the context (register and memory). In this scenario, if you want to run 'prealloc', HyperDbg will run the debuggee (continue the execution) to allocate buffer for you. So, it's obvious that the registers are changed and you're no longer in the target instruction where you previously put the breakpoint.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8482</guid>
<pubDate>Thu, 02 Jan 2025 16:56:54 +0000</pubDate>
</item>
<item>
<title>@6176993302 on 2025-01-02 16:48:27+00:00 (#8481)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8481</link>
<description>Ok 👌 got it now! So the hyoerdbg design tried to pre allocated buffers before entring vmx root mode since in this mode memory allocation is not possible or at least safe to request</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8481</guid>
<pubDate>Thu, 02 Jan 2025 16:48:27 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2025-01-02 16:37:18+00:00 (#8480)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8480</link>
<description>The reason for this is that some commands need interaction with VMX non-root. For example, allocating memory is not possible in the VMX root-mode since paging is disabled (from the OS perspective), so this command will run the debuggee and tries to allocate memory from VMX non-root mode. So, once you run it, the debugger is paused again, and all the registers and memory have been modified.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8480</guid>
<pubDate>Thu, 02 Jan 2025 16:37:18 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2025-01-02 16:33:58+00:00 (#8479)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8479</link>
<description>For example this command won't lose the context.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8479</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8479.jpg" length="42739" type="image/jpeg"/>
<pubDate>Thu, 02 Jan 2025 16:33:58 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2025-01-02 16:33:03+00:00 (#8478)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8478</link>
<description>Like this one, you can check the 'Remarks' section of the command.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8478</guid>
<pubDate>Thu, 02 Jan 2025 16:33:03 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2025-01-02 16:32:41+00:00 (#8477)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8477</link>
<description>photo_2025-01-02_16-32-41.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8477</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8477.jpg" length="38207" type="image/jpeg"/>
<pubDate>Thu, 02 Jan 2025 16:32:41 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2025-01-02 16:32:38+00:00 (#8476)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8476</link>
<description>HyperDbg has two types of commands. Some commands will lose the context (like the 'prealloc' command) and most of the commands won't lose the context.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8476</guid>
<pubDate>Thu, 02 Jan 2025 16:32:38 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2025-01-02 16:31:15+00:00 (#8475)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8475</link>
<description>No, I mean by running this command, you'll lose the context (register and memory). You don't need to modify the source code.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8475</guid>
<pubDate>Thu, 02 Jan 2025 16:31:15 +0000</pubDate>
</item>
<item>
<title>@6176993302 on 2025-01-02 16:15:19+00:00 (#8474)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8474</link>
<description>Thanks sina for the great explanation</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8474</guid>
<pubDate>Thu, 02 Jan 2025 16:15:19 +0000</pubDate>
</item>
<item>
<title>@6176993302 on 2025-01-02 16:15:12+00:00 (#8473)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8473</link>
<description>Got your point, so it will be more safe to keep track of the whole context change it from the source code probably</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8473</guid>
<pubDate>Thu, 02 Jan 2025 16:15:12 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2025-01-02 16:13:45+00:00 (#8472)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8472</link>
<description>You can also increase the default number of preallocations using macros in the source code and recompile hyperdbg, but using the 'prealloc' command, you can allocate it without the need to modify the source code. Just remember that this command will run the debuggee for some times, so, you'll lose the context (memory and registers), thus you need to run it before any other commands (maybe once you just start hyperdbg).</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8472</guid>
<pubDate>Thu, 02 Jan 2025 16:13:45 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2025-01-02 16:10:19+00:00 (#8471)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8471</link>
<description>Hi,
You can use the 'prealloc' command to preallocate buffers:
https://docs.hyperdbg.org/commands/debugging-commands/prealloc</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8471</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://docs.hyperdbg.org/commands/debugging-commands/prealloc" length="0" type="text/html"/>
<pubDate>Thu, 02 Jan 2025 16:10:19 +0000</pubDate>
</item>
<item>
<title>@6176993302 on 2025-01-02 13:04:09+00:00 (#8470)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8470</link>
<description>Hi guys , hope your year will be great with a lot of success 🙌 😊 I have a question 😊 I want to increase the number of pre allocated buffers because after some testing I figured out that the maximum is 20 approximate and thanks in advance</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8470</guid>
<pubDate>Thu, 02 Jan 2025 13:04:09 +0000</pubDate>
</item>
<item>
<title>@6176993302 on 2025-01-02 13:02:53+00:00 (#8469)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8469</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8469</guid>
<pubDate>Thu, 02 Jan 2025 13:02:53 +0000</pubDate>
</item>
<item>
<title>@5790478717 on 2025-01-01 04:17:24+00:00 (#8468)</title>
<link>https://tg-archive.hyperdbg.org/2025-01.html#8468</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2025-01.html#8468</guid>
<pubDate>Wed, 01 Jan 2025 04:17:24 +0000</pubDate>
</item>
<item>
<title>@AleeAmini on 2024-12-31 21:15:33+00:00 (#8467)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8467</link>
<description>Happy new year guys🎄🎄😘</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8467</guid>
<pubDate>Tue, 31 Dec 2024 21:15:33 +0000</pubDate>
</item>
<item>
<title>@S4l3H on 2024-12-31 19:58:30+00:00 (#8466)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8466</link>
<description>Happy new year HyperDbg Family! 🤝
Hope we all learn more stuff👉, level up 🌡, and do amazing projects in 2025! 👍</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8466</guid>
<pubDate>Tue, 31 Dec 2024 19:58:30 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-31 19:38:28+00:00 (#8465)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8465</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8465</guid>
<pubDate>Tue, 31 Dec 2024 19:38:28 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-31 19:38:21+00:00 (#8464)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8464</link>
<description>Happy New Year, everyone! 🎉🎊
Wishing you an amazing 2025 ahead!
This year, we’re excited to work on adding new features to HyperDbg, including support for PCI Express, UEFI, and firmware debugging. As always, your contributions are greatly appreciated!</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8464</guid>
<pubDate>Tue, 31 Dec 2024 19:38:21 +0000</pubDate>
</item>
<item>
<title>@IsNerverMore on 2024-12-31 18:08:16+00:00 (#8463)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8463</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8463</guid>
<pubDate>Tue, 31 Dec 2024 18:08:16 +0000</pubDate>
</item>
<item>
<title>@hyper_dbg on 2024-12-30 20:31:48+00:00 (#8462)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8462</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8462</guid>
<pubDate>Mon, 30 Dec 2024 20:31:48 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-30 05:14:34+00:00 (#8461)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8461</link>
<description>There are also commands for interrupt redirection of Intel VT-d that will be added in the future versions.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8461</guid>
<pubDate>Mon, 30 Dec 2024 05:14:34 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-30 05:13:37+00:00 (#8460)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8460</link>
<description>At this point, we have most of the commands related to handling interrupts, exceptions, and faults. These include !idt for dumping IDT entries, !apic and !ioapic for viewing the state of the Local APIC and I/O APIC in both XAPIC and X2APIC modes, and commands like !exception and !interrupt for intercepting (hooking) interrupts and exceptions.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8460</guid>
<pubDate>Mon, 30 Dec 2024 05:13:37 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-30 05:10:39+00:00 (#8459)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8459</link>
<description>Starting from the next version (v0.12), the new command for dump IDT entries will be added to HyperDbg. You can test it on the 'dev' branch now.
https://docs.hyperdbg.org/commands/extension-commands/idt</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8459</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8459.jpg" length="164447" type="image/jpeg"/>
<pubDate>Mon, 30 Dec 2024 05:10:39 +0000</pubDate>
</item>
<item>
<title>@Alesice on 2024-12-28 09:32:25+00:00 (#8458)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8458</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8458</guid>
<pubDate>Sat, 28 Dec 2024 09:32:25 +0000</pubDate>
</item>
<item>
<title>@7865201591 on 2024-12-25 22:37:12+00:00 (#8456)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8456</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8456</guid>
<pubDate>Wed, 25 Dec 2024 22:37:12 +0000</pubDate>
</item>
<item>
<title>@Mhe1402 on 2024-12-25 10:54:19+00:00 (#8455)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8455</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8455</guid>
<pubDate>Wed, 25 Dec 2024 10:54:19 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-25 04:02:18+00:00 (#8454)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8454</link>
<description>got it.Thank your very much.I'm sorry to bother you in Christmas.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8454</guid>
<pubDate>Wed, 25 Dec 2024 04:02:18 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-25 03:33:48+00:00 (#8453)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8453</link>
<description>I recommend going through the OpenSecurityTrainings' course for HyperDbg, since there are plenty of examples where we used HyperDbg for debugging user mode applications:
https://p.ost2.fyi/courses/course-v1:OpenSecurityTraining2+Dbg3301_HyperDbg+2023_v1/about</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8453</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://p.ost2.fyi/courses/course-v1:OpenSecurityTraining2+Dbg3301_HyperDbg+2023_v1/about" length="0" type="text/html"/>
<pubDate>Wed, 25 Dec 2024 03:33:48 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-25 03:31:18+00:00 (#8452)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8452</link>
<description>So, it's basically about the process memory layout. You can do whatever you want as long as you're in the memory layout of your target process (CR3).</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8452</guid>
<pubDate>Wed, 25 Dec 2024 03:31:18 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-25 03:29:09+00:00 (#8451)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8451</link>
<description>Hi,
Merry Christmas. 🎄
Actually in HyperDbg, there is no difference between debugging a user mode application or a kernel mode code (by design) since it operates at the hypervisor-level. Though, there are plenty of command and functions that facilitate the user mode debugging like the '.start' command or the other commands for switching into a target process.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8451</guid>
<pubDate>Wed, 25 Dec 2024 03:29:09 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-25 02:58:27+00:00 (#8446)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8446</link>
<description>hi.sina. Merry Christmas. Can you answer my question? How to debug application user-mode on hyperdbg?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8446</guid>
<pubDate>Wed, 25 Dec 2024 02:58:27 +0000</pubDate>
</item>
<item>
<title>@5593422848 on 2024-12-24 07:03:52+00:00 (#8445)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8445</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8445</guid>
<pubDate>Tue, 24 Dec 2024 07:03:52 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-24 01:39:51+00:00 (#8444)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8444</link>
<description>got it.thank your very much.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8444</guid>
<pubDate>Tue, 24 Dec 2024 01:39:51 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-24 01:36:25+00:00 (#8443)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8443</link>
<description>BTW, if you encounter any further error, please don't hesitate to post them here and we would be glad to help.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8443</guid>
<pubDate>Tue, 24 Dec 2024 01:36:25 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-24 01:35:53+00:00 (#8442)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8442</link>
<description>Yeah, but there could be a lot of unexpected conditions we didn’t think of (which might cause new errors 🙂). Typically as HyperDbg runs at the hypervisor level, the user needs to consider a ton of factors plus have a solid understanding of CPU internals to figure out what’s going on and how to handle it.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8442</guid>
<pubDate>Tue, 24 Dec 2024 01:35:53 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-24 01:30:39+00:00 (#8441)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8441</link>
<description>No. Haven't been tested yet. Isn't that the solution?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8441</guid>
<pubDate>Tue, 24 Dec 2024 01:30:39 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-24 01:24:24+00:00 (#8440)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8440</link>
<description>Did you test it? Is the problem solved? I see you also closed the GitHub issue.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8440</guid>
<pubDate>Tue, 24 Dec 2024 01:24:24 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-24 01:13:07+00:00 (#8439)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8439</link>
<description>got it. thank your very much.😊</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8439</guid>
<pubDate>Tue, 24 Dec 2024 01:13:07 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-23 11:13:49+00:00 (#8438)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8438</link>
<description>You have plenty of other options, you can start the process using the '.start' command (which intercepts the first instruction of the entry point in the user mode) or you could put !epthook on known user-mode functions that you know it will called or maybe putting a !monitor on a buffer or piece of code, all of them work. Just make sure that your RIP register is in the user-mode and the process is your target process.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8438</guid>
<pubDate>Mon, 23 Dec 2024 11:13:49 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-23 11:10:23+00:00 (#8437)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8437</link>
<description>You should not use the '.pagein' after the '.process'. Since in the implementation, both of the use the same mechanism (even injection in VMCS). So, now that I'm thinking about it, it couldn't work since we're not buffering multiple interrupts/faults/exceptions.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8437</guid>
<pubDate>Mon, 23 Dec 2024 11:10:23 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-23 11:05:01+00:00 (#8436)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8436</link>
<description>You need to intercept the process while it's in the user-mode (not kernel mode) and then inject the page-fault.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8436</guid>
<pubDate>Mon, 23 Dec 2024 11:05:01 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-23 11:04:20+00:00 (#8435)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8435</link>
<description>I see the issue now. Check the RIP address where you paused and examine the execution of the target process. It appears to be in the page-fault handler, which operates in the kernel rather than user mode. If you inject a page fault while the page-fault handler is already active, it can trigger multiple page faults (or a double fault, if I’m not mistaken), ultimately leading to a Blue Screen of Death (BSoD).</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8435</guid>
<pubDate>Mon, 23 Dec 2024 11:04:20 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-23 02:59:34+00:00 (#8434)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8434</link>
<description>photo_2024-12-23_02-59-34.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8434</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8434.jpg" length="49230" type="image/jpeg"/>
<pubDate>Mon, 23 Dec 2024 02:59:34 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-23 02:59:16+00:00 (#8433)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8433</link>
<description>photo_2024-12-23_02-59-16.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8433</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8433.jpg" length="72781" type="image/jpeg"/>
<pubDate>Mon, 23 Dec 2024 02:59:16 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-23 02:57:38+00:00 (#8432)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8432</link>
<description>hi,I'm pretty sure the address is valid.The end result the guess computs is still a blue screen.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8432</guid>
<pubDate>Mon, 23 Dec 2024 02:57:38 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-20 10:46:56+00:00 (#8430)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8430</link>
<description>got it. thank you for your reply. i didn't watch the video. I think that's the problem. I will try the above respond and i will reply this post if have any process. thank your.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8430</guid>
<pubDate>Fri, 20 Dec 2024 10:46:56 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-20 09:58:58+00:00 (#8428)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8428</link>
<description>When do you execute this command? I mean at what stage of a process and after which command?
Did you see this video for the reference?
https://youtu.be/MjDW2gS3lBg?si=jBLvS0C458Erw7A2</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8428</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://youtu.be/MjDW2gS3lBg?si=jBLvS0C458Erw7A2" length="0" type="text/html"/>
<pubDate>Fri, 20 Dec 2024 09:58:58 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-20 09:56:57+00:00 (#8427)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8427</link>
<description>Running the 'lm' command as mentioned in the documentation, runs the debuggee for some times, thus, you'll loose the context (memory, registers, and process). So, you might end up injecting page fault to a different process and as HyperDbg is operating at the kernel, the page fault injection will be delivered to the Windows kernel and it's not a surprise to see BSOD.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8427</guid>
<pubDate>Fri, 20 Dec 2024 09:56:57 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-20 09:52:50+00:00 (#8426)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8426</link>
<description>Are you sure that you're delivering the #PF to the correct process layout? You can check it by using the '.process' command.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8426</guid>
<pubDate>Fri, 20 Dec 2024 09:52:50 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-20 02:35:50+00:00 (#8424)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8424</link>
<description>photo_2024-12-20_02-35-50.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8424</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8424.jpg" length="85632" type="image/jpeg"/>
<pubDate>Fri, 20 Dec 2024 02:35:50 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-20 02:35:33+00:00 (#8423)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8423</link>
<description>hi,
First. i sure the address is actually valid. I use the command 'lm um pid xxx' to get the address. As in the screenshot below.
Second, i run command ".pagein 00007ff9dd850000" in host computer. but the guest computer still blue screen.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8423</guid>
<pubDate>Fri, 20 Dec 2024 02:35:33 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-18 10:25:19+00:00 (#8422)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8422</link>
<description>thank your for your replay.I will try the above respond and contact you immediately if there is any result.thank your</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8422</guid>
<pubDate>Wed, 18 Dec 2024 10:25:19 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-18 09:58:17+00:00 (#8421)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8421</link>
<description>Hi,
I actually respond it in the github (https://github.com/HyperDbg/HyperDbg/issues/488) but will send it here for further discussion:
There might be two issues in this scenario.
First, the address might be actually invalid. Are you 100% sure that the address is valid?
If the address is invalid in the OS, HyperDbg will just inject a #PF and it will crash the system since Windows assumes it as a not-expected error.
Second, it's kinda weird that you used .pagein w which means injecting a 'write'. Change it to the default behavior (without 'w') might fix the issue, so the command should be:
.pagein 00007ffb6bee0000
Let me know whether the above command fixes the problem or not.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8421</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://github.com/HyperDbg/HyperDbg/issues/488" length="0" type="text/html"/>
<pubDate>Wed, 18 Dec 2024 09:58:17 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-18 02:55:29+00:00 (#8420)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8420</link>
<description>when i use monitor command monitor address 00007ffb6bee0000. the hyperdbg will show (err, invalid address). then i use the .pagein w 00007ffb6bee0000 command. and 100% trigger windows blue screen. i use vm as guest. intel i3 cpu.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8420</guid>
<pubDate>Wed, 18 Dec 2024 02:55:29 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-18 02:47:22+00:00 (#8419)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8419</link>
<description>hi.everybody. i use debug model to debug process. i use the .pagein command will trigger blue screen. and it will 100% trigger. I'm not sure it's a bug. Can anyone answer my questions? Thank you very much.😊</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8419</guid>
<pubDate>Wed, 18 Dec 2024 02:47:22 +0000</pubDate>
</item>
<item>
<title>@anna_junet on 2024-12-18 02:27:23+00:00 (#8418)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8418</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8418</guid>
<pubDate>Wed, 18 Dec 2024 02:27:23 +0000</pubDate>
</item>
<item>
<title>@7811530886 on 2024-12-17 14:25:52+00:00 (#8417)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8417</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8417</guid>
<pubDate>Tue, 17 Dec 2024 14:25:52 +0000</pubDate>
</item>
<item>
<title>@qsPfIg873371717 on 2024-12-17 07:54:07+00:00 (#8415)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8415</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8415</guid>
<pubDate>Tue, 17 Dec 2024 07:54:07 +0000</pubDate>
</item>
<item>
<title>@pzwcsndm on 2024-12-16 15:22:32+00:00 (#8414)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8414</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8414</guid>
<pubDate>Mon, 16 Dec 2024 15:22:32 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-12-15 18:18:19+00:00 (#8413)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8413</link>
<description>There are indeed separate page tables on Linux and Windows, and that's the reason you trap CR3 writes in the hypervisor as well</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8413</guid>
<pubDate>Sun, 15 Dec 2024 18:18:19 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-12-15 18:17:18+00:00 (#8412)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8412</link>
<description>But my take is hypervisor doesn't know anything about the guest, whether it is linux, dos or etc. Hypervisor's purpose is to virtualize the execution environment.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8412</guid>
<pubDate>Sun, 15 Dec 2024 18:17:18 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-12-15 18:15:38+00:00 (#8411)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8411</link>
<description>Oh, that's a question for the author then, hehe</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8411</guid>
<pubDate>Sun, 15 Dec 2024 18:15:38 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-12-15 18:10:51+00:00 (#8410)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8410</link>
<description>[discord] <jamlee7879> I'm currently reading "hypervisor-from-scratch-part-4". The architecture diagram of the shadow page table in it doesn't quite match the Linux memory management logic that I knew before, so I'm a bit confused.
My understanding is the same as that shown in this diagram.
https://www.ryanstan.com/mmu-virtualization-shadow-page-tables.html
https://cdn.discordapp.com/attachments/962350355839066130/1317916799718785165/shadow-page-tables-diagram.png?ex=67606d2a&is=675f1baa&hm=2465f1cf56627b2a46e465caf83e28c81d27045ecfaa3609840c7d26023dabf0&</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8410</guid>
<pubDate>Sun, 15 Dec 2024 18:10:51 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-12-15 18:03:18+00:00 (#8409)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8409</link>
<description>I don't know which material you're researching, but it looks like a description of a hypervisor for a pre-EPT era. Hypervisor would trap page faults and mask CR3 register, so that it would replace needed pages for the guest OS on the fly. Indeed, you would have to mask all related page tables (for every related process). However, it's more like an implementation detail, that's why it's probably out of scope for your material.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8409</guid>
<pubDate>Sun, 15 Dec 2024 18:03:18 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-12-15 17:58:06+00:00 (#8408)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8408</link>
<description>[discord] <jamlee7879> Many diagrams are drawn in this way, but I don't understand why only one page table is drawn for the guest. Clearly, there should be multiple page tables (one for each process).
https://cdn.discordapp.com/attachments/962350355839066130/1317913591650713721/703cb802dfdf67ea4295e3fdd8d6d9fe.png?ex=67606a2d&is=675f18ad&hm=eca03a1625753c826ceccd0c301c338ab31ceb44e9db6e09fac291f1a87e4e46&</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8408</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://cdn.discordapp.com/attachments/962350355839066130/1317913591650713721/703cb802dfdf67ea4295e3fdd8d6d9fe.png?ex=67606a2d&is=675f18ad&hm=eca03a1625753c826ceccd0c301c338ab31ceb44e9db6e09fac291f1a87e4e46&" length="0" type="text/html"/>
<pubDate>Sun, 15 Dec 2024 17:58:06 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-12-15 17:54:57+00:00 (#8407)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8407</link>
<description>[discord] <jamlee7879> In Linux, each process has its own page table. However, according to the concept of shadow page tables, it seems that there is only one page table for the guest. This seems very strange.
https://cdn.discordapp.com/attachments/962350355839066130/1317912800395399219/shadow-page-tables-1.png?ex=67606971&is=675f17f1&hm=1a24bfdbcdcae67675e731575ebe01ef151b97f61fd90ba7a7f6eb7c27301627&</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8407</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://cdn.discordapp.com/attachments/962350355839066130/1317912800395399219/shadow-page-tables-1.png?ex=67606971&is=675f17f1&hm=1a24bfdbcdcae67675e731575ebe01ef151b97f61fd90ba7a7f6eb7c27301627&" length="0" type="text/html"/>
<pubDate>Sun, 15 Dec 2024 17:54:57 +0000</pubDate>
</item>
<item>
<title>@zzzzzzzzzzw111 on 2024-12-15 11:45:46+00:00 (#8406)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8406</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8406</guid>
<pubDate>Sun, 15 Dec 2024 11:45:46 +0000</pubDate>
</item>
<item>
<title>@afkuvzrkar on 2024-12-14 03:23:56+00:00 (#8405)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8405</link>
<description>document_2024-12-14_03-23-56.mp4</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8405</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8405.mp4" length="643248" type="video/mp4"/>
<pubDate>Sat, 14 Dec 2024 03:23:56 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-13 22:13:55+00:00 (#8404)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8404</link>
<description>Great. Thanks for fixing it.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8404</guid>
<pubDate>Fri, 13 Dec 2024 22:13:55 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-13 22:13:42+00:00 (#8403)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8403</link>
<description>Merged! 👍</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8403</guid>
<pubDate>Fri, 13 Dec 2024 22:13:42 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-12-13 17:31:02+00:00 (#8402)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8402</link>
<description>[discord] <jamlee7879> Checked in successfully for 'hypervisor-from-scratch-part-2'
https://cdn.discordapp.com/attachments/962350355839066130/1317182006190280714/image.png?ex=675dc0d6&is=675c6f56&hm=91e6ccffd96bea431c7a7874768e590b9379d3dcdb86319ac7097608203ae61b&</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8402</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://cdn.discordapp.com/attachments/962350355839066130/1317182006190280714/image.png?ex=675dc0d6&is=675c6f56&hm=91e6ccffd96bea431c7a7874768e590b9379d3dcdb86319ac7097608203ae61b&" length="0" type="text/html"/>
<pubDate>Fri, 13 Dec 2024 17:31:02 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-12-13 14:25:39+00:00 (#8401)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8401</link>
<description>[discord] <jamlee7879> @HyperDbgBridge https://github.com/rayanfam/rayanfam.github.io/pull/2 Do you have time to review it?</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8401</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://github.com/rayanfam/rayanfam.github.io/pull/2" length="0" type="text/html"/>
<pubDate>Fri, 13 Dec 2024 14:25:39 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-12 16:57:23+00:00 (#8400)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8400</link>
<description>Nice catch. You can send your patch to the blog using this repo:
https://github.com/rayanfam/rayanfam.github.io/tree/main/_posts</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8400</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://github.com/rayanfam/rayanfam.github.io/tree/main/_posts" length="0" type="text/html"/>
<pubDate>Thu, 12 Dec 2024 16:57:23 +0000</pubDate>
</item>
<item>
<title>@LG_Preset on 2024-12-12 16:27:03+00:00 (#8399)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8399</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8399</guid>
<pubDate>Thu, 12 Dec 2024 16:27:03 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-12-11 17:09:07+00:00 (#8398)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8398</link>
<description>[discord] <jamlee7879> you could consider patching the article. 😄
https://rayanfam.com/topics/hypervisor-from-scratch-part-2/#viewing-debugging-messages-in-dbgview</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8398</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://rayanfam.com/topics/hypervisor-from-scratch-part-2/" length="0" type="text/html"/>
<pubDate>Wed, 11 Dec 2024 17:09:07 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-12-11 17:03:02+00:00 (#8397)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8397</link>
<description>[discord] <jamlee7879> it works for me. my win version is 10.0.16299
https://cdn.discordapp.com/attachments/962350355839066130/1316450184007385099/image.png?ex=675b1746&is=6759c5c6&hm=519cbc2fcbf829fa164e17084e0366b7e0c0e5074fb3be8a911d086e4e590392&</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8397</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://cdn.discordapp.com/attachments/962350355839066130/1316450184007385099/image.png?ex=675b1746&is=6759c5c6&hm=519cbc2fcbf829fa164e17084e0366b7e0c0e5074fb3be8a911d086e4e590392&" length="0" type="text/html"/>
<pubDate>Wed, 11 Dec 2024 17:03:02 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-12-11 16:59:12+00:00 (#8395)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8395</link>
<description>[discord] <jamlee7879> @HyperDbgBridge
Is Rayanfam in the group? Things aren't working properly here. The registry entries for DbgView aren't working properly either. It took me about an hour to figure out the correct way to do it. Here's what you should do:
Save the following content as dgbview.reg.
Double-click on dgbview.reg.
```
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Debug Print Filter]
"DEFAULT"=dword:0000000f
```
https://cdn.discordapp.com/attachments/962350355839066130/1316449218633928724/image.png?ex=675b1660&is=6759c4e0&hm=828c61954ef4c4123a50b78220337f9999819a81292ad551763e8655a98fcedb&</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8395</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://cdn.discordapp.com/attachments/962350355839066130/1316449218633928724/image.png?ex=675b1660&is=6759c4e0&hm=828c61954ef4c4123a50b78220337f9999819a81292ad551763e8655a98fcedb&" length="0" type="text/html"/>
<pubDate>Wed, 11 Dec 2024 16:59:12 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-11 15:10:04+00:00 (#8394)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8394</link>
<description>photo_2024-12-11_15-10-04.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8394</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8394.jpg" length="131127" type="image/jpeg"/>
<pubDate>Wed, 11 Dec 2024 15:10:04 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-12-11 15:10:04+00:00 (#8393)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8393</link>
<description>Starting from the next version (v0.12), HyperDbg will support the '!pcitree' command. You can use it from the 'dev' branch now.
https://docs.hyperdbg.org/commands/extension-commands/pcitree</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8393</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8393.jpg" length="195492" type="image/jpeg"/>
<pubDate>Wed, 11 Dec 2024 15:10:04 +0000</pubDate>
</item>
<item>
<title>@xssaint on 2024-12-08 22:04:39+00:00 (#8390)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8390</link>
<description>sticker.webm</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8390</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8390.webm" length="65692" type="video/webm"/>
<pubDate>Sun, 08 Dec 2024 22:04:39 +0000</pubDate>
</item>
<item>
<title>@Fly_Dragon_Fly on 2024-12-07 05:28:24+00:00 (#8388)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8388</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8388</guid>
<pubDate>Sat, 07 Dec 2024 05:28:24 +0000</pubDate>
</item>
<item>
<title>@7806029674 on 2024-12-06 16:10:15+00:00 (#8387)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8387</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8387</guid>
<pubDate>Fri, 06 Dec 2024 16:10:15 +0000</pubDate>
</item>
<item>
<title>@282877022 on 2024-12-06 06:40:20+00:00 (#8386)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8386</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8386</guid>
<pubDate>Fri, 06 Dec 2024 06:40:20 +0000</pubDate>
</item>
<item>
<title>@DoubleFetch on 2024-12-06 05:55:52+00:00 (#8385)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8385</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8385</guid>
<pubDate>Fri, 06 Dec 2024 05:55:52 +0000</pubDate>
</item>
<item>
<title>@HyperDbgChannel on 2024-12-03 16:28:49+00:00 (#8384)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8384</link>
<description>photo_2024-12-03_16-28-49.jpg</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8384</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8384.jpg" length="95831" type="image/jpeg"/>
<pubDate>Tue, 03 Dec 2024 16:28:49 +0000</pubDate>
</item>
<item>
<title>@HyperDbgChannel on 2024-12-03 16:28:49+00:00 (#8383)</title>
<link>https://tg-archive.hyperdbg.org/2024-12.html#8383</link>
<description>HyperDbg v0.11 is released! ✨
This version comes with bug fixes, improvements, and two new commands for viewing Local APIC (XAPIC/X2APIC) and IO APIC.
Big shoutout to Björn Ruytenberg for joining the team for bringing PCIe support to HyperDbg!
https://github.com/HyperDbg/HyperDbg/releases/tag/v0.11.0
Check it out:
https://docs.hyperdbg.org/commands/extension-commands/apic
https://docs.hyperdbg.org/commands/extension-commands/ioapic</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-12.html#8383</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/8383.jpg" length="129534" type="image/jpeg"/>
<pubDate>Tue, 03 Dec 2024 16:28:49 +0000</pubDate>
</item>
<item>
<title>@6817320794 on 2024-11-30 20:18:31+00:00 (#8382)</title>
<link>https://tg-archive.hyperdbg.org/2024-11.html#8382</link>
<description></description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-11.html#8382</guid>
<pubDate>Sat, 30 Nov 2024 20:18:31 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-11-29 10:07:46+00:00 (#8381)</title>
<link>https://tg-archive.hyperdbg.org/2024-11.html#8381</link>
<description>[discord] <jamlee7879> https://tenor.com/view/high-five-patrick-star-spongebob-squarepants-the-patrick-star-show-yes-gif-2201400520488940521</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-11.html#8381</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://tenor.com/view/high-five-patrick-star-spongebob-squarepants-the-patrick-star-show-yes-gif-2201400520488940521" length="0" type="text/html"/>
<pubDate>Fri, 29 Nov 2024 10:07:46 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-11-29 10:07:34+00:00 (#8380)</title>
<link>https://tg-archive.hyperdbg.org/2024-11.html#8380</link>
<description>[discord] <jamlee7879> Next, I'll go on to read "Hypervisor From Scratch" in more depth.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-11.html#8380</guid>
<pubDate>Fri, 29 Nov 2024 10:07:34 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-11-29 10:05:23+00:00 (#8379)</title>
<link>https://tg-archive.hyperdbg.org/2024-11.html#8379</link>
<description>[discord] <jamlee7879> Yes, this is exactly the answer I was looking for. Actually, I asked ChatGPT to write example code like this before, but I can't be 100% sure that the MSR registers are shareable. I didn't have a deep enough understanding of virtualization before. Thank you. You've been a great help.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-11.html#8379</guid>
<pubDate>Fri, 29 Nov 2024 10:05:23 +0000</pubDate>
</item>
<item>
<title>@honorary_bot on 2024-11-29 09:57:38+00:00 (#8378)</title>
<link>https://tg-archive.hyperdbg.org/2024-11.html#8378</link>
<description>It’s the same cpu all the time, it just has different modes of operation. Depending on the mode of execution the CPU has either additional features or otherwise a reduced set of them. VMX root mode pretty much just allows the execution of VMX instructions. VMX guest mode allows auxiliary control structures (like vmcs) to back up its execution. The whole idea of trapping various events in the guest mode is to allow the hypervisor to properly emulate the platform. MSRs for example are shared between all modes, but you don’t want the guest to mess with MsRs that could affect VMX root mode, right? That’s why you have the ability to intercept them and manually handle in the root mode. If that’s your question.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-11.html#8378</guid>
<pubDate>Fri, 29 Nov 2024 09:57:38 +0000</pubDate>
</item>
<item>
<title>@HyperDbgBot on 2024-11-29 09:44:55+00:00 (#8377)</title>
<link>https://tg-archive.hyperdbg.org/2024-11.html#8377</link>
<description>[discord] <jamlee7879> Yes, I've briefly read through the "Hypervisor From Scratch" series, but I didn't quite understand it. I can't imagine what a bluepill style hypervisor program is like. Here's what I know:
1. When the Virtual Machine Monitor (VMM) enters the VMX (Virtual Machine eXtensions) mode, it has already set up the conversions for the Virtual Machine Control Structure (VMCS) and Extended Page Table (EPT).
2. The state of the CPU that enters the operation will be stored in the VMCS. At this time, the virtualized CPU is being used.
3. Then it exits the VMX mode. The code runs on the physical CPU again.
The CPU running in VT (Virtualization Technology) and the physical CPU are like two completely different worlds. Why is it related to the MSR (Model Specific Register) hook? I must have missed some crucial information.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-11.html#8377</guid>
<pubDate>Fri, 29 Nov 2024 09:44:55 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-11-29 08:49:14+00:00 (#8375)</title>
<link>https://tg-archive.hyperdbg.org/2024-11.html#8375</link>
<description>If you're curious about these topics, you might be interested in checking Hypervisor From Scratch series which describes how HyperDbg works internally:
https://rayanfam.com/tutorials/</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-11.html#8375</guid>
<enclosure url="https://tg-archive.hyperdbg.org/media/https://rayanfam.com/tutorials/" length="0" type="text/html"/>
<pubDate>Fri, 29 Nov 2024 08:49:14 +0000</pubDate>
</item>
<item>
<title>@HughEverett on 2024-11-29 08:48:01+00:00 (#8374)</title>
<link>https://tg-archive.hyperdbg.org/2024-11.html#8374</link>
<description>Generally, VT-x is consist of some instructions, which gives you (VMM) the ability to control critical CPU components (like memory, interrupts, IO ports, PCIe bars) by triggering VM-exits.</description>
<guid isPermaLink="false">https://tg-archive.hyperdbg.org/2024-11.html#8374</guid>
<pubDate>Fri, 29 Nov 2024 08:48:01 +0000</pubDate>
</item>
</channel>
</rss>