Iyakokin kariya a kowane dandali
Manhajojin Windows da Android suna ƙirƙirar ramin VPN a matakin tsarin. Akwai ƙarin burauza don Chrome, Edge, Firefox da Brave; kowanne yana kare burauzar da aka shigar da shi a ciki kawai. Ƙarin Chrome yana amfani da wakili na HTTPS da aka tantance; shafukan cikin burauzar, API na FuzeVPN da shafukan da aka ware ba sa wucewa ta wannan wakili. Ƙarin Edge yana amfani da lambar iri ɗaya da ta ƙarin Chrome, kuma Brave yana shigar da ƙarin Chrome daga Chrome Web Store, don haka duk abin da aka faɗa a ƙasa a ƙarƙashin “A Chrome” yana shafar Edge da Brave ma. Ƙarin Firefox yana dogara ne a kan fasalolin wakili na Firefox da kanta; yana kuma ƙunshe da kill switch, shafukan da aka ware da kariyar WebRTC, amma bayanan DNS, IPv6 da WebRTC da aka bayar a ƙasa game da ƙarin burauza suna shafar Chrome, Edge da Brave ne kawai.
Wannan yana kare bayanai yayin tafiya. Ba ya gyara na'urar da aka kutsawa, dawo da kalmar sirri da aka bayyana, kawar da haɗarin shafin yanar gizo mai cutarwa ko kare bayanan da aka bayar da son rai ga wani ɓangare.
Ka'idoji da ɓoye bayanai
A Chrome, ana ɓoye haɗin zuwa wakili da TLS ta TCP. Shafukan HTTPS suna wucewa ta ramin CONNECT kuma suna riƙe nasu ɓoyewar har zuwa shafin yanar gizon; shafin HTTP na yau da kullum ana ɓoye shi ne kawai tsakanin burauza da wakili. Ana zaɓar sigar TLS da tsarin ɓoyewa ta atomatik ga kowane haɗi, daga waɗanda burauza da wakili duka suke tallafawa.
A Android, WireGuard yana amfani da UDP/51820, Curve25519 da ChaCha20-Poly1305. OpenVPN yana amfani da UDP/1194, takardun shaida, tabbatar da uwar garke da tls-crypt-v2; tsarin ɓoye bayanan da aka yi yarjejeniya a kansa AES-256-GCM, AES-128-GCM ko ChaCha20-Poly1305 ne.
A Windows, WireGuardNT 1.1 yana amfani da UDP, Curve25519, ChaCha20-Poly1305, BLAKE2s da HKDF; ana kare maɓallan sirri a cikin na'urar ta DPAPI. OpenVPN 3 Core tare da DCO yana amfani da UDP/IPv4 a tashar 1194 ba tare da komawa TCP ba, tare da takardun shaida da tls-crypt-v2. Ana zaɓar tsarin ɓoyewarsa ta atomatik daga waɗanda uwar garke ta bayar.
Asusu da tantancewa
Ana adana kalmomin sirri bayan an yi musu hashing. Tabbatar da imel, sake saita kalmar sirri da hanyoyin zama suna amfani da token masu iyaka waɗanda za a iya sokewa.
Kukin zama HttpOnly, Secure da SameSite=Lax ne. Ana kare ayyuka masu muhimmanci daga buƙatun da suka fito daga wani tushe.
Na'urori da bayanan tantancewa na fasaha
FuzeVPN yana adana sunan na'ura, maɓallin jama'a ko takardar shaida, adireshin VPN na ciki da uwar garken da aka ba ta don saita da soke damar amfani.
Maɓallan sirri suna nan a na'urar. Share ko soke na'ura yana sa bayanan tantancewarta su daina aiki kuma yana 'yantar da matsayinta cikin iyakar na'urori 5.
DNS
A Chrome, wakilin ne ke warware sunayen shafukan yanar gizon da ke bi ta cikinsa. Sunan mai masaukin wakili, API, shafukan da aka keɓe da wasu warwarewa na hasashe suna amfani da hanyar DNS ta Chrome ko tsarin da aka saba. Ƙarin ba ya tilasta wani mai warwarewa, DNS-over-HTTPS ko DNS-over-TLS, don haka ba zai iya tabbatar da rashin duk wani warwarewar DNS na gida ba.
A Android, sabobin DNS suna fitowa daga saitin VPN kuma buƙatunsu suna tafiya ta ramin. Manhajar ba ta ƙara DoH ko DoT; burauzar da ke amfani da nata amintaccen DNS na iya zaɓar wani mai warwarewa yayin da take ci gaba da bin hanyar VPN.
A Windows, DNS da saitin ya bayar yana tafiya ta ramin. OpenVPN yana kunna block-outside-dns kuma WFP yana toshe IPv4 DNS a wajen ramin a tashoshin 53 da 853; an rufe IPv6 da toshensa na daban. Akwai iyakantaccen keɓancewar DNS kafin haɗi don isa API, sannan a cire shi. Idan ka kashe kill switch, manhajar da ke amfani da DoH a tashar 443 na iya ƙetare toshen da ya shafi DNS.
IPv6
A Chrome, wuraren yanar gizo na IPv6 na jama'a suna bi ta wakili sai waɗanda aka keɓe. Ba a kashe IPv6 a kwamfutar ba; ana toshe adiresoshin IPv6 na gida, loopback da link-local yayin da kariya ke aiki.
A Android da Windows, ingantaccen saitin dual-stack yana bi da IPv4 da IPv6 ta ramin. Idan babu saitin VPN na IPv6, ana toshe IPv6 yayin da ramin ke aiki, ba tare da komawa hanyar sadarwa ta zahiri a ɓoye ba. Hanyar zuwa uwar garken VPN a halin yanzu IPv4 ce.
WebRTC
A Chrome, zaɓin da aka kunna ta tsoho yana amfani da disable_non_proxied_udp don hana WebRTC UDP ƙetare wakili. Wannan saitin gaba ɗaya na iya rage ingancin wasu kira, yana kuma shafar shafukan da aka keɓe kuma ba ya rufe shafukan Chrome masu gata ko wasu ƙari.
A Android, WebRTC yana bin hanyar VPN amma ba a kashe shi a burauza kuma ba a ƙara matattarar WebRTC ta musamman ba. A Windows, zaɓin yana toshe UDP da ba loopback ba a wajen hanyar VPN; idan ka kashe kill switch, TURN ta TCP ko TLS/443 na iya ci gaba da aiki a wajen ramin. Bayyana ƴan takarar ICE na gida a burauza ba ya tabbatar da zubewar bayanai zuwa Intanet da kansa.
Kill switch
A cikin ƙarin Chrome, Edge, Firefox da Brave, kill switch yana kunne ta tsoho kuma yana toshe sabbin buƙatun yanar gizo har sai an tabbatar da haɗin. Ana ci gaba da ba da izinin shafukan da aka keɓe da buƙatun API na ciki; cire haɗi da son rai yana cire toshen.
A Android, kill switch yana dogara da saitunan tsarin “Always-on VPN” (VPN mai aiki kullum) da “Block connections without VPN” (Toshe haɗi ba tare da VPN ba), waɗanda mai amfani dole ne ya kunna.
A Windows, kill switch na WFP yana kunne ta tsohuwa kuma yana rufe IPv4 da IPv6. Yana sanya toshewa kafin kiran haɗi, sannan yana ba da izini ga sabis ɗin VPN da hanyar ramin kawai. Bayan gazawa, zirga-zirga yana ci gaba da toshewa har sai an cire haɗi a sarari. Matattara suna nan idan an rufe manhajar gani, amma suna ɓacewa idan mai gudanarwa ya dakatar da sabis mai gata. Ana iya kashe kill switch a cikin saitunan manhajar.
Babu rajistan ayyukan VPN
FuzeVPN ba ya adana shafukan da aka ziyarta, abun ciki, buƙatun DNS, adiresoshin IP na asali da ke da alaƙa da zama, lokutan haɗi, tsawon lokaci ko tarihin sabobin VPN da aka yi amfani da su.
Sabobin suna sarrafa zirga-zirga a ƙwaƙwalwa kawai muddin ake buƙata don jagorantar ta. FuzeVPN ba ya ƙirƙira ko tattara rajistan haɗin manhaja a wuri guda, sai dai rahotannin gano matsala da ka zaɓi aikawa daga manhajar, waɗanda ake adanawa na kwanaki 30.
Rajistan fasaha da sa ido
Ana sarrafa kayan aikin VPS da kai kuma ana girka su daga saiti na bai ɗaya wanda mai wallafawa ke dubawa a kowane girkawa; har yanzu ba a gudanar da bincike mai zaman kansa ba. Waɗannan dubawa suna tabbatar da rashin rajistan tsarin da ke dawwama a kan sabobin VPN; duk wani al'amari na ɗan lokaci a ƙwaƙwalwa ba ya ƙunsar abun cikin zirga-zirga, tarihin bincike ko alaƙa mai ɗorewa tsakanin mutum da zaman VPN.
Masu samarwa suna adana wasu rajistan dandali daban kamar yadda aka bayyana a Manufar Keɓantawa. Sa ido na FuzeVPN yana amfani da jimillar ma'aunin kayan aiki kawai maimakon tarihin binciken mutum.
Kayan aiki da kwafin ajiya
OVH SAS ne ke karɓar asusu a Faransa. Ana ɓoye kwafin ajiya kuma an iyakance kwafin nesa ga ikon Tarayyar Turai na Cloudflare R2. Cloudflare ne ke jagoranta da kare shafin yanar gizo, yankin abokin ciniki da API.
IONOS SARL, OVH SAS, HolyCloud, HosterDaddy, JustHost, da LuraHosting suna samar da sabobin sirri na kama-da-wane da ake karɓa a cibiyoyin bayanai na zahiri masu alaƙa da yanki. An wallafa jerin wurare a shafin “Wurare”; ƙasar da aka nuna ga kowane wuri ita ce ƙasar adireshin IP na fita. A zahiri, kowace uwar garken VPN tana cikin birni da ƙasar da aka nuna.
Samuwar sabis da amsawa
Ana iya katse sabis don gyara, abubuwan da suka faru, sabunta tsaro ko gazawar masu samarwa. Ba a tabbatar da kowane wuri ko damar zuwa sabis na wani ɓangare na dindindin ba.
A yayin matsala, ana iya soke damar amfani, keɓe sabis da dawo da kwafin ajiya. Ana tantance keta bayanan sirri bisa tsarin GDPR da ya dace.
Abin da ya dogara da kai
Yi amfani da kalmar sirri ta musamman, sabunta na'urori, soke na'urorin da suka ɓace kuma ka tabbatar haɗin VPN yana aiki kafin amfani da ke buƙatar kariya.
Sanar da contact@fuzevpn.com da sauri game da aikin da ba a saba gani ba. VPN ba ya maye gurbin sabuntawa, ƙaƙƙarfan tantancewa da ake da ita a wasu sabis ko taka tsantsan daga zamba.