Jump to content

tjt

Active Members
  • Content count

    726
  • Joined

  • Last visited

  • Days Won

    3

tjt last won the day on April 3

tjt had the most liked content!

Community Reputation

166 Excellent

About tjt

  • Rank
    Registered user
  1. Stai cu ochi pe olx si poate ai noroc sa il gasesti acolo. Totusi sunt putine sanse sa il mai recuperezi.
  2. Achizitionare laptop.

    Ce cu panaramele alea ? Induci bietu' om in eroare cu asemenea chinezarii. Aici gasesti ceva de calitate: laptop .
  3. Attacking Java Deserialization

    Am citit pe verticala mai mult, dar din ce am inteles nu e chiar un atac asupra desrializarii in java. El se foloseste de o vulnerabilitate existenta in cod, asta insemnand ca e absolut necesar sa ai acces la cod.
  4. bypass android protection

    Redenumeste apk-ul. Numele sa fie diferit de Superuser.apk, dupa ii dai adb push in /system/app/ si reboot. 1. adb root 2. adb pull /system/app/Superuser.apk 3. adb shel rm /system/app/Superuser.apk 4. adb shell reboot 5. Redenumeste Superuser.apk in blablabla.apk sau ce vrei tu 6. adb root 7. adb push blablabla.apk /system/app 8. adb shell reboot La pasul 7-8 ar trb sa reinstaleze aplicatia.
  5. bypass android protection

    Am citit pe net ca by default ai acces la root pe gennymotion. Tu ai acces la root, dar vrei si apk-ul Superuser instalat ? Aplicatia functioneaza inainte de a instala Superuser.apk ?
  6. Salut, A trebuit azi la munca sa fac un state machine ca sa updatez UI bazat pe niste eventuri pe care le primesc. Am in jur de 50 de stari, 200 si ceva de eventuri si peste 800 de posibile tranzitii. M-am lovit si in trecut de state machine, dar le-am evitat de fiecare data pentru ca nu mi-au placut niciodata. Am implementat ceva la o scara mai mica folosind ca exemplu ca sa vedeti cum am gandit totul: import com.statemachine.test.events.Event; public class StateMachine { private enum Event{ GO, CWAIT, FINISH, RESET; } private interface IState{ public IState process(Event e); } private enum State implements IState{ START("START"){ @Override public IState process(Event e){ printName(); switch(e) { case GO: System.out.println("received GO. Return FIRE\n"); return FIRE; case CWAIT: System.out.println("received CWAIT. Return WAIT\n"); return WAIT; default: System.out.println("received something unexpected. Don't change\n"); return this; } } }, WAIT("WAIT"){ @Override public IState process(Event e){ printName(); switch(e) { case GO: System.out.println("received GO. Return FIRE\n"); return FIRE; case RESET: System.out.println("received RESET. Return START\n"); return START; default: System.out.println("received something unexpected. Don't change\n"); return this; } } }, FIRE("FIRE"){ @Override public IState process(Event e){ printName(); switch(e) { case FINISH: System.out.println("received FINISH. Return START\n"); return START; case CWAIT: System.out.println("received CWAIT. Return WAIT\n"); return WAIT; default: System.out.println("received something unexpected. Don't change\n"); return this; } } }; String name = null; private State(String name) { this.name = name; } public String getName() { return this.name; } public void printName() { System.out.println("State: " + this.name); } } public static void main(String[] args) { IState state = State.START; state = state.process(Event.RESET); state = state.process(Event.CWAIT); state = state.process(Event.GO); state = state.process(Event.CWAIT); state = state.process(Event.GO); state = state.process(Event.FINISH); state = state.process(Event.GO); state = state.process(Event.RESET); } } Output: State: START received something unexpected. Don't change State: START received CWAIT. Return WAIT State: WAIT received GO. Return FIRE State: FIRE received CWAIT. Return WAIT State: WAIT received GO. Return FIRE State: FIRE received FINISH. Return START State: START received GO. Return FIRE State: FIRE received something unexpected. Don't change Programu merge, isi updateaza starile dar am impresia ca nu e tocmai ok implementarea si ca o sa ma trezesc peste 1-2 luni sa refac totul. Vreo sugestie cum ar putea fi imbunatatit sau poate o alta abordare ? Thanks.
  7. Mi se pare incredibil cat de repede se mobilizeaza toate serviciile DIICOT, SRI si care or mai fi pentru un 'atac informatic'. Daca ar fi asa de prompti si intereasati si in alte situatii care nu sunt 'atacuri' asupra institutilor statului ci atacuri impotriva populatiei gen: diluarea substantelor folosite pt igienizarea spitalelor, ce tara misto am avea. Macar sa ne zica la ce informatii strict secrete au avut acces. Sa intelegem si noi dimensiunea acestui atac. Cate persoane a salvat aceasta operatiune, cate persoane o sa iasa pe strada incepand de azi fara frica de a le fi atacat informatic apartamentul cat timp sunt plecati. Cate persoane a salvat de la infectiile pe care le iei prin spitale. Sa dea numere, rapoarte, costuri, valoarea prejudiciului. Sa intelegem cu toti ce au facut.
  8. Update IPBoard 4.2.0

    Ce oribil arata "reactions" . Ceva gen daca facebook o face, hai sa o facem si noi .
  9. Rule 1: Restrict all code to very simple control flow constructs—do not use goto statements, setjmp or longjmp constructs, or direct or indirect recursion. Rule 2: Give all loops a fixed upper bound. It must be trivially possible for a checking tool to prove statically that the loop cannot exceed a preset upper bound on the number of iterations. If a tool cannot prove the loop bound statically, the rule is considered violated. Rule 3: Do not use dynamic memory allocation after initialization. Rule 4: No function should be longer than what can be printed on a single sheet of paper in a standard format with one line per statement and one line per declaration. Typically, this means no more than about 60 lines of code per function Rule 5: The code’s assertion density should average to minimally two assertions per function. Assertions must be used to check for anomalous conditions that should never happen in reallife executions. Assertions must be side-effect free and should be defined as Boolean tests. When an assertion fails, an explicit recovery action must be taken such as returning an error condition to the caller of the function that executes the failing assertion. Any assertion for which a static checking tool can prove that it can never fail or never hold violates this rule. Rule 6: Declare all data objects at the smallest possible level of scope. Rule 7: Each calling function must check the return value of nonvoid functions, and each called function must check the validity of all parameters provided by the caller. Rule 8: The use of the preprocessor must be limited to the inclusion of header files and simple macro definitions. Token pasting, variable argument lists (ellipses), and recursive macro calls are not allowed. All macros must expand into complete syntactic units. The use of conditional compilation directives must be kept to a minimum. Rule 9: The use of pointers must be restricted. Specifically, no more than one level of dereferencing should be used. Pointer dereference operations may not be hidden in macro definitions or inside typedef declarations. Function pointers are not permitted. Rule 10: All code must be compiled, from the first day of development, with all compiler warnings enabled at the most pedantic setting available. All code must compile without warnings. All code must also be checked daily with at least one, but preferably more than one, strong static source code analyzer and should pass all analyses with zero warnings. Source & more details here: https://spinroot.com/gerard/pdf/Power_of_Ten.pdf
  10. La cat ai scris cred ca i-ai face invidiosi pe cei care au picat bacu' . Cel mai usor mod de a iesi din 'idei geniale la miez de noapte' si sa iti gasesti o motivatie in a face ceva este sa iti stabilesti targeturi pentru care sa dai bani. Platesti pentru un examen (retele, linux, lb. straine, forex, design, etc) si il stabilesti la 1-2 luni distanta. Cu cat mai mic timpul necesar cu atat mai bine. Sa vezi ce chef de invatat o sa ai cand realizezi ca pierzi 100-200 de euro din buzunarul tau pe frecat menta.
  11. header x-key api

    Ai API key de la ei ca sa-l folosesti ?
  12. Salariu Infosec

    De ce sa nu iti dea ? Toata lumea vorbeste de experienta ca de cel mai 'sfant' lucru pe care trebuie sa-l aiba cineva. Experienta in IT e relativa, nu poti sa compari 5 ani in care ai fixat cate un bug pe ici pe colo pe un proiect mic, iar jumate din cod pe care il scriai era copy-paste de pe stackoverflow cu cineva care a lucrat 2 ani pe un proiect mare in care interactiona cu foarte multi developeri, testeri, analisti, pe un proiect in care nu isi permitea sa bage mizerii in codul de productie ca il arata arhitectul cu degetu'. Eu cred ca cineva care e la inceput, cineva care a investit timpul personal chiar si bani ca sa isi imbunatateasca cunostinte, sa obtina certificari, e mult mai valoros. Dovedeste entuziasm, pasiune si determinare. Ca ai 5 ani de experienta, ca ai 1 an de experienta de cele mai multe ori la noul loc de munca esti pe un proiect total diferit de ceea ce faceai si perioada de tranzitie e la fel pentru ambii. Legat de salariu, depinde cum te vinzi. Cred ca poti pleca lejer de la 4.000 in Bucuresti, dar depinde ce alte beneficii primesti, de numele firmei, de volumul de munca. Si inca ceva, nu cred ca ai certificarile respective. Daca le aveai nu mai intrebai pe forum despre cat ai putea castiga. Daca vrei sa le dai, pune mana pe carte si mult succes.
  13. Comentarii Github

    Nu inteleg la ce te referi prin "comasate" , "descarcate" si "evaluate" ? ? Poti explica in termeni mai tehnici ce se intampla sau sa descrii pasii macar. "comasate" - s-au combinate comentariile de la mai multe patch seturi ? "descarcate" - te referi ca nu ti le arata in "git log" ? "evaluate" - comentariile din commit message din ce stiu eu au doar un rol informativ, nu sunt evaluate de nimeni.
  14. Interviu telefon

    Asta-i PSDist, il urmareste binomul peste tot.
×