- Messages
- 303
- Reaction score
- 0
- Points
- 26
keep it up guys... sayang di ako magaling sa linux at ssl... CDC na connection ko... wala na ring makitang pempem at keykey... hay.... :sad:
Symbianize Forum
Most of our features and services are available only to members, so we encourage you to login or register a new account. Registration is free, fast and simple. You only need to provide a valid email. Being a member you'll gain access to all member forums and features, post a message to ask question or provide answer, and share or find resources related to mobile phones, tablets, computers, game consoles, and multimedia.
All that and more, so what are you waiting for, click the register button and join us now! Ito ang website na ginawa ng pinoy para sa pinoy!
Dv235t .pem and .key expirement pag tulungan natin.
- Thread starter hackforumdotnet
- Start date
- Replies 151
- Views 17,041
- Messages
- 35
- Reaction score
- 0
- Points
- 26
habang tinitignan ko yung maigi yung nagenerate ko Cert... langhiya dito namali sa TYPE: printable string, etc... nang inaakala ko na MALAPIT NA KO SA KATOTOHANAN ...ang makulit dito.. tinawagan ako ng barkada at aming pinuntahan mga clients niya para ipakita lang sa akin na mula nung nadeploy nya yung mga MODEM ay CHANGE MAC lang ang ginagawa nya, walang Cert walang Key whatsoever.. nagulat talaga ako.. apat na clients ang pununtahan namin pare pareho CHANGE MAC lang talaga.. ang area is IRISAN BAGUIO CITY.. yung isa sa CITY CAMP Baguio City din pero ganito ang nangyare sa CITY CAMP.. kapag sa 234xxxx frequency connected change MAC lang sya, pero kapag sa 235xxxx need ng PEM at KEY... BIGLANG NAGULO ANG ISIP KO... thinking of an explanation bakit ganon.. bakit??????? kaya for now, stop muna ako dito.. I will continue to solve the missing link kung puede maka connect without PEM at KEY... i will give it 1 week... pero kapag di ko ma-solve, babalik ako dito sa pagtuklas kung pano ma-clone ang CERT generation...
tandaan TLS ang gamit ng mga devices natin (SSL is the OLD protocol)
para saan yan TLS? this is to ensure that the server is talking to a trusted device.. usually involves the recipient verifying the digital signature of the sender using the sender's PUBLIC KEY... The TLS uses a third party, a Certificate Authority (CA) eto yung Issuer ID na problem ko, to identify one end or both end of the transmission/transaction
The recipient (in our case, this is the SERVER) checks that the certificate was issued by a trusted party (usually a trusted root CA), that the certificate is still valid and that the certificate is related to the Server contacted.
Dito nagkakatalo sa TLS details na sinusubukan natin gayahin:
The sender uses the public key, to encrypt a random symmetric encryption key and sends it to the server ... bakit dito? yung PUBLIC KEY ang manggagaling sa AUTHORITY.. yung Private Key dalawa yan, private key ng device natin at yung Private key ng server... wala silang kinalaman sa isa't isa.. kapag ginamit yung private key with the Public key doon mo pa lang magagamit..
Information can be encrypted by one key but can only be decrypted by the other key pair (Private-Public Key Pair).. Dito maraming nalilito... ANONG KEY BA TINUTUKOY MO? Private Key Ba? or Public Key?
kung PRIVATE KEY kahit anong Private key pa yan.. as long as yung keys are similar in nature and can be used alternatively: what one key encrypts, the other key pair can decrypt..
ganito sa sender Private Key Mo plus Public Key equals encryption............. sa kabila sa receiver, Private Key Nya plus Public Key equals decryption...
Since alam ng lahat si Public Key, ganito ang requirement ni server para verified yung device mo: the Server will ask your Device to send a non confidential signed message that will contain the Device Public Key as well as a certificate.
at ito na nga yung last problem ko na Public Key Info which is the Authority Key Identifier at yung keyid galing yan sa Issuer which is Green Packet
MAGULO BA? sa mga nakakaintindi tulong na lang.. again dalawang KEY ito... kasi PRIVATE-PUBLIC KEY PAIR ENCRYPTION ito..
kaya kuha nyo why yung wmx_client_ca.pem ay tatlo? bakit? again PRIVATE-PUBLIC KEY PAIR ENCRYPTION
yung wmx_priv_key.key will be used with the PKI to encrypt the info
PERO HINDI GAGAMITIN SI wmx_priv_key.key to DECRYPT the INFO.. yung server_priv_key.key ang gagamitin ni server to DECRYPT the INFO...
tandaan TLS ang gamit ng mga devices natin (SSL is the OLD protocol)
para saan yan TLS? this is to ensure that the server is talking to a trusted device.. usually involves the recipient verifying the digital signature of the sender using the sender's PUBLIC KEY... The TLS uses a third party, a Certificate Authority (CA) eto yung Issuer ID na problem ko, to identify one end or both end of the transmission/transaction
The recipient (in our case, this is the SERVER) checks that the certificate was issued by a trusted party (usually a trusted root CA), that the certificate is still valid and that the certificate is related to the Server contacted.
Dito nagkakatalo sa TLS details na sinusubukan natin gayahin:
The sender uses the public key, to encrypt a random symmetric encryption key and sends it to the server ... bakit dito? yung PUBLIC KEY ang manggagaling sa AUTHORITY.. yung Private Key dalawa yan, private key ng device natin at yung Private key ng server... wala silang kinalaman sa isa't isa.. kapag ginamit yung private key with the Public key doon mo pa lang magagamit..
Information can be encrypted by one key but can only be decrypted by the other key pair (Private-Public Key Pair).. Dito maraming nalilito... ANONG KEY BA TINUTUKOY MO? Private Key Ba? or Public Key?
kung PRIVATE KEY kahit anong Private key pa yan.. as long as yung keys are similar in nature and can be used alternatively: what one key encrypts, the other key pair can decrypt..
ganito sa sender Private Key Mo plus Public Key equals encryption............. sa kabila sa receiver, Private Key Nya plus Public Key equals decryption...
Since alam ng lahat si Public Key, ganito ang requirement ni server para verified yung device mo: the Server will ask your Device to send a non confidential signed message that will contain the Device Public Key as well as a certificate.
at ito na nga yung last problem ko na Public Key Info which is the Authority Key Identifier at yung keyid galing yan sa Issuer which is Green Packet
MAGULO BA? sa mga nakakaintindi tulong na lang.. again dalawang KEY ito... kasi PRIVATE-PUBLIC KEY PAIR ENCRYPTION ito..
kaya kuha nyo why yung wmx_client_ca.pem ay tatlo? bakit? again PRIVATE-PUBLIC KEY PAIR ENCRYPTION
yung wmx_priv_key.key will be used with the PKI to encrypt the info
PERO HINDI GAGAMITIN SI wmx_priv_key.key to DECRYPT the INFO.. yung server_priv_key.key ang gagamitin ni server to DECRYPT the INFO...
Last edited:
- Messages
- 164
- Reaction score
- 0
- Points
- 26
- Thread Starter
- #83
Magandang balita yan kapatid. makikibalita lang kami.
- Messages
- 35
- Reaction score
- 0
- Points
- 26
habang tinitignan ko yung maigi yung nagenerate ko Cert... langhiya dito namali sa TYPE: printable string, etc... nang inaakala ko na MALAPIT NA KO SA KATOTOHANAN ...ang makulit dito.. tinawagan ako ng barkada at aming pinuntahan mga clients niya para ipakita lang sa akin na mula nung nadeploy nya yung mga MODEM ay CHANGE MAC lang ang ginagawa nya, walang Cert walang Key whatsoever.. nagulat talaga ako.. apat na clients ang pununtahan namin pare pareho CHANGE MAC lang talaga.. ang area is IRISAN BAGUIO CITY.. yung isa sa CITY CAMP Baguio City din pero ganito ang nangyare sa CITY CAMP.. kapag sa 234xxxx frequency connected change MAC lang sya, pero kapag sa 235xxxx need ng PEM at KEY... BIGLANG NAGULO ANG ISIP KO... thinking of an explanation bakit ganon.. bakit??????? kaya for now, stop muna ako dito.. I will continue to solve the missing link kung puede maka connect without PEM at KEY... i will give it 1 week... pero kapag di ko ma-solve, babalik ako dito sa pagtuklas kung pano ma-clone ang CERT generation...
tandaan TLS ang gamit ng mga devices natin (SSL is the OLD protocol)
para saan yan TLS? this is to ensure that the server is talking to a trusted device.. usually involves the recipient verifying the digital signature of the sender using the sender's PUBLIC KEY... The TLS uses a third party, a Certificate Authority (CA) eto yung Issuer ID na problem ko, to identify one end or both end of the transmission/transaction
The recipient (in our case, this is the SERVER) checks that the certificate was issued by a trusted party (usually a trusted root CA), that the certificate is still valid and that the certificate is related to the Server contacted.
Dito nagkakatalo sa TLS details na sinusubukan natin gayahin:
The sender uses the public key, to encrypt a random symmetric encryption key and sends it to the server ... bakit dito? yung PUBLIC KEY ang manggagaling sa AUTHORITY.. yung Private Key dalawa yan, private key ng device natin at yung Private key ng server... wala silang kinalaman sa isa't isa.. kapag ginamit yung private key with the Public key doon mo pa lang magagamit..
Information can be encrypted by one key but can only be decrypted by the other key pair (Private-Public Key Pair).. Dito maraming nalilito... ANONG KEY BA TINUTUKOY MO? Private Key Ba? or Public Key?
kung PRIVATE KEY kahit anong Private key pa yan.. as long as yung keys are similar in nature and can be used alternatively: what one key encrypts, the other key pair can decrypt..
ganito sa sender Private Key Mo plus Public Key equals encryption............. sa kabila sa receiver, Private Key Nya plus Public Key equals decryption...
Since alam ng lahat si Public Key, ganito ang requirement ni server para verified yung device mo: the Server will ask your Device to send a non confidential signed message that will contain the Device Public Key as well as a certificate.
at ito na nga yung last problem ko na Public Key Info which is the Authority Key Identifier at yung keyid galing yan sa Issuer which is Green Packet
MAGULO BA? sa mga nakakaintindi tulong na lang.. again dalawang KEY ito... kasi PRIVATE-PUBLIC KEY PAIR ENCRYPTION ito..
kaya kuha nyo why yung wmx_client_ca.pem ay tatlo? bakit? again PRIVATE-PUBLIC KEY PAIR ENCRYPTION
yung wmx_priv_key.key will be used with the PKI to encrypt the info
PERO HINDI GAGAMITIN SI wmx_priv_key.key to DECRYPT the INFO.. yung server_priv_key.key ang gagamitin ni server to DECRYPT the INFO...
tandaan TLS ang gamit ng mga devices natin (SSL is the OLD protocol)
para saan yan TLS? this is to ensure that the server is talking to a trusted device.. usually involves the recipient verifying the digital signature of the sender using the sender's PUBLIC KEY... The TLS uses a third party, a Certificate Authority (CA) eto yung Issuer ID na problem ko, to identify one end or both end of the transmission/transaction
The recipient (in our case, this is the SERVER) checks that the certificate was issued by a trusted party (usually a trusted root CA), that the certificate is still valid and that the certificate is related to the Server contacted.
Dito nagkakatalo sa TLS details na sinusubukan natin gayahin:
The sender uses the public key, to encrypt a random symmetric encryption key and sends it to the server ... bakit dito? yung PUBLIC KEY ang manggagaling sa AUTHORITY.. yung Private Key dalawa yan, private key ng device natin at yung Private key ng server... wala silang kinalaman sa isa't isa.. kapag ginamit yung private key with the Public key doon mo pa lang magagamit..
Information can be encrypted by one key but can only be decrypted by the other key pair (Private-Public Key Pair).. Dito maraming nalilito... ANONG KEY BA TINUTUKOY MO? Private Key Ba? or Public Key?
kung PRIVATE KEY kahit anong Private key pa yan.. as long as yung keys are similar in nature and can be used alternatively: what one key encrypts, the other key pair can decrypt..
ganito sa sender Private Key Mo plus Public Key equals encryption............. sa kabila sa receiver, Private Key Nya plus Public Key equals decryption...
Since alam ng lahat si Public Key, ganito ang requirement ni server para verified yung device mo: the Server will ask your Device to send a non confidential signed message that will contain the Device Public Key as well as a certificate.
at ito na nga yung last problem ko na Public Key Info which is the Authority Key Identifier at yung keyid galing yan sa Issuer which is Green Packet
MAGULO BA? sa mga nakakaintindi tulong na lang.. again dalawang KEY ito... kasi PRIVATE-PUBLIC KEY PAIR ENCRYPTION ito..
kaya kuha nyo why yung wmx_client_ca.pem ay tatlo? bakit? again PRIVATE-PUBLIC KEY PAIR ENCRYPTION
yung wmx_priv_key.key will be used with the PKI to encrypt the info
PERO HINDI GAGAMITIN SI wmx_priv_key.key to DECRYPT the INFO.. yung server_priv_key.key ang gagamitin ni server to DECRYPT the INFO...
Last edited:
- Messages
- 303
- Reaction score
- 0
- Points
- 26
- Messages
- 2,384
- Reaction score
- 344
- Points
- 28
sumakit ulo ko sa kakabasa sa mga reply dito sa thread mo ts....3 times ko inulit binasa mga comments dito...grabe ang hirap intindihin talaga...may mga part na medyo nagegets ko pero ang kaso wala naman akong alam sa ganito....change mac lang nuon si smarty okay na eh...pero ngayon lalong nagpapakipot si smarty...
may nabasa pa ako dito nagaaway si sir gerald at si sir planbuilder....hehehe!!! oks lang yan mga sir...wag dadaanin sa init ng ulo...tulungan na lang po...
PEACE PO TAYO DITO MGA MASTERS
goodluck and GOD BLESS po sayo ts at sa mga kasamahan mo dito na walang sawang humahanap ng paraan para masolve ang problema natin kay smarty...
UP FOR THIS...malapit na yan....aabangan namin to ts and co.....
may nabasa pa ako dito nagaaway si sir gerald at si sir planbuilder....hehehe!!! oks lang yan mga sir...wag dadaanin sa init ng ulo...tulungan na lang po...
PEACE PO TAYO DITO MGA MASTERS
goodluck and GOD BLESS po sayo ts at sa mga kasamahan mo dito na walang sawang humahanap ng paraan para masolve ang problema natin kay smarty...
UP FOR THIS...malapit na yan....aabangan namin to ts and co.....
- Messages
- 208
- Reaction score
- 0
- Points
- 26
sakit sa ulo wala ma iscan na pem at key.. kung d masolve ang ganitong problem eto nlng pano hugutin un pem at key sa legit kc read-only un nlng pag tuunan ng pansin using command mapalabas c pem at key na naka read only alm ko may nagaaral na eto kung pano hugutin un naka read only d q alm f nagawa na nila... andon lng naman kc un kelangan kaso na read only lng xa.. hmmmm... nakalantad na d lng makuha hahahaha...
- Messages
- 164
- Reaction score
- 0
- Points
- 26
- Thread Starter
- #88
- Messages
- 838
- Reaction score
- 0
- Points
- 26
up up natin para kay sir cyberfish isa kang henyo.... sana matulungan mo kami pag natapos at gumagana na....
more power to you sir
- - - Updated - - -
up up natin para kay sir cyberfish isa kang henyo.... sana matulungan mo kami pag natapos at gumagana na....
more power to you sir
- - - Updated - - -
up up natin para kay sir cyberfish isa kang henyo.... sana matulungan mo kami pag natapos at gumagana na....
more power to you sir
more power to you sir
- - - Updated - - -
up up natin para kay sir cyberfish isa kang henyo.... sana matulungan mo kami pag natapos at gumagana na....
more power to you sir
- - - Updated - - -
up up natin para kay sir cyberfish isa kang henyo.... sana matulungan mo kami pag natapos at gumagana na....
more power to you sir
- Messages
- 438
- Reaction score
- 0
- Points
- 26
Attachments
- Messages
- 403
- Reaction score
- 0
- Points
- 26
nice discovery tol. dito sa loc namin talagang need tlga ng pem/key tuwing mac changing at sa 2 freqs na meron kami (233, 235). keep it up sir!
- Messages
- 416
- Reaction score
- 0
- Points
- 26
sana ma discover na tlga naten to..
pa OT, pwede ba mag connect sa witribe ang DV235? pa link naman ng tut thanks,
pa OT, pwede ba mag connect sa witribe ang DV235? pa link naman ng tut thanks,
Base sakin, sa pagkalkal ko ng mga modems, like DV and mga OX mukang nasa firmware mismo ang sikreto kong bakit na eencode ung pem nya pansinin natin pag punta tau sa uploading ng key at pem sa OX makikita mo may nakalagay doon base sa original mac nya. pero key wala . tingin ko nabura or na ilagay na un sa isang sulok sa loob ng modem in time na nakapag boot up na sia completely and naload na nya un.
Kong makakapag decode man and re Encode mas ok din. d natin alam baka wala nang bukas ang mga may pem and key na OX
~sinichi
Kong makakapag decode man and re Encode mas ok din. d natin alam baka wala nang bukas ang mga may pem and key na OX
~sinichi
- Messages
- 838
- Reaction score
- 0
- Points
- 26
ano na po balita dito bossing cyber?
- Messages
- 389
- Reaction score
- 0
- Points
- 26
pa tambay dito mukang maganda to 
- Messages
- 838
- Reaction score
- 0
- Points
- 26
up up up san ka na bossing cyber
iamsuperpham
Terminated Account
- Messages
- 68
- Reaction score
- 0
- Points
- 16
Sinong gusto sumama sakin ? #ProjectSSL ko...... Need testers.... marunong akong magclone ng certificate.....
Add mo ko sa FB : https://www.facebook.com/profile.php?id=100001092707000 at ipapakita ko sayo ang aking gawa
- - - Updated - - -
tulungan tayo makakuha ng private key ng server , ako mag eencrypt.....
Add mo ko sa FB : https://www.facebook.com/profile.php?id=100001092707000 at ipapakita ko sayo ang aking gawa
- - - Updated - - -
tulungan tayo makakuha ng private key ng server , ako mag eencrypt.....
