18%
03.02.2022
is made possible because cron only checks for a date format and not that the date of the task is legitimate. The crontab date specification for CronRAT is 52 23 31 2 3, which would generate a runtime error
18%
26.03.2025
(s_sudojson);
parser(p_json);
destination(d_sudo);
};
Listing 2
New Logfile Format
May 22 09:38:51 user tscherf ran /usr/bin/vim on host master.ipa.test using sudo
May 22 09:38:52 user tscherf ran
18%
30.01.2020
.0.0.0/0
45 - IpProtocol: udp
46 FromPort: 0
47 ToPort: 65535
48 CidrIp: 0.0.0.0/0
49 VpcId:
50 Ref: FortiVPC
51
52 InstanceProfile:
53 Properties:
54
18%
10.06.2014
60176d8a8e3",
30 "creator_uuid": "352971aa-31ba-496c-9ade-a379feaecd52",
31 "vendor_uuid": "352971aa-31ba-496c-9ade-a379feaecd52",
32 "creator_name": "ADMIN",
33 "platform
18%
17.05.2017
data buffer with trivial data
45 ALLOCATE ( DATA(DIMSF(1),DIMSF(2)) )
46 DO I = 1, DIMSF(2)
47 DO J = 1, DIMSF(1)
48 DATA(J,I) = J - 1 + (I-1)*DIMSF(1)*(MPI_RANK+1)
49 ENDDO
50 ENDDO
51
52
18%
30.01.2020
exploring.
Infos
"Automatically install and configure systems" by Martin Loschwitz, ADMIN
, issue 52, 2019, pg. 62: http://www.admin-magazine.com/Archive/2019/52/Automatically
18%
16.08.2018
-system state UP qlen 1000
link/ether 52:54:00:6b:55:21 brd ff:ff:ff:ff:ff:ff
inet6 fe80::5054:ff:fe6b:5521/64 scope link
valid_lft forever preferred_lft forever
Listing 4
Querying
18%
30.11.2025
Completed 37/37 5598/5598 32.52/32.52
17
18 PHASE ACTIONS
19 Install Phase 7329/7329
20
21 Note
18%
31.05.2012
,383.80
225.23
1.55
parse_int
1.44
16.50
815.19
6,454.50
337.52
2.17
quicksort
1.49
55.84
132.71
3,127.50
713
18%
30.11.2020
'd for the filenames, which are placed in @filelist (lines 52, 53). A foreach loop then opens and reads each file, byte-by-byte, the content of which is placed in the aptly name scalar $text.
Next, the code splits
