Mağaza Sayfası
Hacknet
Tümü Tartışmalar Ekran Görüntüleri Çizimler Yayınlar Videolar Atölye Haberler Rehberler İncelemeler
Hacknet >  Atölye > Aqua Kullanıcısının Atölyesi > System Rift > Tartışmalar
System Rift
Açıklama Tartışmalar7 Yorumlar64 Değişiklik Notları
 Bu başlık sabitlenmiş, muhtemelen önemli bir başlık
Aqua  [geliştirici] 11 Haz 2020 @ 22:33
Extension Hints/Help Thread
Stuck on a particular part of System Rift that you just can't seem to figure out? Feel free to ask a few questions here, and I'll try and respond to you as quickly as possible!
< 1 2 3 4 5 6 ... 19 >
281 yorumdan 31 ile 45 arası gösteriliyor
Grosiek250 #King.Of.The.Cygans 12 Haz 2020 @ 22:34 
Ah I see now I though he was talking about something different
#31
coleslaw2005 12 Haz 2020 @ 22:43 
I'm asking about the v whitelist not the whitelist on the whitelist
#32
coleslaw2005 13 Haz 2020 @ 0:32 
virtual_whitelist :: LH1Y56 has no password.
#33
Aqua  [geliştirici] 13 Haz 2020 @ 0:37 
Looks like that is a major oversight from me! If you have debug commands enabled, then you can just forcehack/FH that system when you can access it. It should've had a password or been able to be hacked, but it looks like I glossed over the design of that! Sorry for that, it's fixed for a new update.
#34
coleslaw2005 13 Haz 2020 @ 6:25 
I hacked into the pacificus node and after getting forkbombed twice, I have no logs to get an IP from.
#35
Aqua  [geliştirici] 13 Haz 2020 @ 6:39 
The Pacificus attack is programmed to open a bunch of ports on your system before delivering a large forkbomb attack- There should be logs on your own computer that show the IP of the system that opened these ports and caused you to crash because of the forkbombs. Though, if all else fails, you could "dscan" the computer ID of the attacker which shouldn't be necessary. The ID of the attacker system is "pAccessBot"; the system should have left logs on your computer pertaining to your ports being opened by a foreign connection, though.
#36
coleslaw2005 13 Haz 2020 @ 6:49 
I can see the ports closing but not them opening
#37
coleslaw2005 13 Haz 2020 @ 7:40 
pacificus_internal: connections_filter can't be hacked without a new portcracker, and there's no password
#38
Kryptonoma 13 Haz 2020 @ 7:51 
I'm stuck on a beginning part of the extension:
I have to find the password for the DEC encryption. In the file sys_archive_encryption_source.txt it's written that the password is the {localhost} proxy identifier. As the config.ini file confirms, the identifier is 870HB3A. However, that's not the password. So, what is?
#39
Grosiek250 #King.Of.The.Cygans 13 Haz 2020 @ 11:12 
I have a problem with Security Plane mission in internals.etherfract.access , where I need to get the correct ip, so I did it like this "connect gc1522344053" I don't know what 4 is cause there is no X there
En son Grosiek250 #King.Of.The.Cygans tarafından düzenlendi; 13 Haz 2020 @ 11:13
#40
(VGW)TRUKZ!LLA*BE* 13 Haz 2020 @ 13:01 
what do you have to do in chapter two
#41
Grosiek250 #King.Of.The.Cygans 13 Haz 2020 @ 13:28 
Scan everything, check email and in short explore as much as you can for now
En son Grosiek250 #King.Of.The.Cygans tarafından düzenlendi; 13 Haz 2020 @ 13:29
#42
Aqua  [geliştirici] 13 Haz 2020 @ 14:57 
if there isn't an X on a line it won't be a part of the Security Plane's IP address.
#43
Grosiek250 #King.Of.The.Cygans 13 Haz 2020 @ 15:01 
So it will look like this gc15223453 ?
#44
Aqua  [geliştirici] 13 Haz 2020 @ 15:11 
Yup! That seems about right! Otherwise cracking into the internal access will force you into an ETAS but also disable the Security Plane either way, if all else fails.
#45
< 1 2 3 4 5 6 ... 19 >
281 yorumdan 31 ile 45 arası gösteriliyor
Sayfa başına: 1530 50