Originally posted by AlxRogan
Announcement
Collapse
No announcement yet.
Computer Vulnerability help
Collapse
X
-
Originally posted by Voltage Spikesay's? highwizard, are you making up words again?
Oh, and sorry Ozone: you're a script kiddie. I'm pretty sure you become infallible around here once your post count reaches 4 digits.
VoltageSpike: Do you like the flavor?
http://dictionary.reference.com/search?q=say%27s
Comment
-
Originally posted by highwizard
http://dictionary.reference.com/search?q=assho%27le
As for having no balls, I can neither confirm nor deny that rumor (NDA).
Comment
-
Originally posted by Voltage_SpikeOh, and sorry Ozone: you're a script kiddie. I'm pretty sure you become infallible around here once your post count reaches 4 digits.
Originally posted by highwizardVoltageSpike: Do you like the flavor?
Comment
-
Originally posted by highwizardDamn, you really are a pussy, if you can't respond to that.
Originally posted by New OrderThe wisdom of the fool won’t set you free
But that’s the way that it goes
And it’s what nobody knows
Well every day my confusion grows
*highwizard enters the discussion*
Every time I see you falling
I get down on my knees and pray
I’m waiting for that final moment
You say the words that I can’t say
Comment
-
Sorry for the long wait on the results for my network security class. I got a 3.8 (out of 4.0) out of the class. Which i am very proud of, and I would like to thank Highwizard, TheCotMan, and voltage spike for their words of wisdom. That helped me though my group project. Which was poorly setup by the sounds of it. The computer that was setup for my group to pen test was being altered though all of my test. Which is a bitch to do when trying to gain access to this computer.
I went though my presentation describing each step i took in the four stages of pen testing. That was supplied to me by TheCotMan. This made for an interesting presentation. I kept finding myself repeating over and over in hopes it ingrains this information not only in their heads, but mine as well. I never got into the computer that was designated for the pen testing. Which saddened me, but will make me work harder in my studies to get better. I never got to mess around with Nesus as much as I wanted, but I the experiences in various other programs was fun. Also helping out the Honeypot group was fun. They downloaded the trial version of a windows honeypot. Then we worked together to present some information that would help in the discovery of a honeypot, and the setting up of one. Also I showed them my posts at Defcon. That is basically it. OH yeah, I told them to never DOUBLE POST!!!
-Enjoy
================================================
Four stages of Pen Testing
==================================================
1. planning
2. discovery
3. attack
4. reporting
=================================
This is the port scan on target computer.
==============================
[root@localhost ~]# nc -v -z -w 3 134.39.10.240 1-65321
dpsvr2003.mtolympus.local [ 134.39.10.240] 3389 (?) open
dpsvr2003.mtolympus.local [134.39.10.240] 3269 (?) open
dpsvr2003.mtolympus.local [ 134.39.10.240 ] 3268 (?) open
dpsvr2003.mtolympus.local [134.39.10.240] 1088 (?) open
dpsvr2003.mtolympus.local [134.39.10.240] 1038 (?) open
dpsvr2003.mtolympus.local [134.39.10.240] 1028 (?) open
dpsvr2003.mtolympus.local [134.39.10.240] 1025 (?) open
dpsvr2003.mtolympus.local [ 134.39.10.240] 636 (ldaps) open
dpsvr2003.mtolympus.local [134.39.10.240] 593 (?) open
dpsvr2003.mtolympus.local [134.39.10.240] 464 (kpasswd) open
dpsvr2003.mtolympus.local [134.39.10.240] 445 (microsoft-ds) open
dpsvr2003.mtolympus.local [134.39.10.240] 389 (ldap) open
dpsvr2003.mtolympus.local [134.39.10.240] 135 (?) open
dpsvr2003.mtolympus.local [134.39.10.240] 88 (kerberos) open
dpsvr2003.mtolympus.local [ 134.39.10.240] 53 (domain) open
[root@localhost ~]#
==============================================
Second scan
=======================================
root@l19msftxps10 ~]# nc -v -w3 -z 134.39.10.240 1-60000
dpsvr2003.mtolympus.local [134.39.10.240] 3389 (?) open
dpsvr2003.mtolympus.local [134.39.10.240] 3269 (?) open
dpsvr2003.mtolympus.local [134.39.10.240] 3268 (?) open
dpsvr2003.mtolympus.local [134.39.10.240] 636 (ldaps) open
dpsvr2003.mtolympus.local [ 134.39.10.240] 593 (?) open
dpsvr2003.mtolympus.local [134.39.10.240] 464 (kpasswd) open
dpsvr2003.mtolympus.local [134.39.10.240] 445 (microsoft-ds) open
dpsvr2003.mtolympus.local [134.39.10.240] 389 (ldap) open
dpsvr2003.mtolympus.local [134.39.10.240] 135 (?) open
dpsvr2003.mtolympus.local [ 134.39.10.240] 88 (kerberos) open
dpsvr2003.mtolympus.local [134.39.10.240] 53 (domain) open
================================================== =
Port info
====================
135 UDP epmap DCE endpoint resolution
88 TCP kerberos Kerberos
53 UDP domain Domain Name Server
389 TCP ldap Lightweight Directory Access Protocol
445 TCP microsoft-ds Microsoft-DS Lioten, Randon, WORM_DELODER.A, W32/Deloder.A, W32.HLLW.Deloder, Sasser
445 UDP microsoft-ds Microsoft-DS
464 TCP kpasswd kpasswd
464 UDP kpasswd kpasswd
593 TCP http-rpc-epmap HTTP RPC Ep Map
593 UDP http-rpc-epmap HTTP RPC Ep Map
636 TCP ldaps ldap protocol over TLS/SSL (was sldap)
636 UDP ldaps ldap protocol over TLS/SSL (was sldap)
1025 TCP blackjack network blackjack Fraggle Rock, md5 Backdoor, NetSpy, Remote Storm
1025 UDP blackjack network blackjack Remote Storm
1038 TCP mtqp Message Tracking Query Protocol
1038 UDP mtqp Message Tracking Query Protocol
1088 UDP cplscrambler-al CPL Scrambler Alarm Log
1089 TCP ff-annunc FF Annunciation
3268 TCP msft-gc Microsoft Global Catalog
3268 UDP msft-gc Microsoft Global Catalog
3269 TCP msft-gc-ssl Microsoft Global Catalog with LDAP/SSL
3269 UDP msft-gc-ssl Microsoft Global Catalog with LDAP/SSL
3389 TCP ms-wbt-server MS WBT Server
3389 UDP ms-wbt-server MS WBT Server
=======================================
checking 134.39.10.17
=============================================
[root@l19msftxps10 ~]# ping 134.39.10.17
PING 134.39.10.17 (134.39.10.17) 56(84) bytes of data.
64 bytes from 134.39.10.17: icmp_seq=0 ttl=64 time=0.267 ms
64 bytes from 134.39.10.17: icmp_seq=1 ttl=64 time=0.236 ms
64 bytes from 134.39.10.17: icmp_seq=2 ttl=64 time=0.229 ms
64 bytes from 134.39.10.17: icmp_seq=3 ttl=64 time=0.239 ms
64 bytes from 134.39.10.17: icmp_seq=4 ttl=64 time= 0.245 ms
64 bytes from 134.39.10.17: icmp_seq=5 ttl=64 time=0.204 ms
64 bytes from 134.39.10.17: icmp_seq=6 ttl=64 time=0.223 ms
=============================================
Ports open for 134.39.10.17
==============================================
22 ssh open
25 smtp open
111 sunrpc open
113 auth open
1241 unknown open
=========================================
Programs under the port
=========================================
593 ncacn_http/1.0
=================================
Information on ports and vulnerablities
===================================
http://web.mit.edu/kerberos/www/advi...3-004-krb4.txt
Comment
-
Originally posted by Ozonei took in the four stages of pen testing. That was supplied to me by TheCotMan.
Also I showed them my posts at Defcon. That is basically it. OH yeah, I told them to never DOUBLE POST!!!
Comment
Comment